[PERFORM] Problem with mergejoin performance (some bug?)

2010-09-16 Thread azajac
I have a problem with some simple query: select version(); PostgreSQL 8.3.8 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.3.2 20081105 (Red Hat 4.3.2-7) vacuum full bug_t1; vacuum full bug_t2; vacuum analyze bug_t1; vacuum analyze bug_t2; explain analyze SELECT ze.id ,rr.id FROM bug_t2 AS rr

Re: [PERFORM] Problem with mergejoin performance

2010-09-13 Thread Tom Lane
[ Please keep the list cc'd ] writes: >> What exactly are those join key values, and what are the min/max values >> in bug_t2? > min of Bug_t1.id = 42, > max of Bug_t1.id = 393065, > min of Bug_t2.id = 352448, > max of Bug_t2.id = 388715, > select count(id) from bug_t2 > 29 > select count

Re: [PERFORM] Problem with mergejoin performance

2010-09-13 Thread Tom Lane
writes: > Merge Join (cost=18.90..20.85 rows=1 width=8) (actual time=614.912..614.912 > rows=0 loops=1) >Merge Cond: (rr.id = ze.id) >-> Index Scan using bug_t2_i1 on bug_t2 rr (cost=0.00..17893.49 > rows=278417 width=4) (actual time=0.023..351.945 rows=278417 loops=1) >-> Sort (c

[PERFORM] Problem with mergejoin performance

2010-09-12 Thread azajac
I have a problem with some simple query: select version(); PostgreSQL 8.3.8 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.3.2 20081105 (Red Hat 4.3.2-7) vacuum full bug_t1; vacuum full bug_t2; vacuum analyze bug_t1; vacuum analyze bug_t2; show default_statistics_target; 1000 e