Re: row_to_json bug with index only scans: empty keys!

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ross Reedstrom <reedstrm(at)rice(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: row_to_json bug with index only scans: empty keys!
Date: 2014-11-10 15:30:53
Message-ID: 5460DA2D.9010906@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 11/10/2014 10:19 AM, Robert Haas wrote:
> On Mon, Nov 10, 2014 at 10:11 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
>

+1

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2014-11-10 15:48:16 Re: Compiler warning in master branch
Previous Message Ross Reedstrom 2014-11-10 15:30:21 Re: row_to_json bug with index only scans: empty keys!