From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Alessandro Baretta <a.baretta@barettadeit.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Suspending SELECTs
Date: Tue, 17 Jan 2006 15:18:07 -0800
Message-ID: <200601171518.07342.josh@agliodbs.com> (raw)
In-Reply-To: <200601171459.02398.josh@agliodbs.com>
References: <43CB71AC.20203@barettadeit.com>
<43CD4BD0.9090807@barettadeit.com>
<200601171459.02398.josh@agliodbs.com>
People:
To follow up further, what Alessandro is talking about is known as a
"keyset cursor". Sybase and SQL Server used to support them; I beleive
that they were strictly read-only and had weird issues with record
visibility.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, a.baretta@barettadeit.com, tgl@sss.pgh.pa.us
Subject: Re: Suspending SELECTs
In-Reply-To: <200601171518.07342.josh@agliodbs.com>
* 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