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?
The relcache code has this problem solved, but I'm unconvinced that GUC
does.
regards, tom lane