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

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Check for interrupts during non-fast-update GIN insertion
Date: 2026-03-13 13:14:03
Message-ID: E1w12L5-003lov-0c@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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(at)gmail(dot)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(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2026-03-13 13:19:30 pgsql: Add stats_reset column to pg_stat_database_conflicts.
Previous Message Alexander Korotkov 2026-03-13 12:01:51 pgsql: Rework ginScanToDelete() to pass Buffers instead of BlockNumbers