| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: scan_recycle_buffers |
| Date: | 2007-03-09 20:08:55 |
| Message-ID: | 45F1BED7.40807@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Simon Riggs wrote:
> Patch to implement buffer cache recycling for scans, as being discussed
> on pgsql-hackers.
A few questions come to mind:
How does it behave with Jeff's synchronized seq scans patch?
I wonder if calling RelationGetNumberOfBlocks on every seq scan becomes
a performance issue for tiny tables with for example just 1 page. It
performs an lseek, which isn't free.
What happens if multiple backends choose overlapping sets of buffers to
recycle?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-03-09 20:37:42 | Re: scan_recycle_buffers |
| Previous Message | Luke Lonergan | 2007-03-09 19:36:40 | Re: Bug: Buffer cache is not scan resistant |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-03-09 20:37:42 | Re: scan_recycle_buffers |
| Previous Message | Simon Riggs | 2007-03-09 19:24:13 | scan_recycle_buffers |