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

From Andrew Dunstan
Subject Re: row_to_json bug with index only scans: empty keys!
Date
Msg-id 545E8BE9.7020802@dunslane.net
Whole thread Raw
In response to Re: row_to_json bug with index only scans: empty keys!  (Ross Reedstrom <reedstrm@rice.edu>)
List pgsql-hackers
On 11/08/2014 04:19 PM, Ross Reedstrom wrote:
> I've no opinion on the not respecting aliases aspect of this, but both
> the hstore and json emtpy keys case breaks the format: it's duplicate keys
> that collapse to a single value, and expected keynames are missing.
>
> The insidious bit about this bug though is that it works fine during testing
> with the developers typically small data sets. It's only triggered in my case
> when we the plan switches to index-only. Even an index scan works fine. I can't
> imagine that there is code out there that _depends_ on this behavior. Just as
> likely to me are that there exist systems that just have "can't reproduce" bugs
> that would be fixed by this.
>
>


No, I can't imagine it either - it's utterly broken. That's the piece 
that Tom is proposing to fix on the back branches. AIUI.

cheers

andrew



pgsql-hackers by date:

Previous
From: Ross Reedstrom
Date:
Subject: Re: row_to_json bug with index only scans: empty keys!
Next
From: Andres Freund
Date:
Subject: Re: Add CREATE support to event triggers