On Tue, Apr 25, 2017 at 9:15 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Andres Freund <and...@anarazel.de> writes: >> On 2017-04-24 23:37:42 -0400, Bruce Momjian wrote: >>> I remember seeing those and those are normally details I do not put in >>> the release notes as there isn't a clear user experience change except >>> "Postgres is faster". Yeah, a bummer, and I can change my filter, but >>> it would require discussion. > >> I think "postgres is faster" is one of the bigger user demands, so I >> don't think that policy makes much sense. A large number of the changes >> over the next few releases will focus solely on that. Nor do I think >> past release notes particularly filtered such changes out. > > I think it has been pretty common to accumulate a lot of such changes > into generic entries like, say, "speedups for hash joins". More detail > than that simply isn't useful to end users; and as a rule, our release > notes are too long anyway. > > regards, tom lane > > Just wondering if the mention of commit 0414b26bac09379a4cbf1fbd847d1cee2293c5e4 is missed? Not sure if this requires a separate entry or could be merged with -- Support parallel btree index scans.
-- Regards, Rafia Sabih EnterpriseDB: http://www.enterprisedb.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
