From: | Jan de Visser <jan(at)de-visser(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu> |
Subject: | Re: Idea: closing the loop for "pg_ctl reload" |
Date: | 2015-03-05 01:13:27 |
Message-ID: | 2386901.4C9dO1OPCO@wolverine |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On March 4, 2015 11:08:09 PM Andres Freund wrote:
> Let's get the basic feature (notification of failed reloads) done
> first. That will be required with or without including the error
> message. Then we can get more fancy later, if somebody really wants to
> invest the time.
Except for also fixing pg_reload_conf() to pay attention to what happens with
postmaster.pid, the patch I submitted does exactly what you want I think.
And I don't mind spending time on stuff like this. I'm not smart enough to deal
with actual, you know, database technology.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2015-03-05 01:18:17 | INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0 |
Previous Message | Peter Geoghegan | 2015-03-05 00:50:30 | a2e35b53 added unused variable to ConversionCreate() |