BUG #18616: Long-running hash index build can not be interrupted - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #18616: Long-running hash index build can not be interrupted
Date
Msg-id 18616-acbb9e5caf41e964@postgresql.org
Whole thread Raw
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      18616
Logged by:          Alexander Lakhin
Email address:      exclusion@gmail.com
PostgreSQL version: 17rc1
Operating system:   Ubuntu 22.04
Description:

The following script:
CREATE TABLE t(i int);
INSERT INTO t SELECT 1 FROM generate_series(1, 10000000);

SET maintenance_work_mem = '1GB';

SET statement_timeout = '90s';
CREATE INDEX hi ON t USING hash (i);

reaches a state, when the backend can not be interrupted.

gdb shows that the code execution loops inside:
#0  _h_indexbuild (...) at hashsort.c:151
#1  0x0000557f3671cbf3 in hashbuild (...)
    at hash.c:183
...
with tups_done increasing slowly (given the total number of tuples).

Reproduced on all supported versions.


pgsql-bugs by date:

Previous
From: Duncan Sands
Date:
Subject: Re: pg_restore with --disable-triggers discards ENABLE ALWAYS
Next
From: Vinay Oli
Date:
Subject: Reg: Size difference