<p dir="ltr"><br /> El mar 21, 2015 2:00 AM, "Mark Kirkwood" <<a
href="mailto:mark.kirkwood@catalyst.net.nz">mark.kirkwood@catalyst.net.nz</a>>escribió:<br /> ><br /> > On
21/03/1519:28, Jaime Casanova wrote:<br /> >><br /> >> what about not removing it but not showing it in
postgresql.conf?as a<br /> >> side note, i wonder why trace_sort is not in postgresql.conf...<br /> >>
otheroption is to make it a compile setting, that why if you want to<br /> >> have it you need to compile and
postgres'developers do that routinely<br /> >> anyway<br /> >><br /> ><br /> > -1<br /> ><br />
>Personally I'm against hiding *any* settings. Choosing sensible defaults - yes! Hiding them - that reeks of secret
squirrelnonsense and overpaid Oracle dbas that knew the undocumented settings for various capabilities. I think/hope
thatno open source project will try to emulate that meme!<br /> ><p dir="ltr">That ship has already sailed.<p
dir="ltr"><a
href="http://www.postgresql.org/docs/9.4/static/runtime-config-developer.html">http://www.postgresql.org/docs/9.4/static/runtime-config-developer.html</a><p
dir="ltr">--<br/> Jaime Casanova<br /> 2ndQuadrant Consultant<br /> Your PostgreSQL partner