Skip site navigation (1) Skip section navigation (2)

Re: [SQL] OFFSET impact on Performance???

From: Richard Huxton <dev(at)archonet(dot)com>
To: alex(at)neteconomist(dot)com
Cc: Andrei Bintintan <klodoma(at)ar-sd(dot)net>,Greg Stark <gsstark(at)mit(dot)edu>, pgsql-sql(at)postgresql(dot)org,pgsql-performance(at)postgresql(dot)org
Subject: Re: [SQL] OFFSET impact on Performance???
Date: 2005-01-26 13:57:00
Message-ID: 41F7A1AC.1060406@archonet.com (view raw or flat)
Thread:
Lists: pgsql-performancepgsql-sql
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

In response to

pgsql-performance by date

Next:From: Peter DarleyDate: 2005-01-26 15:16:25
Subject: Re: Possibly slow query
Previous:From: Alex TurnerDate: 2005-01-26 13:47:32
Subject: Re: [SQL] OFFSET impact on Performance???

pgsql-sql by date

Next:From: Richard HuxtonDate: 2005-01-26 13:58:58
Subject: Re: same question little different test MSSQL vrs Postgres
Previous:From: Alex TurnerDate: 2005-01-26 13:47:32
Subject: Re: [SQL] OFFSET impact on Performance???

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group