From e6487cc4d79e3be58faffb1f73c8c1ba6aade6b5 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 9 Jun 2000 12:20:15 +0000 Subject: Update FAQ. --- doc/src/FAQ.html | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) (limited to 'doc/src/FAQ.html') diff --git a/doc/src/FAQ.html b/doc/src/FAQ.html index bc06aed60be..a71b00f90e3 100644 --- a/doc/src/FAQ.html +++ b/doc/src/FAQ.html @@ -719,16 +719,17 @@ more detailed information to be reported. The -d option takes a number that specifies the debug level. Be warned that high debug level values generate large log files.

-You can actually run the postgres backend from the command line, and -type your SQL statement directly. This is recommended only for -debugging purposes. Note that a newline terminates the query, not a -semicolon. If you have compiled with debugging symbols, you can use a -debugger to see what is happening. Because the backend was not started -from the postmaster, it is not running in an identical environment and -locking/backend interaction problems may not be duplicated.

- -Another method is to start psql in one window, then find the -PID of the postgres process used by +If the postmaster is not running, you can actually run the +postgres backend from the command line, and type your SQL statement +directly. This is recommended only for debugging purposes. Note +that a newline terminates the query, not a semicolon. If you have +compiled with debugging symbols, you can use a debugger to see what is +happening. Because the backend was not started from the postmaster, it +is not running in an identical environment and locking/backend +interaction problems may not be duplicated.

+ +If the postmaster is running, start psql in one window, +then find the PID of the postgres process used by psql. Use a debugger to attach to the postgres PID. You can set breakpoints in the debugger and issue queries from psql. If you are debugging postgres startup, -- cgit v1.2.3