Ahh, yes. In this case it is possibly only with holdable cursors by declaring them and committing before reading any rows from it to force materialization of entire result set to the temporary storage. Although, this approach can be used to avoid std::bad_alloc in case of millions tuples in the result set :-)
2010/10/30 Dave Page <dp...@pgadmin.org> > On Sat, Oct 30, 2010 at 4:14 PM, Dmitriy Igrishin <dmit...@gmail.com> > wrote: > > Do you mean that cursors (regular, not holdable) live only inside a > > transactions? > > But it is possible to check transaction status from another part of > pgAdmin > > or > > even make the window with result set modal ? > > No, I mean that the tool was developed to help tune application > queries, in which the data transfer time can be just as important as > the query execution time. With cursors, you lose that information. > > Of course, patches to make optional use of cursors would be interesting to > us. > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > -- // Dmitriy.
