Re: Issues with hash and GiST LP_DEAD setting for kill_prior_tuple

From: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Issues with hash and GiST LP_DEAD setting for kill_prior_tuple
Date: 2025-07-17 23:26:14
Message-ID: CADzfLwX8RSip6EVOw6+14hOgM+BZ3pXUFsRaAX24r_-0PGc6OA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, Peter!

> FWIW _hash_readpage has a comment about a stashed LSN, so it seems as
> if this was barely missed by the work on hash indexes around 2017:

I think commit 22c5e735 [0] (Remove lsn from HashScanPosData) is the
thing you are looking for in relation to hash.

Best regards,
Mikhail.

[0]: https://github.com/postgres/postgres/commit/22c5e73562c53437979efec4c26cd9fff408777c

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2025-07-17 23:34:55 Re: simple patch for discussion
Previous Message Fujii Masao 2025-07-17 23:16:29 Re: Log prefix missing for subscriber log messages received from publisher