From: | Moritz Onken <onken(at)houseofdesign(dot)de> |
---|---|
To: | |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Slow query with a lot of data |
Date: | 2008-08-21 15:07:54 |
Message-ID: | 74E8B5A3-F0E7-4B66-947B-AE7715A55B90@houseofdesign.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Am 21.08.2008 um 16:39 schrieb Scott Carey:
> It looks to me like the work_mem did have an effect.
>
> Your earlier queries had a sort followed by group aggregate at the
> top, and now its a hash-aggregate. So the query plan DID change.
> That is likely where the first 10x performance gain came from.
But it didn't change as I added the sub select.
Thank you guys very much. The speed is now ok and I hope I can finish
tihs work soon.
But there is another problem. If I run this query without the
limitation of the user id, postgres consumes about 150GB of disk space
and dies with
ERROR: could not write block 25305351 of temporary file: No space
left on device
After that the avaiable disk space is back to normal.
Is this normal? The resulting table (setup1) is not bigger than 1.5 GB.
moritz
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2008-08-21 17:08:14 | Re: Slow query with a lot of data |
Previous Message | Christiaan Willemsen | 2008-08-21 15:06:13 | Re: How to setup disk spindles for best performance |