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

Re: Additional startup logging

From: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Additional startup logging
Date: 2010-07-01 02:43:51
Message-ID: 20100701114351.B04A.52131E4D@oss.ntt.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)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



In response to

Responses

pgsql-hackers by date

Next:From: Mark WongDate: 2010-07-01 03:24:18
Subject: Re: parallelizing subplan execution (was: explain and PARAM_EXEC)
Previous:From: Bruce MomjianDate: 2010-07-01 02:39:54
Subject: Re: Streaming Replication: Checkpoint_segment and wal_keep_segments on standby

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