Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])

<p dir="ltr">Why isn't it enough to just dump out all variables with a source of alter system to a text file? You can
eitherhave a single global lock around that operation or write it to a new file and move it into place. <p dir="ltr">--
<br/> greg<div class="gmail_quote">On 1 Aug 2013 15:19, "Andres Freund" <<a
href="mailto:andres@2ndquadrant.com">andres@2ndquadrant.com</a>>wrote:<br type="attribution" /><blockquote
class="gmail_quote"style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On 2013-08-01 15:17:04 +0100,
GregStark wrote:<br /> > We don't need per guc locking. This is the whole objection Tom had about<br /> > this
patchbeing more complex than it has to be.<br /><br /> IIRC he objected to using locking *at all* because a simple<br
/>one-file-per-setting approach should be used.<br /><br /> Greetings,<br /><br /> Andres Freund<br /><br /> --<br />
 AndresFreund                     <a href="http://www.2ndQuadrant.com/"
target="_blank">http://www.2ndQuadrant.com/</a><br/>  PostgreSQL Development, 24x7 Support, Training & Services<br
/></blockquote></div>