pgsql: Move btbulkdelete's vacuum_delay_point() call to a place in the - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Move btbulkdelete's vacuum_delay_point() call to a place in the
Date
Msg-id 20060214172002.191DA9DCBDF@postgresql.org
Whole thread Raw
Responses Re: pgsql: Move btbulkdelete's vacuum_delay_point()  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-committers
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).

Modified Files:
--------------
    pgsql/src/backend/access/nbtree:
        nbtree.c (r1.140 -> r1.141)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.140&r2=1.141)

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Add psql option: -1 or --single-transaction
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Move btbulkdelete's vacuum_delay_point() call to a place in the