| From: | Drew Wilson <drewmwilson(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Many to many join seems slow? |
| Date: | 2007-05-15 16:45:07 |
| Message-ID: | A1B60119-8777-4CAF-AF80-B776751B8670@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
You're right. If I redirect output to /dev/null, the query completes
in 1.4s.
# \o /dev/null
# SELECT s.source_id, s.value as sourceValue, t.value as
translationValue...
...
Time: 1409.557 ms
#
That'll do for now.
Thanks,
Drew
On May 15, 2007, at 7:17 AM, Heikki Linnakangas wrote:
> Drew Wilson wrote:
>> Merge Join (cost=524224.49..732216.29 rows=92447 width=97)
>> (actual time=1088.871..1351.840 rows=170759 loops=1)
>> ...
>> Total runtime: 1366.757 ms
>
> It looks like the query actual runs in less than 3 seconds, but it
> takes some time to fetch 170759 rows to the client.
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Stone | 2007-05-15 17:44:29 | Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal |
| Previous Message | Drew Wilson | 2007-05-15 16:43:55 | Re: Many to many join seems slow? |