From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Tighten pg_upgrade's new check for non-upgradable anyarray usage
Date: Tue, 05 Jul 2022 22:23:44 +0000
Message-ID: <E1o8qxL-001Ntf-2v@gemulon.postgresql.org> (raw)
Tighten pg_upgrade's new check for non-upgradable anyarray usages.
We only need to reject cases when the aggregate or operator is
itself declared with a polymorphic type. Per buildfarm.
Discussion: https://postgr.es/m/3383880.QJadu78ljV@vejsadalnx
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/08385ed261965c4e1604e357330ac5bf9755b01a
Modified Files
--------------
src/bin/pg_upgrade/check.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
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-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us
Subject: Re: pgsql: Tighten pg_upgrade's new check for non-upgradable anyarray usage
In-Reply-To: <E1o8qxL-001Ntf-2v@gemulon.postgresql.org>
References: <E1o8qxL-001Ntf-2v@gemulon.postgresql.org>
* 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