From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Fuzzy thinking in is_publishable_class
Date: Thu, 23 May 2019 15:13:00 +0200
Message-ID: <139b3cf5-5add-03f0-53f2-6a6762b19b42@2ndquadrant.com> (raw)
In-Reply-To: <2466.1557409276@sss.pgh.pa.us>
References: <15150.1557257111@sss.pgh.pa.us>
<29939.1557369425@sss.pgh.pa.us>
<e0f42cfb-b88f-2528-302b-ef6b96410d35@2ndquadrant.com>
<2466.1557409276@sss.pgh.pa.us>
On 2019-05-09 15:41, Tom Lane wrote:
>> I think we can get rid of the ability to reload the information_schema
>> after initdb. That was interesting in the early phase of its
>> development, but now it just creates complications.
> We've relied on that more than once to allow minor-release updates of
> information_schema views, so I think losing the ability to do it is
> a bad idea.
In those cases we used CREATE OR REPLACE VIEW, which preserves OIDs.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org
Subject: Re: Fuzzy thinking in is_publishable_class
In-Reply-To: <139b3cf5-5add-03f0-53f2-6a6762b19b42@2ndquadrant.com>
* 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