Re: pgsql: Refactor ChangeVarNodesExtended() using the custom callback

From: Aleksander Alekseev <aleksander(at)timescale(dot)com>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Alexander Korotkov <akorotkov(at)postgresql(dot)org>
Subject: Re: pgsql: Refactor ChangeVarNodesExtended() using the custom callback
Date: 2025-05-07 08:59:29
Message-ID: CAJ7c6TMR2+_Dkr2riUpnA9N+p0y-jfeLvxfosaw+cR6hQ_BoOw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Hi,

> > I believe this was pushed by mistake.
>
> Why it should be mistake this time?
> At least, this time I managed to wait till the end of release freeze.

Perhaps I misunderstand something in the process. How one will tag
REL_18_BETA2 or fork REL_18_STABLE considering that the `master`
branch contains this commit or others?

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2025-05-07 09:06:22 Re: pgsql: Add function to log the memory contexts of specified backend pro
Previous Message Alexander Korotkov 2025-05-07 08:51:06 Re: pgsql: Refactor ChangeVarNodesExtended() using the custom callback