Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitd96398d

Browse files
committed
Restructure debug FAQ entry.
1 parent1f7aa64 commitd96398d

File tree

2 files changed

+27
-45
lines changed

2 files changed

+27
-45
lines changed

‎doc/FAQ‎

Lines changed: 13 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated: Mon Jan 3115:40:24 EST 2005
4+
Last updated: Mon Jan 3117:57:02 EST 2005
55

66
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
77

@@ -383,24 +383,20 @@
383383

384384
3.4) What debugging features are available?
385385

386-
PostgreSQL has several features that report status information that
387-
can be valuable for debugging purposes.
386+
There are many log_* server configuration variables that enable
387+
printing of query and process statistics which can be very useful for
388+
debugging and performance measurements.
388389

389-
First, by running configure with the --enable-cassert option, many
390-
assert()s monitor the progress of the backend and halt the program
391-
when something unexpected occurs.
390+
The following detailed debug instructions are to be used to provide
391+
more detailed information for server developers debugging a problem
392392

393-
Both postmaster and postgres have several debug options available.
394-
First, whenever you start postmaster, make sure you send the standard
395-
output and error to a log file, like:
396-
cd /usr/local/pgsql
397-
./bin/postmaster >server.log 2>&1 &
398-
399-
This will put a server.log file in the top-level PostgreSQL directory.
400-
This file contains useful information about problems or errors
401-
encountered by the server. Postmaster has a -d option that allows even
402-
more detailed information to be reported. The -d option takes a number
403-
that specifies the debug level. Be warned that high debug level values
393+
It is also possible to debug the server if it isn't operating
394+
properly. First, by running configure with the --enable-cassert
395+
option, many assert()s monitor the progress of the backend and halt
396+
the program when something unexpected occurs.
397+
The postmaster has a -d option that allows even more detailed
398+
information to be reported. The -d option takes a number that
399+
specifies the debug level. Be warned that high debug level values
404400
generate large log files.
405401

406402
If postmaster is not running, you can actually run the postgres
@@ -421,10 +417,6 @@
421417
process with the debugger, set any breakpoints, and continue through
422418
the startup sequence.
423419

424-
There are several log_* server configuration variables that enable
425-
printing of process statistics which can be very useful for debugging
426-
and performance measurements.
427-
428420
You can also compile with profiling to see what functions are taking
429421
execution time. The backend profile files will be deposited in the
430422
pgsql/data/base/dbname directory. The client profile file will be put

‎doc/src/FAQ/FAQ.html‎

Lines changed: 14 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
alink="#0000ff">
1111
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
1212

13-
<P>Last updated: Mon Jan 3115:40:24 EST 2005</P>
13+
<P>Last updated: Mon Jan 3117:57:02 EST 2005</P>
1414

1515
<P>Current maintainer: Bruce Momjian (<Ahref=
1616
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
@@ -519,29 +519,23 @@ <H4><A name="3.3">3.3</A>) How do I tune the database engine for
519519
<H4><Aname="3.4">3.4</A>) What debugging features are
520520
available?</H4>
521521

522-
<P>PostgreSQL has several features that report status information
523-
that can be valuable for debugging purposes.</P>
522+
<P>There are many<CODE>log_*</CODE> server configuration variables
523+
that enable printing of query and process statistics which can be
524+
very useful for debugging and performance measurements.</P>
524525

525-
<P>First, by running<I>configure</I> with the --enable-cassert
526+
<P><B>The following detailed debug instructions are to be used to
527+
provide more detailed information for server developers debugging a
528+
problem<B></P>
529+
530+
<P>It is also possible to debug the server if it isn't operating
531+
properly. First, by running<I>configure</I> with the --enable-cassert
526532
option, many<I>assert()</I>s monitor the progress of the backend
527533
and halt the program when something unexpected occurs.</P>
528534

529-
<P>Both<I>postmaster</I> and<I>postgres</I> have several debug
530-
options available. First, whenever you start<I>postmaster</I>,
531-
make sure you send the standard output and error to a log file,
532-
like:</P>
533-
<PRE>
534-
cd /usr/local/pgsql
535-
./bin/postmaster &gt;server.log 2&gt;&amp;1 &amp;
536-
</PRE>
537-
538-
<P>This will put a server.log file in the top-level PostgreSQL
539-
directory. This file contains useful information about problems or
540-
errors encountered by the server.<I>Postmaster</I> has a<I>-d</I>
541-
option that allows even more detailed information to be reported.
542-
The<I>-d</I> option takes a number that specifies the debug level.
543-
Be warned that high debug level values generate large log
544-
files.</P>
535+
The<I>postmaster</I> has a<I>-d</I> option that allows even more
536+
detailed information to be reported. The<I>-d</I> option takes a
537+
number that specifies the debug level. Be warned that high debug
538+
level values generate large log files.</P>
545539

546540
<P>If<I>postmaster</I> is not running, you can actually run the
547541
<I>postgres</I> backend from the command line, and type your
@@ -565,10 +559,6 @@ <H4><A name="3.4">3.4</A>) What debugging features are
565559
the debugger, set any breakpoints, and continue through the startup
566560
sequence.</P>
567561

568-
<P>There are several<CODE>log_*</CODE> server configuration variables
569-
that enable printing of process statistics which can be very useful
570-
for debugging and performance measurements.</P>
571-
572562
<P>You can also compile with profiling to see what functions are
573563
taking execution time. The backend profile files will be deposited
574564
in the<I>pgsql/data/base/dbname</I> directory. The client profile

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp