| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Jacob Champion <jchampion(at)postgresql(dot)org> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Subject: | Re: pgsql: libpq: Grease the protocol by default |
| Date: | 2026-02-23 21:17:05 |
| Message-ID: | CAOYmi+=4QhCjssfNEoZVK8LPtWxnfkwT5p-PAeoxtG9gpNjqOQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Feb 23, 2026 at 10:58 AM Jacob Champion
<jchampion(at)postgresql(dot)org> wrote:
>
> libpq: Grease the protocol by default
crake is angry:
> pg_dumpall: error: connection to server on socket "/home/andrew/bf/root/tmp/buildfarm-onigY7/.s.PGSQL.5670" failed: FATAL: unsupported frontend protocol 3.9999: server supports 1.0 to 3.0
> This indicates a bug in either the server being contacted
> or a proxy handling the connection. Please consider
> ...
So while this is kind of a nice result, in that it's correctly
diagnosing the problem, I need to add max_protocol_version=3.0 to the
connection strings for these upgrades during beta.
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2026-02-23 21:24:08 | pgsql: Fix indentation from commit b380a56a3f9 |
| Previous Message | Nathan Bossart | 2026-02-23 20:57:04 | pgsql: Allow pg_{read,write}_all_data to access large objects. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2026-02-23 21:33:46 | Re: convert SpinLock* macros to static inline functions |
| Previous Message | Nathan Bossart | 2026-02-23 21:03:39 | Re: getting "shell command argument contains a newline or carriage return:" error with pg_dumpall when db name have new line in double quote |