Re: Fuzzy thinking in is_publishable_class - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Fuzzy thinking in is_publishable_class
Date
Msg-id CA+TgmoaJSyZGG0kZWqqfHvM8JrRrP1wo05gXimdN+8X8WL4zNg@mail.gmail.com
Whole thread Raw
In response to Re: Fuzzy thinking in is_publishable_class  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, May 9, 2019 at 9:41 AM Tom Lane <tgl@sss.pgh.pa.us> 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.

+1

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Unlogged tables cleanup
Next
From: Alexander Kuzmenkov
Date:
Subject: Re: Removing unneeded self joins