Re: Unexpected planner behavior with *_pattern_ops index matching

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

Thank you very much


I guess it is correct to assume that the same applies to regular
expressions stored in pl/pgsql variables/arguments then, as they're
inspected after the plan is cached?


Is dynamic SQL the recommended/only way around this?


Regards

Fabio Ugo Venchiarutti