Re: [HACKERS] Triconsistent catalog declaration

2014-09-15 Thread Heikki Linnakangas
On 09/15/2014 08:56 PM, Robert Haas wrote: On Mon, Sep 15, 2014 at 10:13 AM, Heikki Linnakangas 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 fro

Re: [HACKERS] Triconsistent catalog declaration

2014-09-15 Thread Tom Lane
Robert Haas writes: > On Mon, Sep 15, 2014 at 10:13 AM, Heikki Linnakangas > wrote: >> 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

Re: [HACKERS] Triconsistent catalog declaration

2014-09-15 Thread Robert Haas
On Mon, Sep 15, 2014 at 10:13 AM, Heikki Linnakangas 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"

Re: [HACKERS] Triconsistent catalog declaration

2014-09-15 Thread Heikki Linnakangas
On 09/15/2014 04:58 PM, Alexander Korotkov wrote: Hi! 9.4 GIN introduces new triconsistent method which can return one of three values in spite of just consistent method. But in catalog declaration triconsistent still returns bool type. It doesn't affect anything because nobody calls triconsiste