Re: Proposal to allow setting cursor options on Portals - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Proposal to allow setting cursor options on Portals
Date
Msg-id CAOYmi+kkQqRw2ajt5e-CX5YchrMwS_qJ4+94Yjxh=dHGo+8jPA@mail.gmail.com
Whole thread Raw
In response to Re: Proposal to allow setting cursor options on Portals  (Jelte Fennema-Nio <postgres@jeltef.nl>)
List pgsql-hackers
On Wed, Jan 14, 2026 at 3:12 PM Jelte Fennema-Nio <postgres@jeltef.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



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
Next
From: lchch1990@sina.cn
Date:
Subject: Can we change pg_rewind used without wal_log_hints and data_checksums