pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Merlin Moncure <mmoncure@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Performance of count(*)
Date: Thu, 22 Mar 2007 14:24:39 -0400
Message-ID: <b42b73150703221124t1d3430c9j7e4fccfa089c9844@mail.gmail.com> (raw)
In-Reply-To: <20070322173930.GI11402@mathom.us>
References: <Pine.LNX.4.62.0703221149210.13747@wr-linux02>
<200703221208.19358.albert@sedifa.com>
<Pine.LNX.4.64.0703221323590.1503@ismoli.solenovo.jns>
<20070322141807.GE11402@mathom.us>
<46029DE3.9030505@modgraph-usa.com>
<4602A15B.7000908@wildenhain.de>
<4602BB19.9050306@modgraph-usa.com>
<4602BC84.8030101@wildenhain.de>
<20070322173930.GI11402@mathom.us>
On 3/22/07, Michael Stone <mstone+postgres@mathom.us> wrote:
> On Thu, Mar 22, 2007 at 06:27:32PM +0100, Tino Wildenhain wrote:
> >Craig A. James schrieb:
> >>You guys can correct me if I'm wrong, but the key feature that's missing
> >>from Postgres's flexible indexing is the ability to maintain state
> >>across queries. Something like this:
> >>
> >> select a, b, my_index_state() from foo where ...
> >> offset 100 limit 10 using my_index(prev_my_index_state);
> >>
> >
> >Yes, you are wrong :-) The technique is called "CURSOR"
> >if you maintain persistent connection per session
> >(e.g. stand allone application or clever pooling webapplication)
>
> Did you read the email before correcting it? From the part you trimmed
> out:
>
> >The problem is that relational databases were invented before the web
> >and its stateless applications. In the "good old days", you could
> >connect to a database and work for hours, and in that environment
> >cursors and such work well -- the RDBMS maintains the internal state of
> >the indexing system. But in a web environment, state information is
> >very difficult to maintain. There are all sorts of systems that try
> >(Enterprise Java Beans, for example), but they're very complex.
>
> It sounds like they wrote their own middleware to handle the problem,
> which is basically what you suggested (a "clever pooling web
> application") after saying "wrong".
Tino was saying that rather that build a complete indexing storage
management solution that lives outside the database, it is better to
do intelligent session management so that you get the simplicity if a
two tier client server system but the scalability of a web app.
Web apps are not necessarily stateless, you just have to be a little
clever about how database connections are opened and closed. Then you
get all the database stuff that comes along with a persistent
connection (advisory locks, cursors, prepared statements, etc) without
building all kinds of data management into the middleware.
merlin
view thread (41+ messages) latest in thread
Message-ID: <b42b73150703221124t1d3430c9j7e4fccfa089c9844@mail.gmail.com> Permalink: ../b42b73150703221124t1d3430c9j7e4fccfa089c9844@mail.gmail.com/ Also on: postgresql.org/message-id/b42b73150703221124t1d3430c9j7e4fccfa089c9844@mail.gmail.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 from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-performance@postgresql.org Cc: mmoncure@gmail.com Subject: Re: Performance of count(*) In-Reply-To: <b42b73150703221124t1d3430c9j7e4fccfa089c9844@mail.gmail.com> References: <Pine.LNX.4.62.0703221149210.13747@wr-linux02> <200703221208.19358.albert@sedifa.com> <Pine.LNX.4.64.0703221323590.1503@ismoli.solenovo.jns> <20070322141807.GE11402@mathom.us> <46029DE3.9030505@modgraph-usa.com> <4602A15B.7000908@wildenhain.de> <4602BB19.9050306@modgraph-usa.com> <4602BC84.8030101@wildenhain.de> <20070322173930.GI11402@mathom.us> <b42b73150703221124t1d3430c9j7e4fccfa089c9844@mail.gmail.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