| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| 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-07 21:59:40 |
| Message-ID: | 23206.1415397580@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 11/07/2014 10:51 AM, Ross Reedstrom wrote:
>> row_to_json() yields empty strings for json keys if the data is
>> fulfilled by an index only scan.
> Could this be a bug in lookup_rowtype_tupdesc()?
I think this is probably a variant of bug #11210, in which the problem is
that tupledescs bubbled up from inheritance children never get column
names assigned to them. I've been speculating about ways to fix that
but I've not thought of anything that's not kinda painful.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-11-07 22:03:35 | Re: recovery_target_time and standby_mode |
| Previous Message | Robert Haas | 2014-11-07 21:51:53 | Re: split builtins.h to quote.h |