Re: pg_upgrade (12->14) fails on aggregate

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Petr Vejsada <pve(at)paymorrow(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_upgrade (12->14) fails on aggregate
Date: 2022-06-17 14:14:13
Message-ID: 1216673.1655475253@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Jun 16, 2022 at 10:01 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
>> To me, oid>=16384 seems more hard-wired than namespace!='pg_catalog'.

> Extensions can be installed into pg_catalog, but they can't get
> low-numbered OIDs.

Exactly. (To be clear, I had in mind writing something involving
FirstNormalObjectId, not that you should put literal "16384" in the
code.)

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Derek Zasiewski 2022-06-17 17:03:28 Issue with SSL and password protected keys in DER/PK8 format
Previous Message Pavel Stehule 2022-06-17 13:30:15 Re: pg_upgrade (12->14) fails on aggregate

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-06-17 14:33:08 Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size
Previous Message Pavel Stehule 2022-06-17 13:30:15 Re: pg_upgrade (12->14) fails on aggregate