[COMMITTERS] pgsql: hash: Immediately after a bucket split,try to clean the old buc - Mailing list pgsql-committers

From Robert Haas
Subject [COMMITTERS] pgsql: hash: Immediately after a bucket split,try to clean the old buc
Date
Msg-id E1ddnMM-00082I-30@gemulon.postgresql.org
Whole thread Raw
Responses Re: [COMMITTERS] pgsql: hash: Immediately after a bucket split, tryto clean the old buc
List pgsql-committers
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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/ff98a5e1e49de061600feb6b4de5ce0a22d386af

Modified Files
--------------
src/backend/access/hash/hashpage.c | 45 ++++++++++++++++++++++++++++----------
1 file changed, 34 insertions(+), 11 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: First-draft release notes for 9.6.4.
Next
From: Peter Eisentraut
Date:
Subject: [COMMITTERS] pgsql: Only kill sync workers at commit time in subscription DDL