Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > The patch basically writes all modified GUC variables to a binary file
> > that can be read in by newly created exec'ed backends.
>
> 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.
> The relcache code has this problem solved, but I'm unconvinced that GUC
> does.
--
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
