pgsql: Check for interrupts during non-fast-update GIN insertion - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: Check for interrupts during non-fast-update GIN insertion
Date
Msg-id E1w12L5-003lov-0c@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Check for interrupts during non-fast-update GIN insertion

ginExtractEntries() can produce a lot of entries for a single item.
During index build, we check for interrupts between entries, and the
fast-update codepath does it as part of vacuum_delay_point(), but the
non-fast update insertion codepath was uninterruptible. Add
CHECK_FOR_INTERRUPTS() between entries in the non-fast update codepath
too.

Author: Vinod Sridharan <vsridh90@gmail.com>
Discussion: https://www.postgresql.org/message-id/CAFMdLD6mQvAuStiOGvBJxAEfo6wdjZhj3+JveTLxOX8MVn4zmA@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/2e1dcf8c5424309305182af4700314cf59bab6b0

Modified Files
--------------
src/backend/access/gin/gininsert.c | 4 ++++
1 file changed, 4 insertions(+)


pgsql-committers by date:

Previous
From: Alexander Korotkov
Date:
Subject: pgsql: Rework ginScanToDelete() to pass Buffers instead of BlockNumbers
Next
From: Fujii Masao
Date:
Subject: pgsql: Add stats_reset column to pg_stat_database_conflicts.