Re: Proposal to allow setting cursor options on Portals
| От | Patrick Reinhart |
|---|---|
| Тема | Re: Proposal to allow setting cursor options on Portals |
| Дата | |
| Msg-id | 2b3d5da9-34ba-49ee-a052-b6dd7233c524@gmail.com обсуждение исходный текст |
| Ответ на | Proposal to allow setting cursor options on Portals (Dave Cramer <davecramer@gmail.com>) |
| Список | pgsql-hackers |
Hi Dave,
The Company I working is in the progress to migrate a lot of databases from Oracle to PostreSQL lately and have the need currently to hold cursors over commits at the moment.
This does lead to nasty Java out-of-memory for big tables as in this case the specified fetch size is been ignored.
There was also some thread around this issue here if I'm not mistaken:
I could also offer some type of I-the-field test as soon there is a way to setup the needed environment locally...
Best regards
Patrick
Greetings,My main driver here is to allow the creation of Holdable portals at the protocol level for drivers. Currently the only way to create a holdable cursor is at the SQL level.DECLARE liahona CURSOR WITH HOLD FOR SELECT * FROM films;The JDBC driver has an option in the API to have result sets survive commits see https://docs.oracle.com/javase/8/docs/api/java/sql/Connection.html#createStatement-int-int-int-Doing this at the protocol level is the correct way to do this as modifying the SQL to create a cursor is very cumbersome and we already have existing code to create a portal. Adding the ability to specify optionsLooking for feedback.Dave Cramer
В списке pgsql-hackers по дате отправления: