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

From Tom Lane
Subject Re: row_to_json bug with index only scans: empty keys!
Date
Msg-id 25271.1415632285@sss.pgh.pa.us
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!  (Robert Haas <robertmhaas@gmail.com>)
Re: row_to_json bug with index only scans: empty keys!  (David G Johnston <david.g.johnston@gmail.com>)
Re: row_to_json bug with index only scans: empty keys!  (Ross Reedstrom <reedstrm@rice.edu>)
List pgsql-hackers
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.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Pankaj Bagul
Date:
Subject: Fwd: How parser works and to add keyword to keywords.h
Next
From: Robert Haas
Date:
Subject: Re: row_to_json bug with index only scans: empty keys!