Re: [PERFORM] planer chooses very bad plan

2010-04-11 Thread Corin
. I'll also increase the default_statistics to 1000, because this also seems to help a lot. Thanks, Corin -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance

Re: [PERFORM] planer chooses very bad plan

2010-04-11 Thread Corin
y tables with similar data. As the size of the table index seems not change at all, I wonder how much additional storage is needed? I only care about runtime performance: are inserts/updates affected by this change? Or is only analyze affected (only run once during the night)? Thanks, Corin

[PERFORM] planer chooses very bad plan

2010-04-11 Thread Corin
xed/analyzed. Are there any parameters I can tune so that pgsql itself chooses the best plan? :) # - Memory - shared_buffers = 256MB temp_buffers = 32MB work_mem = 4MB maintenance_work_mem = 32MB # - Planner Cost Constants - seq_page_cost = 1.0 random_page_cost = 2.5 cpu_tuple_cost = 0.001 cp

[PERFORM] too complex query plan for not exists query and multicolumn indexes

2010-03-19 Thread Corin
ps=1832284)" " Index Cond: ($0 = ref_id)" "-> Bitmap Index Scan on user1 (cost=0.00..1.09 rows=87 width=0) (actual time=0.011..0.011 rows=87 loops=1737236)" " Index

[PERFORM] mysql to postgresql, performance questions

2010-03-18 Thread Corin
UERY PLAN"=>" -> Bitmap Index Scan on birthday_age (cost=0.00..82.37 rows=2611 width=0) (actual time=0.370..0.370 rows=2628 loops=1)"} {"QUERY PLAN"=>" Index Cond: ((birthday_age >= 20) AND (birthday_age <= 22))"} {"QUERY PLAN"=>"Total runtime: