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

From Marti Raudsepp
Subject Re: Text-any concatenation volatility acting as optimization barrier
Date
Msg-id CABRT9RB4-=ScOe00LN_N59b6Z84W0bz1Zc40Ccc93tyBKa7aKQ@mail.gmail.com
Whole thread Raw
In response to Re: Text-any concatenation volatility acting as optimization barrier  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Text-any concatenation volatility acting as optimization barrier  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
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?

Regards,
Marti


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Text-any concatenation volatility acting as optimization barrier
Next
From: Andrew Dunstan
Date:
Subject: Re: Text-any concatenation volatility acting as optimization barrier