Hi everybody,
thanks for the so many responses. :)
> On Thu, Apr 19, 2012 at 3:44 AM, Josh Berkus
>>> 7500ms
>>> http://explain.depesz.com/s/
>> This plan seems very odd -- doing individual index lookups on 2.8m rows
>> is not standard planner behavior. Can you confirm that all of your
>> othe
Hi,
thanks for the suggestion, but it didn't help. We have tried it earlier.
7500ms
http://explain.depesz.com/s/ctn
ALTER TABLE product_parent ALTER COLUMN parent_name SET STATISTICS 1000;
ALTER TABLE product ALTER COLUMN parent_id SET STATISTICS 1000;
ANALYZE product_parent;
ANALYZE product;
q
ple_cost = '0.01';
12ms
http://explain.depesz.com/s/Ypc
this was the query:
select distinct product_code from product p_
inner join product_parent par_ on p_.parent_id=par_.id
where par_.parent_name like 'aa%' limit 2
Any idea?
Thanks in advance,
Istvan
2012
Hi,
i've ran into a planning problem.
Dedicated PostgreSQL Server:
"PostgreSQL 9.1.3 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2
20080704 (Red Hat 4.1.2-46), 64-bit"
Memory: 8GB
4CPUs
The problem is reduced to the following: there are 2 tables:
-product (3millions rows, 1GB)
-produc
