| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Dave Cramer <davecramer(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: Proposal to allow setting cursor options on Portals |
| Date: | 2026-01-15 00:42:00 |
| Message-ID: | CAOYmi+kkQqRw2ajt5e-CX5YchrMwS_qJ4+94Yjxh=dHGo+8jPA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 14, 2026 at 3:12 PM Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
> As a maintainer of a proxy, I'd be pretty annoyed if clients start
> sending fields or messages that I don't expect, without *something* in
> the StartupMessage advertising that that will happen. This specific
> patch would be fine for pgbouncer, because it only parses the first
> few fields of the Bind message. But e.g pgcat seems to parse the whole
> Bind message[2]
Yeah... I'm pretty skeptical of the phrase "backwards compatible" in
the way you've used it, Dave. I think that assumes either that
everyone's packet parsers are incredibly lenient, or else that `ERROR:
invalid message format` should be considered a compatible response.
(This ties into my upthread concern that we don't have a good shared
mental model for middlebox compatibility in the protocol.)
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Jacob Champion | 2026-01-15 00:31:10 | Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta |