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