Re: Text-any concatenation volatility acting as optimization barrier

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Marti Raudsepp <marti(at)juffo(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Text-any concatenation volatility acting as optimization barrier
Date: 2012-02-07 21:01:21
Message-ID: 4F319121.6060608@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/07/2012 03:36 PM, Marti Raudsepp wrote:
> On Tue, Feb 7, 2012 at 22:31, Andrew Dunstan<andrew(at)dunslane(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2012-02-07 21:22:11 Re: Checkpoint sync pause
Previous Message Simon Riggs 2012-02-07 20:58:59 Re: 16-bit page checksums for 9.2