| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, christoph(dot)berg(at)credativ(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error |
| Date: | 2022-06-10 19:47:09 |
| Message-ID: | 2713659.1654890429@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On June 11, 2022 1:12:11 AM GMT+09:00, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> In any case, I now agree with Robert's upthread objection that
>> this should not have been back-patched. It's a nontrivial
>> behavioral change and it's not clear that it's 100% without
>> downsides. I particularly do not want to ship 14.4 with this,
>> because we really need a clean release with no new regressions.
> Okay. An issue here is that I don't have my laptop at hand until 14.4 wraps, which would be around Monday morning my time. Could somebody do that instead?
OK, I can take care of it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-06-11 07:35:22 | Re: Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error |
| Previous Message | Michael Paquier | 2022-06-10 19:45:58 | Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error |