| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Łukasz Jagiełło <lukasz(dot)jagiello(at)gforces(dot)pl>, Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Problems with autovacuum |
| Date: | 2009-05-26 18:28:22 |
| Message-ID: | 16350.1243362502@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane escribi:
>> I believe the interpretation of autovacuum_naptime is that it should
>> examine each database that often, ie once a minute by default. So
>> it's got more than 30 databases per second to look through.
> Note that this is correct in 8.1 and 8.2 but not 8.3 onwards.
Oh? The current documentation still defines the variable thusly:
Specifies the minimum delay between autovacuum runs on any given
database. In each round the daemon examines the database and
issues VACUUM and ANALYZE commands as needed for tables in that
database.
I suppose the use of "minimum" means that this is not technically
incorrect, but it's sure not very helpful if there is some other
rule involved that causes it to not behave as I said. (And if there
is some other rule, what is that?) Please improve the docs.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Łukasz Jagiełło | 2009-05-26 18:36:34 | Re: Problems with autovacuum |
| Previous Message | Alvaro Herrera | 2009-05-26 18:19:34 | Re: Problems with autovacuum |