| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Fuzzy thinking in is_publishable_class |
| Date: | 2019-05-23 13:13:00 |
| Message-ID: | 139b3cf5-5add-03f0-53f2-6a6762b19b42@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-05-23 13:14:59 | Re: [HACKERS] Unlogged tables cleanup |
| Previous Message | Robert Haas | 2019-05-23 13:10:44 | Re: Remove useless associativity/precedence from parsers |