<div dir="ltr"><span>There are quite a few GUC parameters that need restart. Is there a way we can avoid some of them
needingrestart? I am specifically looking at archive_mode and the new wal_level. <br /><br />From my limited
understanding,these parameters need restart because in a running cluster we cannot safely change these GUCs and make
surethat other/running backends will pick them up immediately so that they start behaving differently as required by
theGUC</span>.<br /><br />Are there other reasons to have them set to PGC_POSTMASTER?<br /><br />If the above is
correctand the only reason, then can we have them assigned to a new PGC_ mode and have the SET commands somehow wait
forall backends to pickup the value before returning? (specifically, wait for any running backends to exit the
transaction).<br/><br />I know there are genuine reasons behind having them depend on restart, but am just trying to
eliminatethat, at least for some parameters which a DBA might want to change on the fly, being fully aware of the
consequences.<br/><br />Regards,<br />-- <br />gurjeet.singh<br />@ EnterpriseDB - The Enterprise Postgres Company<br
/><ahref="http://www.enterprisedb.com">http://www.enterprisedb.com</a><br /><br />singh.gurjeet@{ gmail | yahoo
}.com<br/>Twitter/Skype: singh_gurjeet<br /><br />Mail sent from my BlackLaptop device<br /></div>