You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When executing SQL queries with the 'fold' family of functions, could there be some way to control the SQL generated for the "FETCH FORWARD" statements?
If I look at the corresponding activity on the Postgres server, I see a lot of these: FETCH FORWARD 256 FROM temp1
This makes it quite difficult to match up DB activity with what triggered it.
If one of these queries is running for an unexpectedly long time, I'd like to be able to match it up with our logs somehow.
Perhaps the name of the CURSOR could be optionally provided in the FoldOptions.
Or maybe allow a SQL comment to be provided for the FETCH FORWARD statement.
The text was updated successfully, but these errors were encountered:
When executing SQL queries with the 'fold' family of functions, could there be some way to control the SQL generated for the "FETCH FORWARD" statements?
If I look at the corresponding activity on the Postgres server, I see a lot of these:
FETCH FORWARD 256 FROM temp1
This makes it quite difficult to match up DB activity with what triggered it.
If one of these queries is running for an unexpectedly long time, I'd like to be able to match it up with our logs somehow.
Perhaps the name of the CURSOR could be optionally provided in the FoldOptions.
Or maybe allow a SQL comment to be provided for the FETCH FORWARD statement.
The text was updated successfully, but these errors were encountered: