| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Dennis Bjorklund" <db(at)zigo(dot)dhs(dot)org>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Christopher Browne" <cbbrowne(at)acm(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Seqscan in MAX(index_column) |
| Date: | 2003-09-05 06:04:35 |
| Message-ID: | 043c01c37373$970b9da0$2800a8c0@mars |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-09-05 06:14:40 | Re: FK type mismatches? |
| Previous Message | Dennis Bjorklund | 2003-09-05 05:18:43 | Re: Seqscan in MAX(index_column) |