Re: Seqscan in MAX(index_column) - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Seqscan in MAX(index_column)
Date
Msg-id 043c01c37373$970b9da0$2800a8c0@mars
Whole thread Raw
In response to Re: Seqscan in MAX(index_column)  (Dennis Bjorklund <db@zigo.dhs.org>)
List pgsql-hackers
> A general query cache is something that is fairly clean and which might
> help both with count(*) and other queries.
>
> Many databases has a lot of tables that are more or less stable where this
> would work fine. From what I have heard mysql has something like this and
> it works well. For tables that change a lot the the cached queries will
> almost always be invalid so one might want to let the user decide which
> tables should never be cached.

It works well because MySQL doesn't have MVCC...

Chris



pgsql-hackers by date:

Previous
From: Dennis Bjorklund
Date:
Subject: Re: Seqscan in MAX(index_column)
Next
From: Tom Lane
Date:
Subject: Re: FK type mismatches?