Re: BUG #19760: CLUSTER loses a row the transaction inserted and then updated in a rolled-back subtransaction

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Takeshi Ideriha <iderihatakeshi(at)gmail(dot)com>
Cc: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, alpkeles99(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19760: CLUSTER loses a row the transaction inserted and then updated in a rolled-back subtransaction
Date: 2026-10-20 02:22:21
Message-ID: CAGRkXqSo9vZ=7mw_X0tjH1-Wwdz8nWu9xpdX1x8hVM8tCazKAA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Takeshi,

> So I believe we can just rely on HeapTupleHeaderXminInvalid hint bit.

I tried it and it keeps the row in both cases. But it also needs the
logical_rewrite_heap_tuple() call in end_heap_rewrite(). Without it,
logical decoding after VACUUM FULL pg_class fails:

ERROR: could not map filenumber "base/16490/16491" to relation OID

Thanks,
Shihao

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Takeshi Ideriha 2026-10-20 02:32:44 Re: BUG #19760: CLUSTER loses a row the transaction inserted and then updated in a rolled-back subtransaction
Previous Message Narayanan Venkateswaran 2026-10-19 20:23:54 Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses