| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org, Alexander Korotkov <akorotkov(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Refactor ChangeVarNodesExtended() using the custom callback |
| Date: | 2025-05-07 09:33:36 |
| Message-ID: | CAPpHfdsTOxhkvwVGhXEHBY4DK+yJWA3M0V6sYjrtcstOTDYrpw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Hi, Aleksander!
On Wed, May 7, 2025 at 11:59 AM Aleksander Alekseev
<aleksander(at)timescale(dot)com> wrote:
> > > 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?
How can this or other commits on master branch prevent creating new
tag REL_18_BETA2 or forking REL_18_STABLE from master? Perhaps, this
commit is not the only one on master branch after tag REL_18_BETA1.
------
Regards,
Alexander Korotkov
Supabase
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2025-05-07 09:47:41 | Re: pgsql: Refactor ChangeVarNodesExtended() using the custom callback |
| Previous Message | Fujii Masao | 2025-05-07 09:06:22 | Re: pgsql: Add function to log the memory contexts of specified backend pro |