Re: Preventing indirection for IndexPageGetOpaque for known-size page special areas - Mailing list pgsql-hackers

From Pavel Borisov
Subject Re: Preventing indirection for IndexPageGetOpaque for known-size page special areas
Date
Msg-id CALT9ZEFoowytECGUwRPG1XYTL-TXFseJ-HKMd2QmxPDtzdLxEA@mail.gmail.com
Whole thread Raw
In response to Re: Preventing indirection for IndexPageGetOpaque for known-size page special areas  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Fri, Apr 1, 2022 at 11:12 AM Matthias van de Meent
<boekewurm+postgres@gmail.com> wrote:
> Here's a new 0001 to keep CFBot happy.

This seems like it would conflict with the proposal from
http://postgr.es/m/CA+TgmoaD8wMN6i1mmuo+4ZNeGE3Hd57ys8uV8UZm7cneqy3W2g@mail.gmail.com
which I still hope to advance in some form at an appropriate time.
It may be weakly related to the current discussion, but I'd like to note that the other proposed patch for making XID's 64-bit [1] will store per-page-common xid data in the heap page special area. It doesn't contradict storing a nonce in this area also, but I'd appreciate it if we could avoid changing heap page special layout twice.


pgsql-hackers by date:

Previous
From: Pavel Luzanov
Date:
Subject: Re: How about a psql backslash command to show GUCs?
Next
From: Masahiko Sawada
Date:
Subject: Re: Showing I/O timings spent reading/writing temp buffers in EXPLAIN