Re: Cleaning up nbtree after logical decoding on standby work

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Cleaning up nbtree after logical decoding on standby work
Date: 2023-05-26 08:56:53
Message-ID: 20230526085653.335teamdsktomn5e@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2023-May-25, Peter Geoghegan wrote:

> Attached patch completely removes the changes to _bt_getbuf()'s
> signature from 61b313e4.

I suppose you're not thinking of applying this to current master, but
instead just leave it for when pg17 opens, right? I mean, clearly it
seems far too invasive to put it in after beta1. On the other hand,
it's painful to know that we're going to have code that exists only on
16 and not any other release, in an area that's likely to have bugs here
and there, so we're going to need to heavily adjust backpatches for 16

I can't make up my mind about this. What do others think?

Álvaro Herrera PostgreSQL Developer —
"La primera ley de las demostraciones en vivo es: no trate de usar el sistema.
Escriba un guión que no toque nada para no causar daños." (Jakob Nielsen)

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2023-05-26 09:54:42 pg_get_indexdef() modification to use TxnSnapshot
Previous Message Daniel Gustafsson 2023-05-26 08:09:35 Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?