|
1 | 1 |
|
2 | 2 | Developer's Frequently Asked Questions (FAQ) for PostgreSQL |
3 | 3 |
|
4 | | - Last updated:Mon Sep 19 21:28:08 EDT 2005 |
| 4 | + Last updated:Thu Oct 27 09:48:14 EDT 2005 |
5 | 5 |
|
6 | 6 | Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) |
7 | 7 |
|
@@ -798,11 +798,13 @@ typedef struct nameData |
798 | 798 | If the postmaster is running, start psql in one window, then find the |
799 | 799 | PID of the postgres process used by psql using SELECT |
800 | 800 | pg_backend_pid(). Use a debugger to attach to the postgres PID. You |
801 | | - can set breakpoints in the debugger and issue queries from psql. If |
802 | | - you are debugging postgres startup, you can set PGOPTIONS="-W n", then |
803 | | - start psql. This will cause startup to delay for n seconds so you can |
804 | | - attach to the process with the debugger, set any breakpoints, and |
805 | | - continue through the startup sequence. |
| 801 | + can set breakpoints in the debugger and issue queries from the other. |
| 802 | + If you are looking to find the location that is generating an error or |
| 803 | + log message, set a breakpoint at errfinish. psql. If you are debugging |
| 804 | + postgres startup, you can set PGOPTIONS="-W n", then start psql. This |
| 805 | + will cause startup to delay for n seconds so you can attach to the |
| 806 | + process with the debugger, set any breakpoints, and continue through |
| 807 | + the startup sequence. |
806 | 808 |
|
807 | 809 | You can also compile with profiling to see what functions are taking |
808 | 810 | execution time. The backend profile files will be deposited in the |
|