From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Barton <barton.tomas@gmail.com>
Cc: pgsql-bugs@postgresql.org
Subject: Re: Segmentation fault on postgresql 13.4, 12.8 with function call in a cursor
Date: Thu, 09 Sep 2021 12:14:37 -0400
Message-ID: <3684713.1631204077@sss.pgh.pa.us> (raw)
In-Reply-To: <CAPV2KRjd=ErgVGbvO2Ty20tKTEZZr6cYsYLxgN_W3eAo9pf5sw@mail.gmail.com>
References: <CAPV2KRjd=ErgVGbvO2Ty20tKTEZZr6cYsYLxgN_W3eAo9pf5sw@mail.gmail.com>
Tomas Barton <barton.tomas@gmail.com> writes:
> a recent change in postgresql is causing a segfault when a function is
> called in filter section, e.g. with a plan like this:
Ugh, thanks. PersistHoldablePortal isn't being cautious about
re-executing a plan that already reached completion. Will fix.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, barton.tomas@gmail.com
Subject: Re: Segmentation fault on postgresql 13.4, 12.8 with function call in a cursor
In-Reply-To: <3684713.1631204077@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox