| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jo <jl(dot)news(at)uni-bonn(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres 8.3 vs. 8.4 - Query plans and performance |
| Date: | 2011-03-14 15:09:39 |
| Message-ID: | 8922.1300115379@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>> we have performance problems running several queries pon postgres 8.4 .
>> Using the previous version (8.3) our queries performs well
>> (The queries are quite complex, consisting of several sub-queries and
>> various spatial functions).
Two things that frequently bite people during an upgrade:
1. Forgetting to ANALYZE the database after reload. Autovacuum would
probably fix that for you eventually, but it's better to just issue one
manually.
2. Creating the new database with the wrong locale. I see a bunch of
LIKE operators in the query plans you show later, so I'm wondering if
you went from C locale to a non-C locale and that defeated LIKE
optimizations that used to work.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yngve N. Pettersen (Developer Opera Software ASA) | 2011-03-14 15:13:59 | Re: Select for update with offset interferes with concurrent transactions |
| Previous Message | tv | 2011-03-14 15:04:42 | Re: Postgres 8.3 vs. 8.4 - Query plans and performance |