Re: Add more information_schema columns - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Add more information_schema columns
Date
Msg-id 20180213230155.3rf3he6ypn677yfd@alap3.anarazel.de
Whole thread Raw
In response to Re: Add more information_schema columns  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Add more information_schema columns  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2018-02-07 10:50:12 -0500, Peter Eisentraut wrote:
> On 2/7/18 00:14, Michael Paquier wrote:
> > On Tue, Feb 06, 2018 at 10:45:52PM -0500, Peter Eisentraut wrote:
> >> I think what I had meant to write was something like
> >>
> >>     (t.tgtype & (1 | 66))
> >>
> >> but maybe it's clearer to write it all out as you did.
> > 
> > If you prefer that, that's fine for me as well.  I tend to prefer the
> > formulation where both expressions are separated to make clearer that
> > ordering needs to be split for all three characteristics.
> 
> Committed with the separate entries.

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...

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Client Connection redirection support for PostgreSQL
Next
From: Nikita Glukhov
Date:
Subject: Re: jsonpath