Hi Rod,
> Any solution fixing buffers should probably not take into consideration
> the method being performed (do you really want to skip caching a
> sequential scan of a 2 tuple table because it didn't use an index) but
> the volume of data involved as compared to the size of the cache.
Yes, in fact indexes aren't so different to tables really in that regard.
It sounds like version 8 may help out anyway.
regards
Iain
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
- [PERFORM] seq scan cache vs. index cache smackdown Mark Aufflick
- Re: [PERFORM] seq scan cache vs. index cache smack... Iain
- Re: [PERFORM] seq scan cache vs. index cache smack... Christopher Browne
- Re: [PERFORM] seq scan cache vs. index cache smack... Greg Stark
- Re: [PERFORM] seq scan cache vs. index cache s... Tom Lane
- Re: [PERFORM] seq scan cache vs. index cac... Greg Stark
- Re: [PERFORM] seq scan cache vs. index... Josh Berkus
- Re: [PERFORM] seq scan cache vs. ... Tom Lane
- Re: [PERFORM] seq scan cache vs. ... Greg Stark
- Re: [PERFORM] seq scan cache vs. ... Ron Mayer
- Re: [PERFORM] seq scan cache vs. index cache smack... Merlin Moncure
- Re: [PERFORM] seq scan cache vs. index cache s... Christopher Browne