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 4F319121.6060608@dunslane.net
Whole thread Raw
In response to Re: Text-any concatenation volatility acting as optimization barrier  (Marti Raudsepp <marti@juffo.org>)
List pgsql-hackers

On 02/07/2012 03:36 PM, Marti Raudsepp wrote:
> On Tue, Feb 7, 2012 at 22:31, Andrew Dunstan<andrew@dunslane.net>  wrote:
>> It gets worse if you replace the expression with a call to a (non-sql)
>> function returning text, which was in fact the original use case. Then
>> you're pretty  much hosed.
> Oh, if it's a non-SQL function then marking it as STABLE/IMMUTABLE
> should solve it -- did you try that?
>


Hmm, your're right. I could have sworn I tried that. That still leaves 
the oddity you reported, though.

cheers

andrew


pgsql-hackers by date:

Previous
From: Marti Raudsepp
Date:
Subject: Re: Text-any concatenation volatility acting as optimization barrier
Next
From: Simon Riggs
Date:
Subject: Re: 16-bit page checksums for 9.2