[fixed] Trigger test

Dmitrii Bondar <d.bondar@postgrespro.ru>

From: Dmitrii Bondar <d.bondar@postgrespro.ru>

To: pgsql-hackers@lists.postgresql.org, bruce@momjian.us

Date: 2025-01-29T09:53:07Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix some issues in contrib/spi/refint.c.
- 8cfbdf8f4dfb 18.0 landed
I send you a attach of my modified refint.c that
- d489fdfc7f4c 7.1.1 cited

Attachments

test.sql (text/plain)
v1-0001-Triggers-test-fix.patch (text/x-diff) patch v1-0001

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.