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

On 11/08/2014 12:14 PM, Tom Lane wrote:
>> I assume that's what you would propose for just the stable branches, and
>> that going forward we'd always use the aliases from the RTE?
> That would be my druthers.  But given the lack of complaints, maybe we
> should just stick to the more-backwards-compatible behavior until someone
> does complain.  Thoughts?
>
>             


Wouldn't that would mean we might not pick up the expected aliases in
    select row_to_json(q) from (select a,b from foo) as q(x,y)

? If so, I'm definitely in favor of fixing this now.

cheers

andrew