| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fuzzy thinking in is_publishable_class |
| Date: | 2019-05-13 15:32:40 |
| Message-ID: | CA+TgmoaJSyZGG0kZWqqfHvM8JrRrP1wo05gXimdN+8X8WL4zNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 9, 2019 at 9:41 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-05-13 16:21:22 | Re: PostgreSQL 12: Feature Highlights |
| Previous Message | Robert Haas | 2019-05-13 15:28:32 | Re: [HACKERS] Unlogged tables cleanup |