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

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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 13:30:15
Message-ID: CAFj8pRBLR7rJAo5Ki9uw=XJnefJU7jRaAYSAaQYLPfK2rDQC6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

pá 17. 6. 2022 v 15:07 odesílatel Robert Haas <robertmhaas(at)gmail(dot)com>
napsal:

> On Thu, Jun 16, 2022 at 10:01 PM Justin Pryzby <pryzby(at)telsasoft(dot)com>
> wrote:
> > > Also, I'd be inclined to reject system-provided objects by checking
> > > for OID >= 16384 rather than hard-wiring assumptions about things
> > > being in pg_catalog or not.
> >
> > 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.
>

yes

Unfortunately, I did it in Orafce

Regards

Pavel

> --
> Robert Haas
> EDB: http://www.enterprisedb.com
>
>
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-06-17 14:14:13 Re: pg_upgrade (12->14) fails on aggregate
Previous Message Robert Haas 2022-06-17 13:07:21 Re: pg_upgrade (12->14) fails on aggregate

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-06-17 14:14:13 Re: pg_upgrade (12->14) fails on aggregate
Previous Message Robert Haas 2022-06-17 13:07:21 Re: pg_upgrade (12->14) fails on aggregate