From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16137: pg_upgrade fails with an index over nesting function
Date: Mon, 25 Nov 2019 18:18:25 -0500
Message-ID: <10565.1574723905@sss.pgh.pa.us> (raw)
In-Reply-To: <16137-4917a81e8491110e@postgresql.org>
References: <16137-4917a81e8491110e@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> CREATE TABLE test(i INT PRIMARY KEY);
> CREATE FUNCTION func2(i INT) RETURNS INT IMMUTABLE LANGUAGE SQL
> AS 'SELECT $1';
> CREATE FUNCTION func1(c INT) RETURNS INT IMMUTABLE LANGUAGE SQL
> AS 'SELECT func2($1)';
This function is unreliable for lack of schema qualification.
I tend to agree that it'd be nice if pg_upgrade wouldn't be
so picky about that, but we haven't really found a way that
doesn't create security issues (cf CVE-2018-1058).
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, exclusion@gmail.com
Subject: Re: BUG #16137: pg_upgrade fails with an index over nesting function
In-Reply-To: <10565.1574723905@sss.pgh.pa.us>
References: <16137-4917a81e8491110e@postgresql.org> <10565.1574723905@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