On 21 May 2012 19:10, Josh Berkus <josh@agliodbs.com> wrote:
>
>> For these reasons, it may be timely and appropriate, from a purely
>> advocacy point-of-view, to call our new group commit "group commit" in
>> release notes and documentation, and announce it as a new feature.
>
> First, shouldn't we be having this discussion on -advocacy?
Well, no, because this is a specific discussion about release notes.
In any case, I've given up on the idea that we should market new group
commit as "group commit". I believe that that would be a useful and
fair way of representing the feature, but there doesn't seem to be any
support for that view.
In passing, I noticed this:
"""
E.1.3.12.2. pg_stat_statements
Improve pg_stat_statements to aggregate similar queries (Peter
Geoghegan, Tom Lane)
Improve pg_stat_statements' handling of PREPARE/EXECUTE statements (Tom Lane)
Add dirtied and written block counts to pg_stat_statements (Robert Haas)
"""
I think that the second entry should be listed as a bug fix, or a
compatibility note, rather than an actual feature. At the very least,
it should be listed after "Add dirtied and written block counts". I
also think that we should separately list as a feature
pg_stat_statements new ability to track I/O timings at the query
granularity.
Are we any closer to a list of major features?
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
