| From: | Tobias Brox <tobias(at)nordicbet(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tobias Brox <tobias(at)nordicbet(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: long running transactions |
| Date: | 2006-10-10 18:43:54 |
| Message-ID: | 20061010184354.GA24098@oppetid.no |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
[Tom Lane - Tue at 02:26:53PM -0400]
> > autovacuum_vacuum_cost_delay = 500
> > autovacuum_vacuum_cost_limit = 200
>
> Well, that's going to cause it to sleep half a second after every dozen
> or so page I/Os. I think you'd be well advised to reduce the delay.
Modified it to 20/250, and it definitively helped. Sorry for the
list verbosity; I should have been able to resolve this myself already
some 2-3 emails ago :-) I wanted a "soft" introduction of autovac in
production, and assumed that it was better to begin with too much sleep
than too little! Well, well.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-10-10 19:26:23 | Re: Simple join optimized badly? |
| Previous Message | Tom Lane | 2006-10-10 18:26:53 | Re: long running transactions |