Gurjeet Singh <gurjeet@singh.im> writes:
> As it stands right now, a user can decrease the likelyhood of
> Postmaster being killed by adjusting the start script, but that
> decreases the likelyhood of al the child processes, too, making the
> Postmaster just as likely as a kill-candidate, maybe even higher
> because it's the parent, as any backend.
Exactly.
> This patch gives the user a control to let the backend's likelyhood of
> being killed be different/higher than that of the postmaster.
If you think your users might want to give the postmaster OOM-exemption,
why don't you just activate the existing code when you build? Resetting
the OOM setting to zero is safe whether or not the startup script did
anything to the postmaster's setting.
In short, I don't see what a GUC adds here, except uncertainty, which
is not a good thing.
regards, tom lane