From: Bruce Momjian
Date: Mon, 31 Jan 2005 22:57:17 +0000 (+0000)
Subject: Restructure debug FAQ entry.
X-Git-Tag: REL8_1_0BETA1~1438
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d96398d1eb97fc3d18fb8f80b1ea09dd0af59489;p=postgresql
Restructure debug FAQ entry.
---
diff --git a/doc/FAQ b/doc/FAQ
index 2fe694b717..2fe1359356 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Mon Jan 31 15:40:24 EST 2005
+ Last updated: Mon Jan 31 17:57:02 EST 2005
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@@ -383,24 +383,20 @@
3.4) What debugging features are available?
- PostgreSQL has several features that report status information that
- can be valuable for debugging purposes.
+ There are many log_* server configuration variables that enable
+ printing of query and process statistics which can be very useful for
+ debugging and performance measurements.
- First, by running configure with the --enable-cassert option, many
- assert()s monitor the progress of the backend and halt the program
- when something unexpected occurs.
+ The following detailed debug instructions are to be used to provide
+ more detailed information for server developers debugging a problem
- Both postmaster and postgres have several debug options available.
- First, whenever you start postmaster, make sure you send the standard
- output and error to a log file, like:
- cd /usr/local/pgsql
- ./bin/postmaster >server.log 2>&1 &
-
- This will put a server.log file in the top-level PostgreSQL directory.
- This file contains useful information about problems or errors
- encountered by the server. Postmaster has a -d option that allows even
- more detailed information to be reported. The -d option takes a number
- that specifies the debug level. Be warned that high debug level values
+ It is also possible to debug the server if it isn't operating
+ properly. First, by running configure with the --enable-cassert
+ option, many assert()s monitor the progress of the backend and halt
+ the program when something unexpected occurs.
+ The postmaster has a -d option that allows even 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.
If postmaster is not running, you can actually run the postgres
@@ -421,10 +417,6 @@
process with the debugger, set any breakpoints, and continue through
the startup sequence.
- There are several log_* server configuration variables that enable
- printing of process statistics which can be very useful for debugging
- and performance measurements.
-
You can also compile with profiling to see what functions are taking
execution time. The backend profile files will be deposited in the
pgsql/data/base/dbname directory. The client profile file will be put
diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index 8ea5f32443..9c723943b1 100644
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -10,7 +10,7 @@
alink="#0000ff">
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Mon Jan 31 15:40:24 EST 2005
+ Last updated: Mon Jan 31 17:57:02 EST 2005
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@@ -519,29 +519,23 @@
3.4) What debugging features are
available?
- PostgreSQL has several features that report status information
- that can be valuable for debugging purposes.
+ There are many log_*
server configuration variables
+ that enable printing of query and process statistics which can be
+ very useful for debugging and performance measurements.
- First, by running configure with the --enable-cassert
+
The following detailed debug instructions are to be used to
+ provide more detailed information for server developers debugging a
+ problem
+
+ It is also possible to debug the server if it isn't operating
+ properly. First, by running configure with the --enable-cassert
option, many assert()s monitor the progress of the backend
and halt the program when something unexpected occurs.
- Both postmaster and postgres have several debug
- options available. First, whenever you start postmaster,
- make sure you send the standard output and error to a log file,
- like:
-
- cd /usr/local/pgsql
- ./bin/postmaster >server.log 2>&1 &
-
-
- This will put a server.log file in the top-level PostgreSQL
- directory. This file contains useful information about problems or
- errors encountered by the server. Postmaster has a -d
- option that allows even 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.
+ The postmaster has a -d option that allows even 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.
If postmaster is not running, you can actually run the
postgres backend from the command line, and type your
@@ -565,10 +559,6 @@
the debugger, set any breakpoints, and continue through the startup
sequence.
- There are several log_*
server configuration variables
- that enable printing of process statistics which can be very useful
- for debugging and performance measurements.
-
You can also compile with profiling to see what functions are
taking execution time. The backend profile files will be deposited
in the pgsql/data/base/dbname directory. The client profile