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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Alex Aktsipetrov <alex(dot)akts(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks
Date: 2019-07-08 23:49:19
Message-ID: CA+hUKG+HeXeDEPBU-f0ZMViy+=VP5O8FVeLhz7u7BvXtaobv+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jul 9, 2019 at 11:39 AM Alex Aktsipetrov <alex(dot)akts(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Gert van Dijk 2019-07-09 00:12:40 FDW does not push down LIMIT & ORDER BY with sharding (partitions)
Previous Message Alex Aktsipetrov 2019-07-08 23:39:23 Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks