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

Поиск
Список
Период
Сортировка
От Thomas Munro
Тема Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks
Дата
Msg-id CA+hUKG+HeXeDEPBU-f0ZMViy+=VP5O8FVeLhz7u7BvXtaobv+g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks  (Alex Aktsipetrov <alex.akts@gmail.com>)
Ответы Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks  (Thomas Munro <thomas.munro@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Alex Aktsipetrov
Дата:
Сообщение: Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks
Следующее
От: Gert van Dijk
Дата:
Сообщение: FDW does not push down LIMIT & ORDER BY with sharding (partitions)