Re: Idea: closing the loop for "pg_ctl reload" - Mailing list pgsql-hackers

From Jan de Visser
Subject Re: Idea: closing the loop for "pg_ctl reload"
Date
Msg-id 4075735.bDerbqPRc5@wolverine
Whole thread Raw
In response to Re: Idea: closing the loop for "pg_ctl reload"  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On March 3, 2015 04:57:58 PM Jim Nasby wrote:
> On 3/3/15 11:48 AM, Andres Freund wrote:
> >  I'm saying that you'll need a way to notice that a reload was processed
>  > or not. And that can't really be the message itself, there has to be
>  > some other field; like the timestamp Tom proposes.
> 
> Ahh, right. We should make sure we don't go brain-dead if the system 
> clock moves backwards. I assume we couldn't just fstat the file...

The timestamp field is already there (in my patch). It gets populated when the 
server starts and repopulated by SIGHUP_handler. It's the only timestamp 
pg_ctl pays attention to.




pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Proposal: knowing detail of config files via SQL
Next
From: Robert Haas
Date:
Subject: Re: failures with tuplesort and ordered set aggregates (due to 5cefbf5a6c44)