pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed

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
Date: Sun, 18 Oct 2020 20:18:56 -0400
Message-ID: <247889.1603066736@sss.pgh.pa.us> (raw)
In-Reply-To: <247080.1603065654@sss.pgh.pa.us>
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>

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

view thread (17+ messages)  latest in thread

Message-ID: <247889.1603066736@sss.pgh.pa.us>
Permalink:  ../247889.1603066736@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/247889.1603066736@sss.pgh.pa.us

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pinker@onet.eu
  Subject: Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
  In-Reply-To: <247889.1603066736@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox