Re: Unexpected planner behavior with *_pattern_ops index matching

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: fabio(at)vuole(dot)me
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Unexpected planner behavior with *_pattern_ops index matching
Date: 2014-10-30 14:16:35
Message-ID: 19641.1414678595@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Fabio Ugo Venchiarutti <fabio(at)vuole(dot)me> writes:
> As you can see, CONCAT()'s output isn't deemed suitable for an index
> scan. The same happens for all type-compatible STABLE functions i tried.

Conversion of the pattern to an index qualification requires that the
pattern be a plan-time constant. STABLE functions, by definition,
are not that.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2014-10-30 14:21:49 Re: Appending new data to existing field of Json data type
Previous Message Karsten Hilbert 2014-10-30 09:30:39 PostgreSQL on tablet grade SSD ?