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

From Simon Riggs
Subject Re: pgsql: Move btbulkdelete's vacuum_delay_point()
Date
Msg-id 1139950000.1258.1017.camel@localhost.localdomain
Whole thread Raw
In response to pgsql: Move btbulkdelete's vacuum_delay_point() call to a place in the  (tgl@postgresql.org (Tom Lane))
Responses Re: pgsql: Move btbulkdelete's vacuum_delay_point()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Tue, 2006-02-14 at 13:20 -0400, Tom Lane wrote:
> Log Message:
> -----------
> Move btbulkdelete's vacuum_delay_point() call to a place in the loop where
> we are not holding a buffer content lock; where it was, InterruptHoldoffCount
> is positive and so we'd not respond to cancel signals as intended.  Also
> add missing vacuum_delay_point() call in btvacuumcleanup.  This should fix
> complaint from Evgeny Gridasov about failure to respond to SIGINT/SIGTERM
> in a timely fashion (bug #2257).

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.

Best Regards, Simon Riggs


pgsql-committers by date:

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