Message-ID: <41F7A1AC.1060406@archonet.com>
Date: Wed, 26 Jan 2005 13:57:00 +0000
From: Richard Huxton <dev@archonet.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
MIME-Version: 1.0
To: alex@neteconomist.com
Cc: Andrei Bintintan <klodoma@ar-sd.net>,
	Greg Stark <gsstark@mit.edu>, pgsql-sql@postgresql.org,
	pgsql-performance@postgresql.org
Subject: Re: [SQL] OFFSET impact on Performance???
References: <019f01c4fee1$1b58d600$0b00a8c0@forge>	
	<41EF9FD3.5020400@archonet.com>
	<020d01c4fef6$595bb9d0$0b00a8c0@forge>	
	<41EFCC5B.5010302@archonet.com>	
	<33c6269f05012008391490448b@mail.gmail.com>	
	<87y8eh1hy9.fsf@stark.xeocode.com>	
	<015a01c5038f$73a70720$0b00a8c0@forge>
	<33c6269f05012605473319ef40@mail.gmail.com>
In-Reply-To: <33c6269f05012605473319ef40@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Alex Turner wrote:
> As I read the docs, a temp table doesn't solve our problem, as it does
> not persist between sessions.  With a web page there is no guarentee
> that you will receive the same connection between requests, so a temp
> table doesn't solve the problem.  It looks like you either have to
> create a real table (which is undesirable becuase it has to be
> physicaly synced, and TTFB will be very poor) or create an application
> tier in between the web tier and the database tier to allow data to
> persist between requests tied to a unique session id.
> 
> Looks like the solutions to this problem is not RDBMS IMHO.

It's less the RDBMS than the web application. You're trying to mix a 
stateful setup (the application) with a stateless presentation layer 
(the web). If you're using PHP (which doesn't offer a "real" middle 
layer) you might want to look at memcached.

--
   Richard Huxton
   Archonet Ltd