Re: Two more RI fast-path issues

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Two more RI fast-path issues
Date: 2026-11-18 06:00:00
Message-ID: df7e1f0a-0b4e-4f21-8789-be029e7b40cf@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Amit,

08.10.2026 06:58, Amit Langote wrote:
> On Wed, Oct 7, 2026 at 10:02 PM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
>> On Tue, Oct 6, 2026 at 3:20 PM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
>> ...
>> Barring comments, would like to push the attached slightly updated
>> version (comment, commit message fixes) tomorrow after committing the
>> patches in [1] because I rebased these over those other patches.
> I've pushed these.

I've accidentially discovered that a test case added with 061065e28 can
produce a new assertion failure with just:
-    UPDATE fp_pk_cid SET v = v + 1 WHERE id OPERATOR(pg_catalog.=) $1;
+    UPDATE fp_pk_cid SET id = id + 1 WHERE id OPERATOR(pg_catalog.=) $1;

TRAP: failed Assert("entry->data.lockmode == BUFFER_LOCK_UNLOCK"), File: "bufmgr.c", Line: 5941, PID: 2303915
ExceptionalCondition at assert.c:51:13
BufferLockAcquire at bufmgr.c:5948:2
LockBufferInternal at bufmgr.c:6631:3
LockBuffer at bufmgr.h:340:1
_bt_lockbuf at nbtpage.c:1072:1
_bt_getbuf at nbtpage.c:839:2
_bt_getroot at nbtpage.c:380:13
_bt_search at nbtsearch.c:113:8
_bt_search_insert at nbtinsert.c:385:1
_bt_doinsert at nbtinsert.c:170:10
btinsert at nbtree.c:225:11
index_insert at indexam.c:235:9
ExecInsertIndexTuples at execIndexing.c:450:4
ExecUpdateEpilogue at nodeModifyTable.c:2372:20
ExecUpdate at nodeModifyTable.c:2754:19
ExecModifyTable at nodeModifyTable.c:4801:12
ExecProcNodeFirst at execProcnode.c:470:1
...
2026-11-18 07:06:47.374 EET postmaster[2302673] LOG:  client backend (PID 2303915) was terminated by signal 6: Aborted
2026-11-18 07:06:47.374 EET postmaster[2302673] DETAIL:  Failed process was running: INSERT INTO fp_fk_cid VALUES (1);

Could you please have a look?

Best regards,
Alexander

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Koshino Taiki 2026-11-18 06:28:25 Re: Proposal: Include CHECK constraint expression in violation error DETAIL
Previous Message Chao Li 2026-11-18 05:40:38 Re: pg_basebackup: check timeline history file write failures in ReceiveXlogStream()