| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: pgsql: libpq: Grease the protocol by default |
| Date: | 2026-02-23 23:34:42 |
| Message-ID: | 3635497.1771889682@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
> On Mon, Feb 23, 2026 at 2:18 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Either that or we decide that it's time to throw 9.2 support
>> overboard (looks like 9.3 and up are fine).
> Well, while I was hacking on a patch I realized that 9.3 (all the way
> up to 10) is only okay if you're running a sufficiently patched
> version. PG11 is the first to support negotiation for the whole
> release line.
Hmm ... and of course the whole point of this exercise is to be sure
we can pg_upgrade from those out-of-support versions.
> I think Jelte said it well back on the -committers thread:
>> Why only force max_protocol_version=3.0 for beta? It sounds like
>> this would also be an issue once we eventually bump the default
>> version.
> So a fix belongs in pg_upgrade, IMO, instead of the test. I have a
> draft passing locally that I should be able to share soon.
Fair enough.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2026-02-23 23:41:46 | Re: pgsql: libpq: Grease the protocol by default |
| Previous Message | Jacob Champion | 2026-02-23 22:51:46 | Re: pgsql: libpq: Grease the protocol by default |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2026-02-23 23:41:46 | Re: pgsql: libpq: Grease the protocol by default |
| Previous Message | Michael Paquier | 2026-02-23 23:20:11 | Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists |