From: Vik Fearing <vik@postgresfriends.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@lists.postgresql.org
Subject: Re: We don't enforce NO SCROLL cursor restrictions
Date: Thu, 9 Sep 2021 19:47:41 +0200
Message-ID: <e6b5e1c3-71ad-b384-7f6f-0c3f021906d1@postgresfriends.org> (raw)
In-Reply-To: <3712911.1631207435@sss.pgh.pa.us>
References: <3712911.1631207435@sss.pgh.pa.us>
On 9/9/21 7:10 PM, Tom Lane wrote:
> We don't actually prevent you from scrolling a NO SCROLL cursor:
>
> There are probably specific cases where you do get an error,
> but we don't have a blanket you-can't-do-that check. Should we?
I would say yes. NO SCROLL means no scrolling; or at least should.
On the other hand, if there is no optimization or other meaningful
difference between SCROLL and NO SCROLL, then we can just document it as
a no-op that is only provided for standard syntax compliance.
--
Vik Fearing
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: pgsql-hackers@postgresql.org
Cc: vik@postgresfriends.org, tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org
Subject: Re: We don't enforce NO SCROLL cursor restrictions
In-Reply-To: <e6b5e1c3-71ad-b384-7f6f-0c3f021906d1@postgresfriends.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox