pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alessandro Baretta <a.baretta@barettadeit.com>
To: mark@mark.mielke.cc
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Suspending SELECTs
Date: Wed, 18 Jan 2006 09:57:50 +0100
Message-ID: <43CE030E.1070707@barettadeit.com> (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>

mark@mark.mielke.cc wrote:
> On Tue, Jan 17, 2006 at 08:56:00PM +0100, Alessandro Baretta wrote:
> 
>>I understand most of these issues, and expected this kind of reply. Please, 
>>allow me to insist that we reason on this problem and try to find a 
>>solution. My reason for doing so is that the future software industry is 
>>likely to see more and more web applications retrieving data from virtually 
>>endless databases, and in such contexts, it is sensible to ask the final 
>>client--the web client--to store the "cursor state", because web 
>>interaction is intrinsically asynchronous, and you cannot count on users 
>>logging out when they're done, releasing resources allocated to them. Think 
>>of Google.
> 
> 
> What is wrong with LIMIT and OFFSET? I assume your results are ordered
> in some manner.

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.

Alex

-- 
*********************************************************************
http://www.barettadeit.com/
Baretta DE&IT
A division of Baretta SRL

tel. +39 02 370 111 55
fax. +39 02 370 111 54

Our technology:

The Application System/Xcaml (AS/Xcaml)
<http://www.asxcaml.org/;

The FreerP Project
<http://www.freerp.org/;



view thread (29+ messages)  latest in thread

Message-ID: <43CE030E.1070707@barettadeit.com>
Permalink:  ../43CE030E.1070707@barettadeit.com/
Also on:    postgresql.org/message-id/43CE030E.1070707@barettadeit.com

 · 

reply

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: a.baretta@barettadeit.com, mark@mark.mielke.cc, tgl@sss.pgh.pa.us
  Subject: Re: Suspending SELECTs
  In-Reply-To: <43CE030E.1070707@barettadeit.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