From: | Wes <wespvp(at)syntegra(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Excessive vacuum times |
Date: | 2005-12-13 16:04:47 |
Message-ID: | BFC44D3F.1B34F%wespvp@syntegra.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12/12/05 5:26 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The problem was determined to be due to the fact that indexes are vacuumed
>> in index order, not in disk storage order. I don't see anything about this
>> in the "What's new" for 8.1. Has anything been done to resolve this?
>
> No. Avoiding that would require a new approach to
> vacuum-vs-ordinary-indexscan interlocking, so it won't happen until
> someone has a Bright Idea (tm).
Any ideas on how I might I reconfigure to mitigate the issue? Separating
the most offending indexes to separate drives probably isn't an option.
Wes
From | Date | Subject | |
---|---|---|---|
Next Message | Terry Lee Tucker | 2005-12-13 16:05:11 | to_char() Question |
Previous Message | DANTE ALEXANDRA | 2005-12-13 15:56:51 | Re: PostGreSQL 8.1.0 : out of memory during vacuum full |