Jan Wieck <JanWieck@Yahoo.com> writes:
> If the user changes the config and HUP's the postmaster, postmaster
> rereads the config and merges only those changes, that are changable at
> runtime into it's status. From that status it creates the new file,
> renames, HUP's the backends and they reread that file.
That just moves any potential race conditions to another place, doesn't it?
How's reading this file any safer than reading postgresql.conf? If the
PM gets a second SIGHUP in quick succession, it could be rewriting the
intermediate file while backends are trying to read it.
regards, tom lane