Re: Problems with pg_upgrade and extensions referencing catalog tables/views

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "Nasby, Jim" <nasbyj(at)amazon(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Problems with pg_upgrade and extensions referencing catalog tables/views
Date: 2019-05-10 00:14:07
Message-ID: 20190510001407.xqfihagkglgjrrip@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 8, 2019 at 10:07:23PM +0000, Nasby, Jim wrote:
> I don’t recall why pg_upgrade wants to control OIDs… don’t we
> re-create all catalog entries for user objects from scratch?

The C comment at top of pg_upgrade.c explains why some oids must be preserved:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/bin/pg_upgrade/pg_upgrade.c;h=0b304bbd56ab0204396838618e86dfad757c2812;hb=HEAD

It doesn't mention extensions.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2019-05-10 00:19:59 Re: pg12 release notes
Previous Message Justin Pryzby 2019-05-10 00:13:35 Re: pg12 release notes