[fixed] Trigger test

From: Dmitrii Bondar <d(dot)bondar(at)postgrespro(dot)ru>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org, bruce(at)momjian(dot)us
Subject: [fixed] Trigger test
Date: 2025-01-29 09:53:07
Message-ID: 79755a2b18ed4fe5e29da6a87a1e00d1@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi, Hackers!

I was testing a connection pooler with `make installcheck` and noticed
that `check_foreign_key()` from the `refint` library reuses the same
cached plan for cascade `UPDATE`/`DELETE` operations. As a result, a
cascade `DELETE` is applied after an `UPDATE` command on the primary key
table (which should not happen after the commit
https://github.com/postgres/postgres/commit/d489fdfc7f4ccf0010fe0397e7272bdfc257e8f2)
I have attached a file (test.sql) to reproduce an issue and the
solution.

Regards,
Dmitrii Bondar.

Attachment Content-Type Size
test.sql text/plain 1.1 KB
v1-0001-Triggers-test-fix.patch text/x-diff 4.2 KB

Browse pgsql-hackers by date

  From Date Subject
Next Message Maxim Orlov 2025-01-29 09:58:55 Re: postgres_fdw could deparse ArrayCoerceExpr
Previous Message Shubham Khanna 2025-01-29 09:43:55 Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.