Re: Idea: closing the loop for "pg_ctl reload"

From: Jan de Visser <jan(at)de-visser(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Idea: closing the loop for "pg_ctl reload"
Date: 2015-03-03 23:24:51
Message-ID: 4075735.bDerbqPRc5@wolverine
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-03-03 23:53:20 Re: failures with tuplesort and ordered set aggregates (due to 5cefbf5a6c44)
Previous Message Stephen Frost 2015-03-03 23:22:11 Re: Proposal: knowing detail of config files via SQL