Re: row_to_json bug with index only scans: empty keys! - Mailing list pgsql-hackers

From Robert Haas
Subject Re: row_to_json bug with index only scans: empty keys!
Date
Msg-id CA+TgmoZhtpaGRW3c+M2Y0V3haC6wrK4SA-mLRSjr5-Yom1scqA@mail.gmail.com
Whole thread Raw
In response to Re: row_to_json bug with index only scans: empty keys!  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: row_to_json bug with index only scans: empty keys!  (Andrew Dunstan <andrew@dunslane.net>)
Re: row_to_json bug with index only scans: empty keys!  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Nov 10, 2014 at 10:11 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I wrote:
>> Attached are patches meant for HEAD and 9.2-9.4 respectively.
>
> BTW, has anyone got an opinion about whether to stick the full fix into
> 9.4?  The argument for, of course, is that we'd get the full fix out to
> the public a year sooner.  The argument against is that someone might
> have already done compatibility testing of their application against
> 9.4 betas, and then get blindsided if we change this before release.
>
> I'm inclined to think that since we expect json/jsonb usage to really
> take off with 9.4, it might be better if we get row_to_json behaving
> unsurprisingly now.  But I'm not dead set on it.

I think we should put the full fix in 9.4.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: row_to_json bug with index only scans: empty keys!
Next
From: Magnus Hagander
Date:
Subject: Re: remove pg_standby?