Re: Unexpected planner behavior with *_pattern_ops index matching

From: Fabio Ugo Venchiarutti <fabio(at)vuole(dot)me>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Unexpected planner behavior with *_pattern_ops index matching
Date: 2014-10-30 22:06:06
Message-ID: 5452B64E.3090400@vuole.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2014-10-30 22:39:06 Re: Unexpected planner behavior with *_pattern_ops index matching
Previous Message Stephen Frost 2014-10-30 19:31:27 Re: Planet Postgres