From: | AlexK987 <alex(dot)cue(dot)987(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Why is GIN index slowing down my query? |
Date: | 2015-02-02 01:37:26 |
Message-ID: | 1422841046401-5836323.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Tom,
This is a realistic case: everyone have Python and Java skills, but PostGis
and Haskell and Closure are rare. If we are looking for a person that has
all the skills required for a task (array[1, 15]), that is "skills <@
array[1, 15] " and not the opposite, right?
Also can you explain why " entries for "0" and "1" swamp everything else so
that the planner
doesn't know that eg "15" is really rare. " I thought that if a value is not
found in the histogram, than clearly that value is rare, correct? What am I
missing here?
I hear what you are saying about "don't keep both extremely common and
extremely rare entries in the same array", but I cannot predict the future,
so I do not know which values are going to be common next year, or two years
later. So I think it would be very difficult to follow this advice.
What do you think?
--
View this message in context: http://postgresql.nabble.com/Why-is-GIN-index-slowing-down-my-query-tp5836319p5836323.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | AlexK987 | 2015-02-02 03:00:05 | Re: Why is GIN index slowing down my query? |
Previous Message | Tom Lane | 2015-02-01 23:34:13 | Re: Why is GIN index slowing down my query? |