| From: | Jelte Fennema-Nio <me(at)jeltef(dot)nl> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | 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: | 2025-10-31 21:56:19 |
| Message-ID: | CAGECzQR9Yx484X7Kk+gdw5HPezvf4YWGg_GemqB2s6jWj2TCUg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 31 Oct 2025 at 17:24, Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> I still wouldn't want the declaration
> that "we default to the latest" to be mixed into the growing search
> engine slop pile.
Fair enough (although the intent is to get to that state at some point).
> Is there an even stronger way for us to grease this? For example,
> could we agree that no one will ever implement 0003.7FFF and push that
> during the beta, failing if anyone gives us an unsupported version?
I quite like that idea! Although maybe not 7FFF, but 270F so that
PQfullProtocolVersion returns 39999. And I think it'd be good to also
add a protocol option, like _pq_.test_protocol_breakage and fail the
connection attempt client side if that does not get returned back as
unsupported. I'll try to update this patch to do that in the coming days.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Alger | 2025-10-31 22:29:19 | Re: [PATCH] Add pg_get_type_ddl() to retrieve the CREATE TYPE statement |
| Previous Message | Andres Freund | 2025-10-31 21:55:00 | Re: Updating IPC::Run in CI? |