From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: exclusion@gmail.com
Subject: BUG #18616: Long-running hash index build can not be interrupted
Date: Fri, 13 Sep 2024 10:00:00 +0000
Message-ID: <18616-acbb9e5caf41e964@postgresql.org> (raw)
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, exclusion@gmail.com
Subject: Re: BUG #18616: Long-running hash index build can not be interrupted
In-Reply-To: <18616-acbb9e5caf41e964@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox