From: Frank Wiles <frank@wiles.org>
To: mark@mark.mielke.cc
Cc: a.baretta@barettadeit.com
Cc: tgl@sss.pgh.pa.us
Cc: pgsql-performance@postgresql.org
Subject: Re: Suspending SELECTs
Date: Tue, 17 Jan 2006 16:51:15 -0600
Message-ID: <20060117165115.2a5873dc.frank@wiles.org> (raw)
In-Reply-To: <20060117211259.GA13926@mark.mielke.cc>
References: <43CB71AC.20203@barettadeit.com>
<9766.1137433907@sss.pgh.pa.us>
<43CD4BD0.9090807@barettadeit.com>
<20060117211259.GA13926@mark.mielke.cc>
On Tue, 17 Jan 2006 16:12:59 -0500
mark@mark.mielke.cc wrote:
> In the mean time, I successfully use LIMIT and OFFSET without such an
> optimization, and things have been fine for me.
Same here.
---------------------------------
Frank Wiles <frank@wiles.org>
http://www.wiles.org
---------------------------------
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: frank@wiles.org, mark@mark.mielke.cc, a.baretta@barettadeit.com, tgl@sss.pgh.pa.us
Subject: Re: Suspending SELECTs
In-Reply-To: <20060117165115.2a5873dc.frank@wiles.org>
* 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