On Sat, Oct 13, 2018 at 3:57 AM Robert Haas <robertmh...@gmail.com> wrote:
> On Wed, Oct 10, 2018 at 8:27 AM Haribabu Kommi <kommi.harib...@gmail.com> > wrote: > > Here is the patch as per the above discussion. > > One potential problem with this is that we could add more control-file > attributes in the future, and it will be annoying if the view ends up > with a million columns, or if we ever have to rename them. Yes, there is a problem if we add more attributes or rename them. > People who > have created objects that depend on those views may find that > pg_dump/restore or pg_upgrade fail, just as they do when we whack > around pg_stat_activity. pg_settings gets around that using an > EAV-like format. I'm not sure that's the best solution here, but it's > something to think about. > similar like pg_settings view, so displaying all the data without validating them from pg_extension may solve the problem. Other idea to avoid this problem is, how about displaying the extra columns using JSONB data type, so that all the extra additional columns that are not important will go to that column? Regards, Haribabu Kommi Fujitsu Australia
