From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Christian Rengstl" <Christian(dot)Rengstl(at)klinik(dot)uni-regensburg(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Performance problem with query |
Date: | 2006-07-14 13:59:19 |
Message-ID: | b42b73150607140659u3a163980keed67c91d7cdc9e3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7/14/06, Christian Rengstl
<Christian(dot)Rengstl(at)klinik(dot)uni-regensburg(dot)de> wrote:
> Hi,
>
> somehow my reply yesterday got lost, but nevertheless here comes the
> explain analyze again. It's the explain of the operation that causes
> this huge performance discrepancy. Unfortunately i had to perform the
> explain analyze with an empty temp_table, because after the whole
> operation is done, i delete the data again to save some space.
that's not much help. remember that explain analyze actually performs
your query. so next time you run it, do explain analyze and post
results here. just quick tip: run analyze before you run your big
query.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2006-07-14 14:18:57 | Re: Q: Table scans on set difference |
Previous Message | Christian Rengstl | 2006-07-14 13:22:43 | Antw: Problem with archive_command |