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

From: Sandro Santilli <strk(at)kbt(dot)io>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, Junwang Zhao <zhjwpku(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Eliminating SPI / SQL from some RI triggers - take 3
Date: 2026-04-09 11:07:50
Message-ID: adeIhgpWq22E5kwW@hst.kbt.io
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 02, 2026 at 01:34:41PM +0100, Tomas Vondra wrote:
>
> TBH I haven't noticed the memory context issue myself, I only noticed
> because the builds with index prefetch started crashing.

We're getting a crash in PostGIS too, since that commit was merged into
the master branch, see https://trac.osgeo.org/postgis/ticket/6066

The crash is triggered a C function using SPI.

--strk;

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2026-04-09 11:28:24 Re: Reduce build times of pg_trgm GIN indexes
Previous Message Jim Jones 2026-04-09 11:07:12 Re: Additional message in pg_terminate_backend