| From: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
| Cc: | "CK Tan" <cktan(at)greenplum(dot)com>, "Luke Lonergan" <LLonergan(at)greenplum(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "Jeff Davis" <pgsql(at)j-davis(dot)com>, "Simon Riggs" <simon(at)enterprisedb(dot)com> |
| Subject: | Re: Seq scans roadmap |
| Date: | 2007-05-10 10:51:55 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA57901FD9968@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Also, that patch doesn't address the VACUUM issue at all. And
> using a small fixed size ring with scans that do updates can
> be devastating. I'm experimenting with different ring sizes
> for COPY at the moment. Too small ring leads to a lot of WAL
> flushes, it's basically the same problem we have with VACUUM
> in CVS HEAD.
My first take on that would be to simply abandon any dirty (and actually
also any still pinned) buffer from the ring and replace the ring slot
with a buffer from the freelist.
If the freelist is empty and LSN allows writing the buffer, write it
(and maybe try to group these).
If the LSN does not allow the write, replace the slot with a buffer from
LRU.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-05-10 12:22:01 | Re: Seq scans roadmap |
| Previous Message | Zeugswetter Andreas ADI SD | 2007-05-10 10:14:11 | Re: Seq scans roadmap |