| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Piggybacking vacuum I/O |
| Date: | 2007-01-26 16:47:32 |
| Message-ID: | 2e78013d0701260847q168544cbwf3c4b6f31a51f8fc@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/26/07, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>
>
> Maybe have the bgwriter update hint bits as it evicts pages out of the
> cache? It could result in pg_clog read traffic for each page that needs
> eviction; not such a hot idea.
I thought once we enhance clog so that there are no clog reads,
bgwriter would be able to update hint bits without getting into any deadlock
with pg_clog read.
May be we can have this as a seperate TODO
Thanks,
Pavan
--
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-01-26 16:47:52 | Re: Piggybacking vacuum I/O |
| Previous Message | Tom Lane | 2007-01-26 16:40:38 | Re: Proposal: Snapshot cloning |