From: | Patrick Vachon <pvachon(dot)videotron(at)videotron(dot)ca> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Difference between 8.1 & 8.3 |
Date: | 2008-07-16 21:37:58 |
Message-ID: | 487E6A36.3010100@videotron.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi guys,
I've got a query that is running slower on 8.3 than on 8.1 (with
equivalent server config),
because the join ordering is not the same, at least that's my guess... ;-)
In 8.1.4, table A had 122880 pages, B 112690 pages and C 80600 pages.
Now in 8.3.3, table A has only 77560 pages, B 69580 but C remains at
80600 pages.
In 8.1 the tables were joined in that way (using explain analyse):
C join A join B
now in 8.3:
B join A join C
Beside that, the plan is very similar, but the indexes used are not the
same.
Could the number of disk pages of a table influence the
order in which it is joined, even when it is scanned with an index?
I'm pretty sure it is because of the reduced table sizes,
since the server configuration is the same.
Thoughts?
Thanks,
Patrick
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Williamson | 2008-07-16 21:59:42 | Re: Difference between 8.1 & 8.3 |
Previous Message | Stephen Conley | 2008-07-15 21:26:52 | Re: requested shared memory size overflows size_t |