public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dave Cramer <[email protected]>
To: Jelte Fennema-Nio <[email protected]>
Cc: Jacob Champion <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Subject: Re: Proposal to allow setting cursor options on Portals
Date: Tue, 6 Jan 2026 07:14:06 -0500
Message-ID: <CADK3HH+o9dTYsXpCk7-Z0JW-QB2TV7=e97O8B-XDOGQb14AfSQ@mail.gmail.com> (raw)
In-Reply-To: <CADK3HHL_cUzm-R+0nHcLvxdOZQeR0YKQMDjwLTEiGX-F9=tbeA@mail.gmail.com>
References: <CADK3HHKe1PA1U6aB5-7tWBQ0yZGgNvY7H=ECDD9955Pas_zx_Q@mail.gmail.com>
<CAGECzQRQ5optaG4DPbshKS+zpUtn_oceh8-qdshFbS+-FSb8Dg@mail.gmail.com>
<CAOYmi+nVQRpSs3vd_v9L8ytO9wnL2ndnzGwU31aDGorVFxrAYA@mail.gmail.com>
<CAGECzQSZ43JMjA8QEJoF9DCdTO0GQeR2qyhouQciSG2ik40Yhg@mail.gmail.com>
<CAOYmi+m20jS8zZ2qFpSnvhaqGDX+vtgCsqcu9VhokyLqF8kFag@mail.gmail.com>
<CADK3HH+DPY_x_H=e0c_AVWoUP9E+YXdyJDVvmzYEYxZXT87Agw@mail.gmail.com>
<CAGECzQRZwbuSNp-mgPWmC97q63ODAun=pQtXa1Ru19ksz986Hg@mail.gmail.com>
<CADK3HHKDrnRAoAcUv1ucLB0o_ZUcJRwm+jonNPNUHoDtcA9Crw@mail.gmail.com>
<CAGECzQQriv-h_h8Ygxh_RfnLt2G4P9nWrpgMi9YL2bmcOLbUEA@mail.gmail.com>
<CADK3HHL_cUzm-R+0nHcLvxdOZQeR0YKQMDjwLTEiGX-F9=tbeA@mail.gmail.com>
On Mon, 15 Dec 2025 at 06:32, Dave Cramer <[email protected]> wrote:
>
>
> On Sun, 14 Dec 2025 at 09:04, Jelte Fennema-Nio <[email protected]>
> wrote:
>
>> On Sun, 14 Dec 2025 at 14:49, Dave Cramer <[email protected]> wrote:
>> > Here I was thinking that binary was the one that did make sense. The
>> pgjdbc driver would like the results back in binary, I believe others would
>> as well.
>>
>> I agree drivers would like binary results back, but it's unclear to me
>> how CURSOR_OPT_BINARY is different from setting the result column
>> format codes to an array of a single 1? That should also change all
>> columns to be binary right?
>>
>
> Fair point.
>
>>
>> > Fair, but from my POV, we are only concerned with Postgres. I would say
>> it's up to the other implementations to deal with incompatibilities.
>>
>> I get what you mean, but I feel like we should at least be concerned
>> with popular ecosystem tools like, pgbouncer and pgpool. But then it
>> quickly becomes an exercise in where we draw the line, what about
>> postgres forks like Yugabyte? Or things very similar like cockroachdb.
>> Both of those are distributed, and probably don't use our LSNs. So as
>> a concrete example, if we add LSNs to the protocol, it would be nice
>> to work with their version too if it's not too much effort. e.g. by
>> specifing a length for the commit id in the protocol instead of
>> forcing it at the protocol level to always be a 64bit integer.
>>
>
> It would make sense to be forward looking here in the event that Postgres
> ever has wider LSN's agreed.
>
Any progress on this ?
Dave
>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Proposal to allow setting cursor options on Portals
In-Reply-To: <CADK3HH+o9dTYsXpCk7-Z0JW-QB2TV7=e97O8B-XDOGQb14AfSQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox