server log files - Mailing list pgsql-general

From EBIHARA, Yuichiro
Subject server log files
Date
Msg-id 8869dd0b0806300348h72d7f64u5dcd98a0750f2b28@mail.gmail.com
Whole thread Raw
Responses Re: server log files  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi Experts,

I'm using PostgreSQL 8.3.3 and have a question about log files that
PostgreSQL generates.

There are two ways to specify the log file path

1)pg_ctl start -l <filename>
http://www.postgresql.org/docs/8.3/interactive/app-pg-ctl.html

2)server configuration (postgresql.conf)
http://www.postgresql.org/docs/8.3/interactive/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHERE

I'm now considering the following settings in postgresql.conf.

log_destinatio = stderr
logging_collector = on
log_directory = 'pg_log'
log_filename = 'postgresql-%Y-%m-%d.log'
log_rotation_age = 1d
log_truncate_on_rotation = off

I just wonder whether I still should continue using 'pg_ctl start -l
<filename>' to keep useful information about PostgreSQL server status.

I tried enabling both of two log files but few messages were written
to the former one.
It seems only messages generated before those parameters are
recognized and ones generated by pg_ctl itself are written.
For instance, I can see some messages by issueing 'pg_ctl start' while
PostgreSQL is already up.

If all messages while PostgreSQL server is running are wrintten to the
file specified by log_directory and log_filename, I'd like to consider
to start up PostgreSQL as follows:
$pg_ctl start > /dev/null

Any comments or suggestions would be greatly appreciated.
Thanks in advance,

ebi

pgsql-general by date:

Previous
From: "Pavel Stehule"
Date:
Subject: Re: allowed variable names in functions?
Next
From: Karsten Hilbert
Date:
Subject: Re: allowed variable names in functions?