Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pinker <pinker@onet.eu>
Cc: pgsql-bugs@postgresql.org
Date: 2020-10-19T18:47:01Z
Lists: pgsql-bugs
pinker <pinker@onet.eu> writes: > I've changed all name data types to text and running a query on a simple > table with another function and it is still crashing :/ > yeah, removing ORDER BY helps here also... Hard to comment on that when you haven't shown an example. Anyway, I've identified the issue with the presented example and pushed a fix. If you're in a position to rebuild Postgres locally you could try applying https://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=25378db74fd97f2b10ad44d1f0b2e1f8b0a651f2 and see whether it takes care of all the cases you noticed. regards, tom lane
Commits
-
Fix list-munging bug that broke SQL function result coercions.
- 25378db74fd9 13.1 landed
- c8ab9701791e 14.0 landed