Re: pgsql: Move btbulkdelete's vacuum_delay_point()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Move btbulkdelete's vacuum_delay_point()
Date: 2006-02-14 20:55:12
Message-ID: 22513.1139950512@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> On Tue, 2006-02-14 at 13:20 -0400, Tom Lane wrote:
>> add missing vacuum_delay_point() call in btvacuumcleanup.

> Cool and Interesting. That might explain some pretty dire performance
> numbers from last week while running auto vacuum. Performance was
> flat-lining for a while. Still need to investigate further though.

Yeah, the missing delay would result in a spike in I/O demand from
vacuum (auto or otherwise) while processing a big index, if you had
vacuum delay configured. GIST had the same problem, too.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2006-02-14 21:57:05 Re: pgsql: Add psql option: -1 or --single-transaction
Previous Message Simon Riggs 2006-02-14 20:46:40 Re: pgsql: Move btbulkdelete's vacuum_delay_point()