Re: Additional startup logging - Mailing list pgsql-hackers

From Takahiro Itagaki
Subject Re: Additional startup logging
Date
Msg-id 20100701114351.B04A.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Additional startup logging  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Additional startup logging
List pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote:

> It seems potentially useful to LOG the version() string in the log
> file during startup.  It might also help to LOG any settings which
> might result in the loss of committed transactions or in database
> corruption during startup.  (After a crash, the postgresql.conf file
> might not show the values which were in effect during startup, and
> it is too late to "show" the values.)

I think such logs depends on purposes, so they should be customizable.

You could write a module, that is registered in 'shared_preload_libraries'
and logs internal information you want from _PG_init() or shmem_startup_hook.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Streaming Replication: Checkpoint_segment and wal_keep_segments on standby
Next
From: Michael Glaesemann
Date:
Subject: Re: Additional startup logging