Applied. I have added a note to check for file changes before signal
handler is installed in child.
---------------------------------------------------------------------------
Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > > Tom Lane wrote:
> > >> Where exactly is the interlock to ensure that the new backend will end up
> > >> with the correct settings if someone is changing the values at about
> > >> the time of the fork?
> >
> > > Postmaster creates a new file, then does rename() to move it to the name
> > > used by the backends. It can't move it until the file is not in use.
> >
> > And?
> >
> > How exactly does that guarantee that the new backend will see an update
> > occurring at about the same time? I'm pretty sure that GUC is fired up
> > before backends start listening to signals (and that's assuming the
> > Windows port has a Unixy idea of signal response, which I seem to recall
> > you telling me wasn't the case).
>
>
> Oh, I am not sure. I haven't gotten the signal stuff done yet.
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania 19073
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073