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
