<div dir="ltr"><br /><div class="gmail_extra"><br /><div class="gmail_quote">On Tue, Sep 30, 2014 at 3:44 AM, Tom Lane
<spandir="ltr"><<a href="mailto:tgl@sss.pgh.pa.us" target="_blank">tgl@sss.pgh.pa.us</a>></span> wrote:<br
/><blockquoteclass="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">RobertHaas <<a href="mailto:robertmhaas@gmail.com">robertmhaas@gmail.com</a>> writes:<br /> > The
itemsI see are:<br /><br /> > - Remove xloginsert_slots/xloginsert_locks GUC - Not yet!!<br /><br /> > The text
seemsto indicate that there's some disagreement on this<br /> > point. I don't have a strong opinion on whether or
notto keep the<br /> > GUC, but if we're going to remove it it should probably happen before<br /> > beta3. It's
goingto be impossible to remove once we've released with<br /> > it, I suspect.<br /><br /></span>The lack of any
documentationfor the GUC (neither in config.sgml or<br /> postgresql.conf.sample) suggests very very strongly that it
wasnot<br /> meant to be shipped. If we don't remove it I will certainly insist<br /> that it be documented
adequately.<br/><br /> Personally I think a hardwired #define should be plenty. What's the<br /> argument that users
willneed to tune this at runtime?<br /></blockquote></div>I tend to go in this direction too. It is unclear how it is
reallyable to improve scalability, or at least some documentation should be here to help users to set it. An additional
thoughtas well: set it with a configure switch at compilation instead of a GUC.<br />-- <br />Michael<br /></div></div>
