| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Lists <lists(at)benjamindsmith(dot)com>, pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Unexpectedly high disk space usage RESOLVED (Manual reindex/vacuum) |
| Date: | 2012-11-10 22:08:52 |
| Message-ID: | CAOR=d=206oJiZ_mkencYONYToSeTsbGuAu9s_9KkkwDz9hgi-w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Nov 10, 2012 at 2:12 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Fri, Nov 9, 2012 at 5:56 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
>>
>> As well, since the default nap time is 1 minute, it will take at least
>> 50 minutes to vacuum each db as nap time is how long autovac waits
>> between databases.
>
> That isn't how it works. The naptime is per database, not per
> cluster. If the naptime is 1 minute and there are 50 "active"
> databases, then it will launch a new worker every 1.2 seconds
> (assuming the old ones finish fast enough that doing so would not
> exceed autovacuum_max_workers)
Hmmm. That was not my understanding from previous discussions on nap time.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Angelico | 2012-11-10 22:14:33 | Re: PG defaults and performance (was Re: Unexpectedly high disk space usage RESOLVED (Manual reindex/vacuum)) |
| Previous Message | Jeff Janes | 2012-11-10 21:12:35 | Re: Unexpectedly high disk space usage RESOLVED (Manual reindex/vacuum) |