From: Tino Wildenhain <tino@wildenhain.de>
To: Alessandro Baretta <a.baretta@barettadeit.com>
Cc: mark@mark.mielke.cc, Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Suspending SELECTs
Date: Wed, 18 Jan 2006 10:08:25 +0100
Message-ID: <43CE0589.3000003@wildenhain.de> (raw)
In-Reply-To: <43CE030E.1070707@barettadeit.com>
References: <43CB71AC.20203@barettadeit.com>
<9766.1137433907@sss.pgh.pa.us>
<43CD4BD0.9090807@barettadeit.com>
<20060117211259.GA13926@mark.mielke.cc>
<43CE030E.1070707@barettadeit.com>
Alessandro Baretta schrieb:
> mark@mark.mielke.cc wrote:
>
...
>
> It looks like this is the only possible solution at present--and in the
> future, too--but it has a tremendouse performance impact on queries
> returning thousands of rows.
>
Well actually one of the better solutions would be persistent cursors
(and therefore connection pooling). I bet this is easier then
fiddling with the problems of offset/limit and inventing even more
compex caching in the application.
Just my 0.02c
++Tino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tino@wildenhain.de, a.baretta@barettadeit.com, tgl@sss.pgh.pa.us
Subject: Re: Suspending SELECTs
In-Reply-To: <43CE0589.3000003@wildenhain.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox