Support for explicitly setting the SCROLL option via CX configuration #597
Comments
|
I can consider it, but if I did it for a patch version it would be off by default and only enabled with a compiler flag. let me see how the changes would affect users, and give a more definitive answer. |
|
Thanks for consider this @JerrySievert! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @JerrySievert ,
In PLv8, the SCROLL option is not explicitly passed during cursor creation. Internally, PostgreSQL determines whether a cursor should support scrolling based on the execution plan ([1]). However, certain plan nodes (e.g., ForeignScan) do not support backward scanning unless the SCROLL option is explicitly enabled in the statement.
Would it be possible to introduce a configurable option from CX to explicitly enable or disable SCROLL ([2])? When set to true, the cursor would always allow backward scanning. When set to false, the system would fall back to the current behavior, evaluating scroll support based on the execution context.
[1] https://github.com/postgres/postgres/blob/master/src/backend/executor/spi.c#L1702
[2] https://github.com/plv8/plv8/blob/r3.2/plv8_func.cc#L678
The text was updated successfully, but these errors were encountered: