Re: COUNT & Pagination - Mailing list pgsql-performance

From Neil Conway
Subject Re: COUNT & Pagination
Date
Msg-id 8765f7ij7v.fsf@mailbox.samurai.com
Whole thread Raw
In response to Re: COUNT & Pagination  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-performance
"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


pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Join optimisation Quandry
Next
From: Neil Conway
Date:
Subject: Re: Trigger question