Re: Triconsistent catalog declaration - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Triconsistent catalog declaration
Date
Msg-id CA+TgmoaKeKPFZw5ZX6KP2_itamsYApFV0FkxQJm9vFmmdreXCw@mail.gmail.com
Whole thread Raw
In response to Re: Triconsistent catalog declaration  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Triconsistent catalog declaration
Re: Triconsistent catalog declaration
List pgsql-hackers
On Mon, Sep 15, 2014 at 10:13 AM, Heikki Linnakangas
<hlinnakangas@vmware.com> wrote:
> That makes for a bit awkward input and output from psql, when the values
> used are 0, 1, 2, rather than ascii characters. But that's OK, because as
> you said these functions are not callable from psql anyway, as they have
> "internal" arguments.

Maybe we should change them to something a bit more understandable.

> This requires a catalog change to fix. Are we still planning to do a
> catversion bump for 9.4 because of the jsonb changes?

That was my understanding, although we seem to be proceeding at an
inexplicably glacial pace.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: B-Tree support function number 3 (strxfrm() optimization)
Next
From: Peter Geoghegan
Date:
Subject: Re: B-Tree support function number 3 (strxfrm() optimization)