Re: Partial index on JSON column

From: Samuel Williams <space(dot)ship(dot)traveller(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Partial index on JSON column
Date: 2019-02-20 00:39:18
Message-ID: CAHkN8V-oq12JB8D5A-5NyF3gXkWQY4ohx7Bfecmud0VRG=nPSw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks Tom, I did solve the problem by adding the null constraint for now,
it's a quick solution, and I look forward to the future where this case is
handled appropriately.

On Wed, 20 Feb 2019 at 12:17, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I wrote:
> > Try it like
>
> > EXPLAIN SELECT COUNT(*) FROM "user_event" WHERE ((parameters ->>
> > 'suggestion_id'::text) = '26') AND what = 'suggestion_notification';
>
> > I don't think we assume that CoerceViaIO is strict, and without that
> > the deduction that the value couldn't be null doesn't hold.
>
> Hmm ... on closer inspection, we do assume that CoerceViaIO is strict,
> but not everyplace knows that, so there's something that could be
> improved here. In the meantime, try it as stated above.
>
> regards, tom lane
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Mike Yeap 2019-02-20 10:12:59 LDAP authenticated session terminated by signal 11: Segmentation fault, PostgresSQL server terminates other active server processes
Previous Message Tom Lane 2019-02-19 23:17:39 Re: Partial index on JSON column