| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Draft back-branch release notes are up |
| Date: | 2026-11-09 06:04:12 |
| Message-ID: | CAA4eK1LEtMV_qY3bySpUnFwWe6cKiuuvx4O1S=d=r0Uq+1f+BQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 9, 2026 at 11:11 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
> > On Sun, Nov 8, 2026 at 9:37 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> Hmph. I read that and I was like "so what?". Why would users need
> >> to know that? How likely is it that anyone would issue such a
> >> combined command in the first place?
>
> > I agree that it is less likely for users to use such a combination and
> > even if they use I don't think it is a big deal. We can leave
> > mentioning anything about such a combination.
>
> To be clear, that was an honest request for information. I don't
> understand why this point is worth space in the release notes.
> But if you think it is, educate me. We still have a little time
> to adjust the notes ...
>
This was an unintended behavior (resetting slot's two_phase property
when user tries to mark two_phase for a subscription where two_phase
was already set) which was previously working and has the risk of the
same bugs as noted in the commit message. I don't know if in practice
any one would be using such a combination, so it is not clear to me if
there is a need to mention it in release notes. We can wait and see if
Bertrand has any thoughts on the same.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ruohang Feng | 2026-11-09 06:09:50 | Re: Credits For v19 |
| Previous Message | Xuneng Zhou | 2026-11-09 06:04:03 | Re: BGWORKER_INTERRUPTIBLE workers are never restarted after DROP/ALTER/CREATE DATABASE |