|
|
|
|
@ -13,7 +13,7 @@ |
|
|
|
|
<H1>Developer's Frequently Asked Questions (FAQ) for |
|
|
|
|
PostgreSQL</H1> |
|
|
|
|
|
|
|
|
|
<P>Last updated: Tue Nov 22 10:17:05 EST 2005</P> |
|
|
|
|
<P>Last updated: Tue Nov 22 10:17:51 EST 2005</P> |
|
|
|
|
|
|
|
|
|
<P>Current maintainer: Bruce Momjian (<A href= |
|
|
|
|
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR> |
|
|
|
|
@ -984,7 +984,7 @@ |
|
|
|
|
Use a debugger to attach to the <I>postgres</I> <SMALL>PID</SMALL>. |
|
|
|
|
You can set breakpoints in the debugger and issue queries from the |
|
|
|
|
other. If you are looking to find the location that is generating |
|
|
|
|
an error or log message, set a breakpoint at <I>errfinish</>. |
|
|
|
|
an error or log message, set a breakpoint at <I>errfinish</I>. |
|
|
|
|
|
|
|
|
|
<I>psql</I>. If you are debugging <I>postgres</I> startup, you can |
|
|
|
|
set PGOPTIONS="-W n", then start <I>psql</I>. This will cause startup |
|
|
|
|
|