From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Claudio Freire <klaussfreire(at)gmail(dot)com>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Jan Wieck <jan(at)wi3ck(dot)info> |
Subject: | Re: open items for 9.4 |
Date: | 2014-09-29 20:05:28 |
Message-ID: | 20140929200528.GD2084@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2014-09-29 14:44:42 -0400, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > The items I see are:
>
> > - Remove xloginsert_slots/xloginsert_locks GUC - Not yet!!
>
> > The text seems to indicate that there's some disagreement on this
> > point. I don't have a strong opinion on whether or not to keep the
> > GUC, but if we're going to remove it it should probably happen before
> > beta3. It's going to be impossible to remove once we've released with
> > it, I suspect.
>
> The lack of any documentation for the GUC (neither in config.sgml or
> postgresql.conf.sample) suggests very very strongly that it was not
> meant to be shipped.
That's definitely the case.
> If we don't remove it I will certainly insist that it be documented
> adequately.
Definitely.
> Personally I think a hardwired #define should be plenty. What's the
> argument that users will need to tune this at runtime?
That right now it can make quite noticeable differences in
scalability. And we have not much data to justify 8 as the default. And
that's surely not going to change if we require recompiles.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2014-09-29 20:06:45 | Re: json (b) and null fields |
Previous Message | Andrew Dunstan | 2014-09-29 20:03:13 | Re: json (b) and null fields |