Re: [PERFORM] Seq scan on big table, episode 2

2012-10-31 Thread Shaun Thomas
On 10/31/2012 05:55 AM, Vincenzo Melandri wrote: on People: CREATE UNIQUE INDEX people_pkey ON people USING btree (key1, key2) CREATE INDEX people_pkey_hash_loc ON people USING hash (key1); CREATE INDEX people_pkey_hash_id ON people USING hash (key2); I can't say why it would ignore the first

Re: [PERFORM] Seq scan on big table, episode 2

2012-10-31 Thread Vincenzo Melandri
I may (or may not) have found the solution: a reindex on the 3 tables fixed the query plan. Now I can plan to reindex only the involved indexes at the start of the data import procedure. On Wed, Oct 31, 2012 at 11:55 AM, Vincenzo Melandri wrote: > Hi all :) > > I'm here again. > This time I'll pr

[PERFORM] Seq scan on big table, episode 2

2012-10-31 Thread Vincenzo Melandri
Hi all :) I'm here again. This time I'll provide more details (explain analyze, data-type, and indexes), hope it will be enough :) The query that is performing a plan that i do not understand is the following: select [some fields from all 3 tables] from DATA_SEQUENCES join SU