Re: Release SPI plans for referential integrity with DISCARD ALL - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: Release SPI plans for referential integrity with DISCARD ALL
Date
Msg-id CADkLM=dMkUP0kr5u63iLT_B3qk3nFNbcX0Y6gh=f+HukFsjwyA@mail.gmail.com
Whole thread Raw
In response to Release SPI plans for referential integrity with DISCARD ALL  (yuzuko <yuzukohosoya@gmail.com>)
Responses Re: Release SPI plans for referential integrity with DISCARD ALL
List pgsql-hackers
In addition to that, a following case would be solved with this approach:
When many processes are referencing many tables defined foreign key
constraints thoroughly, a huge amount of memory will be consumed
regardless of whether referenced tables are partitioned or not.

Attached the patch.  Any thoughts?

Amit Langote has done some great work at eliminating SPI from INSERT/UPDATE triggers entirely, thus reducing the number of cached plans considerably.

I think he was hoping to have a patch formalized this week, if time allowed.

It doesn't have DELETE triggers in it, so this patch might still have good value for deletes on a commonly used enumeration table.

However, our efforts might be better focused on eliminating SPI from delete triggers as well, an admittedly harder task.

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Deleting older versions in unique indexes to avoid page splits
Next
From: Heikki Linnakangas
Date:
Subject: Re: Yet another fast GiST build