]> granicus.if.org Git - postgresql/commit
hash: Immediately after a bucket split, try to clean the old bucket.
authorRobert Haas <rhaas@postgresql.org>
Fri, 4 Aug 2017 23:33:01 +0000 (19:33 -0400)
committerRobert Haas <rhaas@postgresql.org>
Fri, 4 Aug 2017 23:33:01 +0000 (19:33 -0400)
commitff98a5e1e49de061600feb6b4de5ce0a22d386af
tree9ceffad35527c7b3be5479dfcd2efec769f0e472
parent03378c4da598840b0520a53580dd7713c95f21c8
hash: Immediately after a bucket split, try to clean the old bucket.

If it works, then we won't be storing two copies of all the tuples
that were just moved.  If not, VACUUM will still take care of it
eventually.  Per a report from AP and analysis from Amit Kapila, it
seems that a bulk load can cause splits fast enough that VACUUM won't
deal with the problem in time to prevent bloat.

Amit Kapila; I rewrote the comment.

Discussion: http://postgr.es/m/20170704105728.mwb72jebfmok2nm2@zip.com.au
src/backend/access/hash/hashpage.c