Tom Lane wrote:
>
> I said:
> > That way the file never changes after postmaster start and there can
> > be no race condition. Children will instead have to read
> > postgresql.conf for themselves during their launch (after they read the
> > nondefault_variables file), but that's an easy one-line addition.
>
> On second thought, that just moves the race condition upstream (to the
> person editing postgresql.conf) ... so never mind that idea. We don't
> want any part of Postgres reading postgresql.conf except shortly after
> someone has SIGHUP'd the postmaster.
I didn't actually look at that part of the code yet ... why would any
backend read postgresql.conf? I thought only the postmaster does that
and that he SIGHUP's all backends after writing the new file. That way
there is not race condition other that hupping the PM while w'ing the
file.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
