Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pinker <pinker(at)onet(dot)eu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
Date: 2020-10-19 00:18:56
Message-ID: 247889.1603066736@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Oh, here's a simpler reproducer:

create or replace function foo (out schemaname text, out relname text)
returns setof record language sql
as $$
select nspname, relname from pg_class c join pg_namespace n
on (n.oid = relnamespace)
order by 1
$$;

select * from foo();

It doesn't fail without the ORDER BY, suggesting that the problem
is localized in failing to handle the case where a sort key
column needs to be coerced.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pinker 2020-10-19 01:02:28 Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
Previous Message Tom Lane 2020-10-19 00:00:54 Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines