Re: We don't enforce NO SCROLL cursor restrictions

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: We don't enforce NO SCROLL cursor restrictions
Date: 2021-09-09 17:47:41
Message-ID: e6b5e1c3-71ad-b384-7f6f-0c3f021906d1@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-09-09 18:09:58 Re: We don't enforce NO SCROLL cursor restrictions
Previous Message Mark Dilger 2021-09-09 17:42:11 Re: [Patch] ALTER SYSTEM READ ONLY