Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks
Date
Msg-id CA+hUKG+HeXeDEPBU-f0ZMViy+=VP5O8FVeLhz7u7BvXtaobv+g@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks  (Alex Aktsipetrov <alex.akts@gmail.com>)
Responses Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks  (Thomas Munro <thomas.munro@gmail.com>)
List 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
rightidea.
 

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



pgsql-bugs by date:

Previous
From: Alex Aktsipetrov
Date:
Subject: Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks
Next
From: Gert van Dijk
Date:
Subject: FDW does not push down LIMIT & ORDER BY with sharding (partitions)