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

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, 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-08 17:22:07
Message-ID: 1415467327.82056.YahooMailNeo@web122302.mail.ne1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:

>> 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?

I think consistent use of the aliases would be less surprising and
should be what we do on master. I agree that we should avoid
breaking anything that might be working as intended on stable
branches.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-11-08 17:30:05 Re: row_to_json bug with index only scans: empty keys!
Previous Message Andres Freund 2014-11-08 17:20:05 Re: Add CREATE support to event triggers