| From: | "Pierre C" <lists(at)peufeu(dot)com> |
|---|---|
| To: | Fabrício dos Anjos Silva <fabricio(dot)silva(at)linkcom(dot)com(dot)br>, "Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: How does PG know if data is in memory? |
| Date: | 2010-10-01 13:45:34 |
| Message-ID: | op.vjwgh8ejeorkce@apollo13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> It sounds horrendously complicated to keep track of to me, and in the
> end it won't make query execution any faster, it'll just potentially
> help the planner pick a better plan. I wonder if that'd be worth the
> extra CPU time spent managing the cache and cache content stats, and
> using those cache stats when planning? It'd be an interesting
> experiment, but the outcome is hardly obvious.
Well, suppose you pick an index scan, the only way to know which index
(and heap) pages you'll need is to actually do the index scan... which
isn't really something you'd do when planning. So you scan,
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-10-01 13:46:07 | Re: How does PG know if data is in memory? |
| Previous Message | Craig Ringer | 2010-10-01 12:24:21 | Re: How does PG know if data is in memory? |