DEBUG output w/o debug set - Mailing list pgsql-hackers

<p><font size="2">I've recently installed Postgres 7.2, but this also applied to the 7.1.3 installation I had too. I'm
seeinga lot of DEBUG messages being output to the logfile/syslog, both when PG starts and stops, and also during VACUUM
ANALYZEruns (w/o verbose mode turned on); I start/stop PG via something like:</font><p><font size="2">su -l $PGUSER -c
"pg_ctlstart -D '$PGDATA' -s -l $PGLOG"</font><p><font size="2">and the analyze runs are done from cron like
so:</font><p><fontsize="2">su -l $PGUSER -c "/usr/local/pgsql/bin/vacuumdb --all --analyze"</font><p><font size="2">In
postgresql.conf,the relevant section looks like:</font><br /><font size="2">---</font><br /><font size="2"># Debug
display</font><br/><font size="2">#silent_mode = false</font><br /><font size="2">log_connections = true</font><br
/><fontsize="2">log_timestamp = true</font><br /><font size="2">log_pid = true</font><br /><font size="2">#debug_level
=0 # range 0-16</font><br /><font size="2">#debug_print_query = false</font><br /><font size="2">#debug_print_parse =
false</font><br/><font size="2">#debug_print_rewritten = false</font><br /><font size="2">#debug_print_plan =
false</font><br/><font size="2">#debug_pretty_print = false</font><br /><font size="2"># requires
USE_ASSERT_CHECKING</font><br/><font size="2">#debug_assertions = true</font><br /><font size="2">---</font><p><font
size="2">whichto mean says that there shouldn't be much debug output (level=0); I'm OK with the connection messages.
I'veattached some examples of the messages below if they're helpful. Is this something I have done, or something I can
turnoff? Its mainly the analyze lines that fill the log up. I'd have a quick grep at the code for DEBUG's but I'll have
towait till I get home.</font><p><font size="2">Cheers,</font><br /><font size="2">Joe</font><p><font size="2">-- DEBUG
examples:</font><p><fontsize="2">Feb 12 17:13:40 www postgres[32308]: [1] DEBUG:  smart shutdown request</font><br
/><fontsize="2">Feb 12 17:13:40 www postgres[32375]: [2] DEBUG:  shutting down</font><br /><font size="2">Feb 12
17:13:42www postgres[32375]: [3] DEBUG:  database system is shut down</font><br /><font size="2">Feb 12 17:14:01 www
postgres[32398]:[1] DEBUG:  database system was shut down at 2002-02-12 17:13:42 EST</font><br /><font size="2">Feb 12
17:14:01www postgres[32398]: [2] DEBUG:  checkpoint record is at 0/2CA848</font><br /><font size="2">Feb 12 17:14:01
wwwpostgres[32398]: [3] DEBUG:  redo record is at 0/2CA848; undo record is at 0/0; shutdown TRUE</font><br /><font
size="2">Feb12 17:14:01 www postgres[32398]: [4] DEBUG:  next transaction id: 1795; next oid: 16557</font><br /><font
size="2">Feb12 17:14:01 www postgres[32398]: [5] DEBUG:  database system is ready</font><br /><font size="2">Feb 12
17:14:08www postgres[32410]: [1] DEBUG:  connection: host=[local] user=postgres database=template1</font><br /><font
size="2">Feb12 17:14:08 www postgres[32412]: [1] DEBUG:  connection: host=[local] user=postgres
database=postgres</font><br/><font size="2">Feb 12 17:14:08 www postgres[32412]: [2] DEBUG:  --Relation
pg_type--</font><br/><font size="2">Feb 12 17:14:08 www postgres[32412]: [3-1] DEBUG:  Pages 2: Changed 0, Empty 0; Tup
143:Vac 0, Keep 0, UnUsed 1.</font><br /><font size="2">Feb 12 17:14:08 www postgres[32412]: [3-2]      Total CPU
0.00s/0.00usec elapsed 0.00 sec.</font><br /><font size="2">Feb 12 17:14:08 www postgres[32412]: [4] DEBUG:  Analyzing
pg_type</font><br/><font size="2">Feb 12 17:14:08 www postgres[32412]: [5] DEBUG:  --Relation pg_attribute--</font><br
/><fontsize="2">Feb 12 17:14:08 www postgres[32412]: [6-1] DEBUG:  Pages 11: Changed 0, Empty 0; Tup 795: Vac 0, Keep
0,UnUsed 21.</font><br /><font size="2">Feb 12 17:14:08 www postgres[32412]: [6-2]      Total CPU 0.00s/0.00u sec
elapsed0.00 sec.</font><br /><font size="2">Feb 12 17:14:08 www postgres[32412]: [7] DEBUG:  Analyzing
pg_attribute</font><br/><font size="2">Feb 12 17:14:08 www postgres[32412]: [8] DEBUG:  --Relation pg_class--</font><br
/><fontsize="2">...</font><code><font size="3"><br /><br /> ***********Confidentiality/Limited Liability
Statement***************<br/><br /> Have the latest business news and in depth analysis delivered to your <br />
desktop.Subscribe to "Insights", Deloitte's fortnightly email <br /> business bulletin . . . <br /><br />
http://www.deloitte.com.au/preferences/preference.asp<br/><br /> This message contains privileged and confidential
informationintended<br /> only for the use of the addressee named above. If you are not the <br /> intended recipient
ofthis message, you must not disseminate, copy or <br /> take any action in reliance on it. If you have received this
message<br /> in error, please notify Deloitte Touche Tohmatsu immediately. Any <br /> views expressed in this message
arethose of the individual sender, <br /> except where the sender specifically states them to be the views of <br />
Deloitte.<br/><br /> The liability of Deloitte Touche Tohmatsu, is limited by, and to the <br /> extent of, the
Accountants'Scheme under the Professional Standards <br /> Act 1994 (NSW).<br /><br /> The sender cannot guarantee that
thisemail or any attachment to it is free of computer viruses or other conditions which may damage or<br /> interfere
withdata, hardware or software with which it might be used. It is sent on the strict condition that the user carries
outand relies<br /> on its own procedures for ensuring that its use will not interfere with the recipients systems and
therecipient assumes all risk of use and<br /> absolves the sender of all responsibility for any consequence of its
use.<br/></font></code>