Re: [GENERAL] Possible bug with row_to_json

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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: 2013-08-13 22:13:53
Message-ID: CAHyXU0zPbVEwCOu591e8UANqL-uZ1=-DFEbGJLPixXVnNZvYBA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Tue, Aug 13, 2013 at 4:34 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Since this behavior can also be demonstrated in 9.2 (and maybe further
> back using xml features?), I don't think we should consider it a
> blocker bug for 9.3. I'm planning to set it on the back burner for
> the moment and go worry about the planner's LATERAL bugs.

+1

merlin

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Sergey Konoplev 2013-08-13 22:32:38 Re: Performance of ORDER BY RANDOM to select random rows?
Previous Message Robert James 2013-08-13 22:05:26 What type of index do I need for this JOIN?

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2013-08-14 00:07:06 Re: Regarding BGworkers
Previous Message Tom Lane 2013-08-13 21:34:12 Re: [GENERAL] Possible bug with row_to_json