| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Wes <wespvp(at)syntegra(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Excessive vacuum times |
| Date: | 2005-12-13 17:44:08 |
| Message-ID: | 8246.1134495848@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Wes <wespvp(at)syntegra(dot)com> writes:
> 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.
What are you using for vacuum_mem? A larger value should reduce the
number of times we have to scan the indexes of a large table.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2005-12-13 17:49:08 | Re: Bug#342369: PostgreSQL 8.1.0 RHEL / Debian incompatible |
| Previous Message | Scott Marlowe | 2005-12-13 17:40:06 | Re: Memory Leakage Problem |