Re: Text-any concatenation volatility acting as optimization barrier - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Text-any concatenation volatility acting as optimization barrier
Date
Msg-id 4F32AFA0.9010703@dunslane.net
Whole thread Raw
In response to Re: Text-any concatenation volatility acting as optimization barrier  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Text-any concatenation volatility acting as optimization barrier
List 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


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Progress on fast path sorting, btree index creation time
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Enable min/max optimization for bool_and/bool_or/every