From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Jordan Gigov <coladict(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: jsonb problematic operators |
Date: | 2016-12-09 17:40:12 |
Message-ID: | CAKFQuwaPLsp6=Y7Q1JFPF=FqF1tXO6KRNrrRzLb-3rLyuAiE5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Dec 9, 2016 at 10:17 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> As Geoff says, you don't have to use the operators; you could use the
> equivalent functions instead. Every operator just gets turned into a
> function call internally, so this is always possible.
>
In most cases - the decision to tie indexing to operators makes this
imperfect. Whether there is an actual problem with these operators I am
unsure.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2016-12-09 17:54:04 | Re: jsonb problematic operators |
Previous Message | Pavel Stehule | 2016-12-09 17:39:50 | proposal: psql statements \gstore \gstore_binary (instead COPY RAW) |