Re: Cleaning up nbtree after logical decoding on standby work
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Peter Geoghegan <pg@bowt.ie>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>, Andres Freund <andres@anarazel.de>
Date: 2023-05-26T07:46:31Z
Lists: pgsql-hackers
On Thu, May 25, 2023 at 06:50:31PM -0700, Peter Geoghegan wrote:
> It's possible that Bertand would have done it this way to begin with
> were it not for the admittedly pretty bad nbtree convention around
> P_NEW. It would be nice to get rid of P_NEW in the near future, too --
> I gather that there was discussion of that in the context of recent
> work in this area.
Nice cleanup overall.
+ if (XLogStandbyInfoActive() && RelationNeedsWAL(rel))
{
- /* Okay to use page. Initialize and return it. */
- _bt_pageinit(page, BufferGetPageSize(buf));
- return buf;
+ safexid = BTPageGetDeleteXid(page);
+ isCatalogRel = RelationIsAccessibleInLogicalDecoding(heaprel);
+ _bt_log_reuse_page(rel, blkno, safexid, isCatalogRel);
There is only one caller of _bt_log_reuse_page(), so assigning a
boolean rather than the heap relation is a bit strange to me. I think
that calling RelationIsAccessibleInLogicalDecoding() within
_bt_log_reuse_page() where xlrec_reuse is filled with its data is much
more natural, like HEAD. One argument in favor of HEAD is that it is
not possible to pass down a wrong value for isCatalogRel, but your
patch would make that possible.
--
Michael
Commits
-
nbtree: Allocate new pages in separate function.
- d088ba5a5aa4 16.0 landed
-
Pass down table relation into more index relation functions
- 61b313e47eb9 16.0 cited
-
Note case where nbtree VACUUM finishes splits.
- 35bc0ec7c800 12.0 cited
-
Fix interaction between CREATE INDEX and "snapshot too old".
- bf9a60ee3349 9.6.0 cited