Re: pgsql: Move btbulkdelete's vacuum_delay_point() - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Move btbulkdelete's vacuum_delay_point()
Date
Msg-id 22513.1139950512@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Move btbulkdelete's vacuum_delay_point()  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: pgsql: Move btbulkdelete's vacuum_delay_point()  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-committers
Simon Riggs <simon@2ndquadrant.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

pgsql-committers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: pgsql: Move btbulkdelete's vacuum_delay_point()
Next
From: Simon Riggs
Date:
Subject: Re: pgsql: Add psql option: -1 or --single-transaction