Re: Segmentation fault on postgresql 13.4, 12.8 with function call in a cursor

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Tomas Barton <barton.tomas@gmail.com>

Cc: pgsql-bugs@postgresql.org

Date: 2021-09-09T16:14:37Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Avoid fetching from an already-terminated plan.
- cba79a163267 15.0 landed
- b7056c0a25e5 14.0 landed
- d8d93bc8baa9 13.5 landed
- 7813451c20c3 11.14 landed
- 2e75e969c88f 12.9 landed
Avoid misbehavior when persisting a non-stable cursor.
- c1fd756fd23f 13.4 cited

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