Skip site navigation (1) Skip section navigation (2)

Re: server log files

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "EBIHARA, Yuichiro" <ebihara(at)iplocks(dot)co(dot)jp>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: server log files
Date: 2008-06-30 15:19:55
Message-ID: 28836.1214839195@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
"EBIHARA, Yuichiro" <ebihara(at)iplocks(dot)co(dot)jp> writes:
> 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.

You probably still want -l just to capture any error occuring during
server startup.  But once the log collector has started to run, nothing
more should get written to that file.

> 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

If the postmaster fails to start, you won't know why.

			regards, tom lane

In response to

Responses

pgsql-general by date

Next:From: Lennin CaroDate: 2008-06-30 15:27:31
Subject: Re: Query
Previous:From: Tom LaneDate: 2008-06-30 15:15:42
Subject: Re: freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group