pgsql: Improve handling of dead tuples in hash indexes.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Improve handling of dead tuples in hash indexes.
Date: 2016-11-08 15:53:24
Message-ID: E1c48iC-00069c-JH@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Improve handling of dead tuples in hash indexes.

When squeezing a bucket during vacuum, it's not necessary to retain
any tuples already marked as dead, so ignore them when deciding which
tuples must be moved in order to empty a bucket page. Similarly, when
splitting a bucket, relocating dead tuples to the new bucket is a
waste of effort; instead, just ignore them.

Amit Kapila, reviewed by me. Testing help provided by Ashutosh
Sharma.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/f0e72a25b05d4c29d0102fa0b892782ff193a00e

Modified Files
--------------
src/backend/access/hash/hashovfl.c | 4 ++++
src/backend/access/hash/hashpage.c | 4 ++++
2 files changed, 8 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-11-08 16:35:27 pgsql: Use heap_modify_tuple not SPI_modifytuple in pl/perl triggers.
Previous Message Amit Kapila 2016-11-08 12:23:42 Re: Re: [COMMITTERS] pgsql: Change the way that LWLocks for extensions are allocated.