Re: Eliminating SPI / SQL from some RI triggers - take 3

Sandro Santilli <strk@kbt.io>

From: Sandro Santilli <strk@kbt.io>
To: Amit Langote <amitlangote09@gmail.com>
Cc: Tomas Vondra <tomas@vondra.me>, Junwang Zhao <zhjwpku@gmail.com>, Pavel Stehule <pavel.stehule@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2026-04-10T18:35:36Z
Lists: pgsql-hackers
On Fri, Apr 10, 2026 at 01:14:11PM +0900, Amit Langote wrote:
> 
> I have just pushed 0001 which you'll find in master as 34a3078629.

No crash with commit 2a3d2f9f68da0c430c497bf29f60373f5214307d
(which includes 34a3078629).

Thank you !

--strk;

  Libre GIS consultant/developer ๐ŸŽบ
  https://strk.kbt.io/services.html

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference โ†’
  1. Fix some const qualifier use in ri_triggers.c

  2. doc: Improve consistency of parallel vacuum description.

  3. Move afterTriggerFiringDepth into AfterTriggersData

  4. Fix typo left by 34a30786293

  5. Fix RI fast-path crash under nested C-level SPI

  6. Add nkeys parameter to recheck_matched_pk_tuple()

  7. Fix deferred FK check batching introduced by commit b7b27eb41a5

  8. Optimize fast-path FK checks with batched index probes

  9. Make FastPathMeta self-contained by copying FmgrInfo structs

  10. Add fast path for foreign key constraint checks