From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add more information_schema columns |
Date: | 2018-02-16 21:46:25 |
Message-ID: | dff81905-79a7-933e-24af-ddc05868c8cc@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/13/18 18:39, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> Do we have a policy about catversion bumps for information schema
>> changes? A cluster from before this commit fails the regression tests
>> after the change, but still mostly works...
>
> I think historically we've not bumped catversion, on the grounds that
> there's no incompatibility with the backend as such. However, it is
> kind of annoying that not updating means the regression tests fail.
> Informally, I'm sure most developers take "catversion bump" to mean
> "you need to initdb". So I'd support saying that an information_schema
> change should include a catversion bump if it involves any changes in
> regression test results.
I will do that in the future if that is the preference.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2018-02-16 21:46:42 | Re: ALTER TABLE ADD COLUMN fast default |
Previous Message | Peter Eisentraut | 2018-02-16 21:23:46 | Re: Cancelling parallel query leads to segfault |