| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Zeugswetter Andreas DAZ SD <ZeugswetterA(at)spardat(dot)at>, Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bgwriter changes |
| Date: | 2004-12-14 20:41:13 |
| Message-ID: | 1103056873.4037.3587.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2004-12-14 at 19:40, Tom Lane wrote:
> "Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at> writes:
> > Is it possible to do a patch that produces a dirty buffer list in LRU order
> > and stops early when eighter maxpages is reached or bgwriter_percent
> > pages are scanned ?
>
> Only if you redefine the meaning of bgwriter_percent. At present it's
> defined by reference to the total number of dirty pages, and that can't
> be known without collecting them all.
>
> If it were, say, a percentage of the total length of the T1/T2 lists,
> then we'd have some chance of stopping the scan early.
...which was exactly what was proposed for option (3).
--
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-12-14 20:50:11 | Re: cant write to file within call handler interface |
| Previous Message | Tom Lane | 2004-12-14 20:37:31 | Re: possible wierd boolean bug? |