| From: | Joe Van Dyk <joe(at)tanga(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: querying jsonb for arrays inside a hash |
| Date: | 2015-11-09 17:13:48 |
| Message-ID: | CACfv+pLH3Z7ox-H9o01x805H03OpyGoOczVti2PuDtTYfrwPTQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
You're right, brain fart. Nevermind! :)
On Sat, Nov 7, 2015 at 4:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Joe Van Dyk <joe(at)tanga(dot)com> writes:
> > I noticed that querying for
> > product_attributes @> '{"upsell":["true"]}'
> > is much slower than querying for
> > product_attributes @> '{"upsell": 1}'
>
> > Is that expected?
>
> Your EXPLAIN results say that the first query matched 135843 rows and the
> second one none at all, so a significant variation in runtime doesn't seem
> that surprising to me ...
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Osborne | 2015-11-10 12:13:21 | Slow 3 Table Join with v bad row estimate |
| Previous Message | Tom Lane | 2015-11-08 00:00:21 | Re: querying jsonb for arrays inside a hash |