Re: Would it be possible to backpatch Close support in libpq (28b5726) to PG16? - Mailing list pgsql-hackers

From Joe Conway
Subject Re: Would it be possible to backpatch Close support in libpq (28b5726) to PG16?
Date
Msg-id 6e3df8df-0912-5a45-46bc-7fd5a0bcbfd7@joeconway.com
Whole thread Raw
In response to Re: Would it be possible to backpatch Close support in libpq (28b5726) to PG16?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List 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




pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: walsender "wakeup storm" on PG16, likely because of bc971f4025c (Optimize walsender wake up logic using condition variables)
Next
From: Thomas Munro
Date:
Subject: Re: Rename ExtendedBufferWhat in 16?