[PERFORM] Seqscan

2007-10-22 Thread Adrian Demaestri
Hi, I think planner should use other plans than seqscan to solve querys like select * from hugetable limit 1, especially when the talbe is very large. Is it solved in newer versions or is there some open issues about it?. thanks I'm working with postgres 8.0.1,

Re: [PERFORM] Seqscan

2007-10-23 Thread Adrian Demaestri
b.f1 AND a.f2 = b.f2 LEFT JOIN c ON a.f3 = c.f3 Each one of the tables a, b and c has about 5 million rows. The relation between the tables using that joins conditions is at most 1 to 1 thanks! Jeff Davis <[EMAIL PROTECTED]> escribió: On Mon, 2007-10-22 at 19:24 -0700, Adrian Demaest

[PERFORM] planner doesn't use multicolumn index

2003-10-08 Thread Adrian Demaestri
We've a table with about 8 million rows, and we need to get rows by the value of two of its fields( the type of the fields are int2 and int4, the where condition is v.g. partido=99 and partida=123). We created a multicolumn index on that fields but the planner doesn't use it, it still use a seqscan