Re: We don't enforce NO SCROLL cursor restrictions
Vik Fearing <vik@postgresfriends.org>
From: Vik Fearing <vik@postgresfriends.org>
To: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org
Date: 2021-09-09T17:47:41Z
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
Commits
-
Fix some anomalies with NO SCROLL cursors.
- fa5d0415f10f 13.5 landed
- d844cd75a676 14.0 landed
- c1b7a6c27312 15.0 landed
- ba408fc960b6 12.9 landed
- 9ea8d3d24a9f 11.14 landed
-
Avoid misbehavior when persisting a non-stable cursor.
- ba2c6d6cec00 14.0 cited