| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Gregory Stark <stark(at)enterprisedb(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Subject: | Re: Visibility map and freezing |
| Date: | 2009-01-20 20:40:37 |
| Message-ID: | 1232484037.2327.227.camel@ebony.2ndQuadrant |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2009-01-20 at 21:51 +0200, Heikki Linnakangas wrote:
> Attached is a simple patch to only start skipping pages after 20
> consecutive pages marked as visible in the visibility map. This doesn't
> do any "look-ahead", so it will always scan the first 20 pages of a
> table before it starts to skip pages, and whenever there's even one page
> that needs vacuuming, the next 19 pages will also be vacuumed.
>
> We could adjust that figure 20 according to table size. Or by
> seq_page_cost/random_page_cost. But I'm leaning towards a simple
> hard-coded value for now.
Yes, sounds good. Can we stick to multiples of 2 as the OS readahead
does IIRC? So either 16 or 32. I'd go 32.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryce Nesbitt | 2009-01-20 21:04:07 | New pg_dump patch, --no-stats flag, disables sending to statistics collector |
| Previous Message | Heikki Linnakangas | 2009-01-20 19:56:10 | Re: Hot standby, RestoreBkpBlocks and cleanup locks |