Re: Suspending SELECTs - Mailing list pgsql-performance

From Tom Lane
Subject Re: Suspending SELECTs
Whole thread Raw
In response to Suspending SELECTs  (Alessandro Baretta)
Responses Re: Suspending SELECTs  (Alvaro Herrera <>)
Re: Suspending SELECTs  ("Craig A. James")
Re: Suspending SELECTs  (Alessandro Baretta)
List pgsql-performance
Alessandro Baretta <> writes:
> I am aware that what I am dreaming of is already available through
> cursors, but in a web application, cursors are bad boys, and should be
> avoided. What I would like to be able to do is to plan a query and run
> the plan to retreive a limited number of rows as well as the
> executor's state. This way, the burden of maintaining the cursor "on
> hold", between activations of the web resource which uses it, is
> transferred from the DBMS to the web application server,

This is a pipe dream, I'm afraid, as the state of a cursor does not
consist exclusively of bits that can be sent somewhere else and then
retrieved.  There are also locks to worry about, as well as the open
transaction itself, and these must stay alive inside the DBMS because
they affect the behavior of other transactions.  As an example, once
the cursor's originating transaction closes, there is nothing to stop
other transactions from modifying or removing rows it would have read.

            regards, tom lane

pgsql-performance by date:

From: Marcos
Subject: Use of * affect the performance
From: Alvaro Herrera
Subject: Re: Suspending SELECTs