Horton

Re: Proposal to allow setting cursor options on Portals

Dave Cramer <davecramer@gmail.com>

View thread View on postgr.es
From: Dave Cramer <davecramer@gmail.com>
To: Sami Imseih <samimseih@gmail.com>
Cc: Hannu Krosing <hannuk@google.com>, Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Jelte Fennema-Nio <postgres@jeltef.nl>, Jacob Champion <jacob.champion@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Heikki Linnakangas <hlinnaka@iki.fi>
Date: 2026-03-24T10:01:05Z
Lists: pgsql-hackers 
On Mon, 23 Mar 2026 at 21:59, Sami Imseih <samimseih@gmail.com> wrote:

> Hi,
>
> One thing that just occurred to me is why must we limit
> the new protocol extension to holdable cursors?
>
> PQsendBindWithCursorOptions() will work with any cursor option,
> Maybe it should be called "_pq_.named_portal" or perhaps better
> "_pq_.cursor"?
>

Well there are currently ways to name a portal with V3 so named portal
doesn't make sense.

_pq_.cursor would be fine.

Dave

Commits

  1. Fix distinctness check for queries with grouping sets

  2. Provide for forward compatibility with future minor protocol versions.