| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Jelte Fennema <postgres(at)jeltef(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: Would it be possible to backpatch Close support in libpq (28b5726) to PG16? |
| Date: | 2023-08-16 23:20:09 |
| Message-ID: | 6e3df8df-0912-5a45-46bc-7fd5a0bcbfd7@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/15/23 15:39, Alvaro Herrera wrote:
> On 2023-Aug-16, Michael Paquier wrote:
>
>>> Personally I think backpatching 28b5726 has a really low risk of
>>> breaking anything.
>>
>> I agree about the low-risk argument, though. This is just new code.
>
> Here's a way to think about it. If 16.1 was already out, would we add
> libpq support for Close to 16.2?
Seems pretty clearly a "no" to me.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-08-16 23:31:27 | Re: Rename ExtendedBufferWhat in 16? |
| Previous Message | Thomas Munro | 2023-08-16 22:58:45 | Re: walsender "wakeup storm" on PG16, likely because of bc971f4025c (Optimize walsender wake up logic using condition variables) |