Re: Text-any concatenation volatility acting as optimization barrier

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Text-any concatenation volatility acting as optimization barrier
Date: 2012-02-08 17:23:44
Message-ID: 4F32AFA0.9010703@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/08/2012 11:20 AM, Tom Lane wrote:
> I am going to go ahead and commit the patch with the altered json
> results, because IMO it is mere accident that these regression cases
> were coming out with "nice" field labels anyway. When and if Andrew
> gets the RowExpr cases fixed properly, that will show up as these
> cases going back to nicer-looking output.

I take it this is your way of making me hurry up with that work :-)

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-02-08 17:48:20 Re: [PATCH] Enable min/max optimization for bool_and/bool_or/every
Previous Message Peter Geoghegan 2012-02-08 16:53:37 Re: Progress on fast path sorting, btree index creation time