Horton

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

Pavel Borisov <pashkin.elfe@gmail.com>

View thread View on postgr.es
From: Pavel Borisov <pashkin.elfe@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>, Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2022-04-07T08:49:43Z
Lists: 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.

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

Commits

  1. Add macros in hash and btree AMs to get the special area of their pages

  2. Make WAL segment size configurable at initdb time.