Magnus Hagander wrote:
>The difference is that if the other admin edited it in vi *last week* it
>will still break with your way, unless every admin always rembers to do
>load_pg_hba() before doing *anything at all*.
What if you send patches over the wire rather than the whole or
subsets of the file. You could make the patching fail if anything
doesn't match and force the client to re-diff the file and send a
new patch if it doesn't match exactly.
Quite a large increase in complexity, but at least the window of
opportunity that it has to go wrong would be vastly reduced. Plus
you can do whatever operating specific locking on the file is
appropiate while the update is in progress without needing to expose
anything to the client.
This is sounding more like a job for something external to Postgres
and you just need some way of telling Postgres that it needs to
reload the appropiate config file though.
Sam