pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: alpkeles99@gmail.com
Subject: BUG #19760: CLUSTER loses a row the transaction inserted and then updated in a rolled-back subtransaction
Date: Thu, 15 Oct 2026 13:59:46 +0000
Message-ID: <19760-8f9a0eba17bc8c92@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      19760
Logged by:          Alperen Keles
Email address:      alpkeles99@gmail.com
PostgreSQL version: 18.6
Operating system:   macOS 26 arm64 (also seen on Ubuntu 24.04 x86_64)
Description:        

CLUSTER (and REPACK on master) silently drops a live row when the same
transaction inserted the row and then updated it inside a subtransaction
that was rolled back. No error is raised; the row is gone after COMMIT.

  CREATE TABLE t1(c0 int, c1 int);
  CREATE INDEX t1_i0 ON t1 (c1);
  BEGIN;
  INSERT INTO t1 VALUES (1, 1);
  SAVEPOINT s1; UPDATE t1 SET c0 = 2; ROLLBACK TO s1;
  CLUSTER t1 USING t1_i0;
  SELECT count(*) FROM t1;   -- 0, expected 1
  COMMIT;
  SELECT count(*) FROM t1;   -- 0, expected 1

Reproduced with default settings on 18.6 (REL_18_STABLE a85b5523e67),
14.24 and master 158b6d5109 (all --enable-cassert --enable-debug, macOS
arm64); also found on master on Ubuntu x86_64. Rechecked on 2026-10-15
(Ubuntu 24.04, x86_64, gcc 13.3, --enable-cassert --enable-debug, server
under ulimit -v 6 GB):
the same on 19rc1 (REL_19_STABLE 0fb192f1b02), master aa7b9cf132b and
REL_18_STABLE 4d62ef92fda. CLUSTER VERBOSE reports a
negative "dead row versions cannot be removed yet" count (-1 here).

Found with a query fuzzer.








view thread (30+ messages)  latest in thread

Message-ID: <19760-8f9a0eba17bc8c92@postgresql.org>
Permalink:  ../19760-8f9a0eba17bc8c92@postgresql.org/
Also on:    postgresql.org/message-id/19760-8f9a0eba17bc8c92@postgresql.org

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, alpkeles99@gmail.com
  Subject: Re: BUG #19760: CLUSTER loses a row the transaction inserted and then updated in a rolled-back subtransaction
  In-Reply-To: <19760-8f9a0eba17bc8c92@postgresql.org>
  References: <19760-8f9a0eba17bc8c92@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