From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Geoghegan <pg(at)heroku(dot)com> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: 9.3 release notes: move compatibility items into their own sect |
Date: | 2013-05-04 14:33:06 |
Message-ID: | 20130504143306.GC5631@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Fri, May 3, 2013 at 09:39:38PM -0700, Peter Geoghegan wrote:
> On Fri, May 3, 2013 at 6:11 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > 9.3 release notes: move compatibility items into their own section
>
> The commit_delay improvements should stay under performance, where I
> previously indicated they should be - it's clearly a notable new
> feature (commit_delay is way more effective now), as opposed to a
> tweak to the semantics of an existing feature. The fact that the
> behavior was changed could be separately noted, alongside the fact
> that Simon made commit_delay PGC_POSTMASTER (this is already
> separately noted anyway).
>
> Similarly, I think that this is a new feature that needs a separate
> compatibility note:
>
> Allow in-memory sorts to use their full memory allocation (Jeff Janes)
>
> It's possible that people were previously over-allocating memory to
> compensate for the server's former unwillingness to make full use of
> work_mem. You should specifically warn against that.
OK, I moved commit_delay back to performance, and moved in-memory sorts
up to compatibility.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-05-04 14:44:54 | pgsql: 9.3 release notes: adjustments |
Previous Message | Peter Geoghegan | 2013-05-04 04:39:38 | Re: pgsql: 9.3 release notes: move compatibility items into their own sect |