Re: BUG #17916: Expression IN list translates to unqualified operator

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: RekGRpth <rekgrpth(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17916: Expression IN list translates to unqualified operator
Date: 2023-05-03 14:43:18
Message-ID: CAKFQuwbLKduuWpS5Ld9HaWV8JiHw6XfZvLMLPf6D5NAOCAuO9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, May 3, 2023 at 6:43 AM RekGRpth <rekgrpth(at)gmail(dot)com> wrote:

> How can I safely use an expression IN list in extensions?
>
>
search_path control is your only knob if you want to use IN. Otherwise,
you can typically reformulate an IN expression into an "op ANY" expression
and then "op" can be schema-qualified.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Cyrus Lozano 2023-05-03 15:18:30 Re: BUG #17917: to_tsquery syntax error
Previous Message Tom Lane 2023-05-03 13:46:13 Re: BUG #17917: to_tsquery syntax error