Re: Text-any concatenation volatility acting as optimization barrier

From: Marti Raudsepp <marti(at)juffo(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Text-any concatenation volatility acting as optimization barrier
Date: 2012-02-07 20:36:56
Message-ID: CABRT9RB4-=ScOe00LN_N59b6Z84W0bz1Zc40Ccc93tyBKa7aKQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

Regards,
Marti

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-02-07 20:58:59 Re: 16-bit page checksums for 9.2
Previous Message Andrew Dunstan 2012-02-07 20:31:56 Re: Text-any concatenation volatility acting as optimization barrier