On Tue, Apr 25, 2017 at 2:45 PM, Bruce Momjian <br...@momjian.us> wrote: > On Tue, Apr 25, 2017 at 10:37:48AM -0700, Andres Freund wrote: >> On 2017-04-25 13:11:32 -0400, Bruce Momjian wrote: >> > I don't think this warrants inclusion in the release notes for reasons >> > already discussed. The vacuum truncation operation is a rare one and >> > an implementation detail. >> >> I think that's backwards. The truncate operation is quite delicate >> because it happens with AccessExclusiveLock held. This regularly does >> cause issues in production. When users look for things they possibly >> should update for, something like "performance improvents in final >> vacuum phase" + oneliner is going to be a lot more interesting than, >> say, "Add MONEY operators for multiplication and division with INT8 >> values". >> >> More and more users are going to be primarily interested in three >> classes of new things in postgres: 1) performance 2) replication 3) >> easier management. Arbitrarily excluding one of the major categories >> from release notes isn't a useful policy, especially if we continue to >> list new feature that'll effect no more than a handful of people. > > I disputed that my logic is arbitrary. However, given your > explanation, I have added the item: > > Improve speed of <command>VACUUM</>'s removal of trailing empty > heap pages (Alvaro Herrera)
That's enough for me, thanks. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
