| From: | Aaron Guyon <battlemage(at)gmail(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Postgres 8.3, four times slower queries? |
| Date: | 2009-03-03 17:52:27 |
| Message-ID: | f0afbb9b0903030952k5bd08302o2cd71cd195f2ea79@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Mar 3, 2009 at 12:38 PM, <david(at)lang(dot)hm> wrote:
> if you haven't done a vaccum analyse on either installation then postgres'
> idea of what sort of data is in the database is unpredictable, and as a
> result it's not surprising that the two systems guess differently about what
> sort of plan is going to be most efficiant.
>
> try doing vaccum analyse on both databases and see what the results are.
>
> David Lang
>
These are the results with vacuum analyze:
8.2.12: 624.366 ms
8.3.3: 1273.601 ms
| Attachment | Content-Type | Size |
|---|---|---|
| analyze_8_2_12_va.txt | text/plain | 6.0 KB |
| analyze_8_3_3_va.txt | text/plain | 6.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sebastjan Trepca | 2009-03-03 19:05:53 | Re: Problems with ordering (can't force query planner to use an index) |
| Previous Message | Robert Haas | 2009-03-03 17:40:44 | Re: Problems with ordering (can't force query planner to use an index) |