From: Neil Conway <neilc@samurai.com>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: Rajesh Kumar Mallah <mallah@trade-india.com>
Cc: David Shadovitz <david@www.shadovitz.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: COUNT & Pagination
Date: Mon, 19 Jan 2004 18:58:44 -0500
Message-ID: <8765f7ij7v.fsf@mailbox.samurai.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0401141436230.25071-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0401141436230.25071-100000@css120.ihs.com>
"scott.marlowe" <scott.marlowe@ihs.com> writes:
> Yes, previously run query should be faster, if it fits in kernel
> cache.
Or the PostgreSQL buffer cache.
> Plus, the design of Postgresql is such that it would have to do a
> LOT of cache checking to see if there were any updates to the
> underlying data between selects.
Last I checked (which was a while ago, admittedly), the MySQL design
completely purges the query cache for a relation whenever that
relation is mentioned in an INSERT, UPDATE, or DELETE. When this was
discussed (check the -hackers archives for more), IIRC the consensus
was that it's not worth implementing it if we can't do better than
that.
-Neil
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: neilc@samurai.com, scott.marlowe@ihs.com, mallah@trade-india.com, david@www.shadovitz.com
Subject: Re: COUNT & Pagination
In-Reply-To: <8765f7ij7v.fsf@mailbox.samurai.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