From: | Łukasz Jagiełło <lukasz(dot)jagiello(at)gforces(dot)pl> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Problems with autovacuum |
Date: | 2009-05-26 18:36:34 |
Message-ID: | de899fb00905261136m2d82b7ddxdba690e211ccdb9c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
W dniu 26 maja 2009 20:28 użytkownik Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napisał:
>>> 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.
After change autovacuum_naptime postgresql behave like you wrote before.
--
Łukasz Jagiełło
System Administrator
G-Forces Web Management Polska sp. z o.o. (www.gforces.pl)
Ul. Kruczkowskiego 12, 80-288 Gdańsk
Spółka wpisana do KRS pod nr 246596 decyzją Sądu Rejonowego Gdańsk-Północ
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-05-26 18:41:15 | Re: Problems with autovacuum |
Previous Message | Tom Lane | 2009-05-26 18:28:22 | Re: Problems with autovacuum |