Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
Date
Msg-id 247889.1603066736@sss.pgh.pa.us
Whole thread Raw
In response to Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines  (pinker <pinker@onet.eu>)
List 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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
Next
From: pinker
Date:
Subject: Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines