Re: BUG #15720: `executor could not find named tuplestore ABC` in AFTER DELETE trigger referencing OLD TABLE as ABC
Jason Madden <jason.madden@nextthought.com>
From: Jason Madden <jason.madden@nextthought.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thomas Munro <thomas.munro@gmail.com>,
PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2019-07-09T15:55:38Z
Lists: pgsql-bugs
> On Jul 9, 2019, at 10:45, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > > FYI, we're now thinking that the problem here is unrelated to partitions > but instead is a bug in EPQ, which is a subsystem that's entered only when > a row to be locked/updated is found to have just been updated by some > concurrent transaction. See > > https://www.postgresql.org/message-id/flat/15900-bc482754fe8d7415%40postgresql.org > > If you're in a position to build a custom version of Postgres, you > might try whether the patch proposed in that thread resolves your > problem. Thank you for the update. Unfortunately, I no longer work with that system and aren't able to try to reproduce the issue. ~Jason
Commits
-
Pass QueryEnvironment down to EvalPlanQual's EState.
- 72b526779a93 10.10 landed
- 9509173d2430 11.5 landed
- abbb2e143213 12.0 landed
- f5825853e3af 13.0 landed