Request a Demo
Home   >   mailing lists

Re: Unexpected planner behavior with *_pattern_ops index matching - Mailing list pgsql-general

From Tom Lane
Subject Re: Unexpected planner behavior with *_pattern_ops index matching
Date
Msg-id 19641.1414678595@sss.pgh.pa.us
Whole thread Raw
In response to Unexpected planner behavior with *_pattern_ops index matching  (Fabio Ugo Venchiarutti <fabio@vuole.me>)
Responses Re: Unexpected planner behavior with *_pattern_ops index matching
List pgsql-general
Tree view 
Fabio Ugo Venchiarutti <fabio@vuole.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

pgsql-general by date:

Previous
From: Karsten Hilbert
Date:
Subject: PostgreSQL on tablet grade SSD ?
Next
From: Adrian Klaver
Date:
Subject: Re: Appending new data to existing field of Json data type