Horton

Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks

Thomas Munro <thomas.munro@gmail.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@gmail.com>
To: Alex Aktsipetrov <alex.akts@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>, Andres Freund <andres@anarazel.de>
Date: 2019-07-08T23:49:19Z
Lists: pgsql-bugs 
On Tue, Jul 9, 2019 at 11:39 AM Alex Aktsipetrov <alex.akts@gmail.com> wrote:
> Attaching the patch that fixes the issue, although I am not familiar with the codebase to be sure that it is the right idea.

Thanks for the report and the proposed fix!

Hmm, I wonder if EPQ might be involved in bug report #15720 (version 11.2):

https://www.postgresql.org/message-id/flat/15720-38c2b29e5d720187%40postgresql.org

-- 
Thomas Munro
https://enterprisedb.com

Commits

  1. Pass QueryEnvironment down to EvalPlanQual's EState.

  2. Store tuples for EvalPlanQual in slots, rather than as HeapTuples.