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.
But I'm still wondering if the order of operations in SIGHUP_handler is
wrong.
regards, tom lane
