| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Russell Smith <mr-russ(at)pws(dot)com(dot)au> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Heavy write activity on first vacuum of fresh TOAST data |
| Date: | 2007-12-14 07:42:42 |
| Message-ID: | 29185.1197618162@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Russell Smith <mr-russ(at)pws(dot)com(dot)au> writes:
> Given vacuum must then touch every page, is there a win in only setting
> hint bits on pages where vacuum has to do some other work on the page?
> As vacuum is causing significant IO load for data that may not be
> accessed for some time.
Well, if vacuum doesn't do it then some other poor sod will have to.
My feeling is that vacuum's purpose in life is to offload maintenance
cycles from foreground queries, so we should be happy to have it setting
all the hint bits. If Kevin doesn't like the resultant I/O load then he
should use the vacuum_cost_delay parameters to dial down vacuum speed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-12-14 11:03:56 | Re: Need help on parameters and their values to tune the postgresql database |
| Previous Message | Russell Smith | 2007-12-14 07:30:11 | Re: Heavy write activity on first vacuum of fresh TOAST data |