Re: automatically assigning catalog toast oids

From: John Naylor <jcnaylor(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: automatically assigning catalog toast oids
Date: 2018-12-14 13:42:55
Message-ID: 3E944265-FEEF-43C3-B174-2234AB7397CB@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 12/13/18, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Looking at the existing entries, it seems like we'd have to have
> one special case: schema public has OID 2200 but is intentionally
> not pinned.

setup_depend() mentions other exceptions, but only this one currently has any effect as far as I can see:

"pg_database: it's a feature, not a bug, that template1 is not pinned."

-John Naylor

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Steele 2018-12-14 13:43:20 Re: Change pgarch_readyXlog() to return .history files first
Previous Message David Steele 2018-12-14 13:27:02 Re: Remove Deprecated Exclusive Backup Mode