| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Łukasz Jagiełło <lukasz(dot)jagiello(at)gforces(dot)pl> |
| Cc: | 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-25 18:55:06 |
| Message-ID: | 6357.1243277706@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
=?UTF-8?B?xYF1a2FzeiBKYWdpZcWCxYJv?= <lukasz(dot)jagiello(at)gforces(dot)pl> writes:
> That autovacuum working hole time, shoudn't be run only when db needs ?
With 2000 databases to cycle through, autovac is going to be spending
quite a lot of time just finding out whether it needs to do anything.
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.
Maybe it would make more sense to have one database (or at least,
many fewer databases) and 2000 schemas within it?
If you really want to stick with this layout, you're going to have to
increase autovacuum_naptime.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Łukasz Jagiełło | 2009-05-25 19:07:53 | Re: Problems with autovacuum |
| Previous Message | Łukasz Jagiełło | 2009-05-25 18:43:27 | Re: Problems with autovacuum |