Re: Preventing indirection for IndexPageGetOpaque for known-size page special areas

From: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Preventing indirection for IndexPageGetOpaque for known-size page special areas
Date: 2022-04-07 08:49:43
Message-ID: CALT9ZEFoowytECGUwRPG1XYTL-TXFseJ-HKMd2QmxPDtzdLxEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> On Fri, Apr 1, 2022 at 11:12 AM Matthias van de Meent
> <boekewurm+postgres(at)gmail(dot)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.

[1]
https://www.postgresql.org/message-id/flat/CACG%3DezZe1NQSCnfHOr78AtAZxJZeCvxrts0ygrxYwe%3DpyyjVWA%40mail.gmail.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2022-04-07 08:52:19 Re: Showing I/O timings spent reading/writing temp buffers in EXPLAIN
Previous Message Andres Freund 2022-04-07 08:36:30 Re: pgsql: Prefetch data referenced by the WAL, take II.