From: Tom Lane <tgl@sss.pgh.pa.us>
To: pinker <pinker@onet.eu>
cc: pgsql-bugs@postgresql.org
Subject: Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent
 machines
In-reply-to: <1603069348354-0.post@n3.nabble.com>
References: <1603050466566-0.post@n3.nabble.com>
 <1603050580276-0.post@n3.nabble.com> <235509.1603051243@sss.pgh.pa.us>
 <1603051414438-0.post@n3.nabble.com> <236292.1603052323@sss.pgh.pa.us>
 <1603057047424-0.post@n3.nabble.com> <247080.1603065654@sss.pgh.pa.us>
 <247889.1603066736@sss.pgh.pa.us> <1603069348354-0.post@n3.nabble.com>
Comments: In-reply-to pinker <pinker@onet.eu>
	message dated "Sun, 18 Oct 2020 18:02:28 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <432921.1603133221.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Oct 2020 14:47:01 -0400
Message-ID: <432922.1603133221@sss.pgh.pa.us>
Precedence: bulk

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=3Dpostgresql.git;a=3Dpatch;h=3D25378d=
b74fd97f2b10ad44d1f0b2e1f8b0a651f2

and see whether it takes care of all the cases you noticed.

			regards, tom lane