| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta |
| Date: | 2026-02-18 23:27:14 |
| Message-ID: | CAOYmi+m9dLWzY8=LQRrGiijdwyGVLZf1QCP1H2S1ghuen_LxbA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 18, 2026 at 3:11 PM Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
> I tried it out with PgBouncer commit f7ffd67ed8 (the one right before
> NegotiateProtocolVersion support was added) and got the following back
> with psql. So yes it works:
Cool! Thank you for testing that.
> I think "_pq_." would be very unlikely to cause false positives too
> *currently*, because it's the only protocol extension we're currently
> requesting. But I'm not sure that will remain true after we actually
> add support for some extensions (e.g. the error could be about an
> invalid option being used for a valid protocol extension). So I'd say
> let's stay on the "we're sure it's a bug" side and not use it as a
> heuristic.
Yeah, that makes sense. I plan to commit a squashed version of v8,
then, and if we think of improvements then we can always make them.
> I still have some not so secret hope that you (or another
> committer) will have time to look at my GoAway patch and realise it's
> pretty trivial and safe to commit.
(I will probably not be able to for the PG19 cycle.)
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2026-02-18 23:33:58 | DOCS QUESTION - space added within synopsis replaceable tag. |
| Previous Message | Andres Freund | 2026-02-18 23:24:30 | Re: Headerscheck support for meson |