Re: [PATCH] refint: Avoid reusing cascade UPDATE plans.

On 2026-May-15, Nathan Bossart wrote:

> Yeah, this may be the best option.  I'm curious what others think.

I think this bug makes it clear that this code has few enough users, and
a sufficient number of bugs, that we should just nuke it.  Do you really
want to spend so much time trying to fix it?  The module's documentation
says

   (This functionality is long since superseded by the built-in foreign
   key mechanism, of course, but the module is still useful as an example.)

but I question whether the usefulness value is really there.

Would anyone oppose that?

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"How amazing is that? I call it a night and come back to find that a bug has
been identified and patched while I sleep."                (Robert Davidson)
               http://archives.postgresql.org/pgsql-sql/2006-03/msg00378.php