Re: [GENERAL] Possible bug with row_to_json

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Jack Christensen <jack(at)jackchristensen(dot)com>
Subject: Re: [GENERAL] Possible bug with row_to_json
Date: 2014-01-31 23:00:05
Message-ID: 4953.1391209205@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Tue, Aug 13, 2013 at 05:34:12PM -0400, Tom Lane wrote:
>> Further poking at this issue shows that there are related behaviors that
>> aren't fixed by my proposed patch.

> Where are we on this?

Still have no idea how to fix the whole-row-Var case. We could fix some
of these behaviors, but I'm inclined to think we should wait, and take
all the related compatibility hits at once.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2014-02-01 01:00:47 Re: pg_basebackup on standby node failed
Previous Message Bruce Momjian 2014-01-31 22:40:40 Re: [GENERAL] Possible bug with row_to_json

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-01-31 23:01:38 Re: WITH ORDINALITY planner improvements
Previous Message Michael Paquier 2014-01-31 22:49:53 Re: FOR UPDATE/SHARE incompatibility with GROUP BY, DISTINCT, HAVING and window functions