From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Joel's Performance Issues WAS : Opteron vs Xeon |
Date: | 2005-04-22 09:47:31 |
Message-ID: | 4268C833.8080302@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Dave Page wrote:
>
>
>
>>-----Original Message-----
>>From: pgsql-performance-owner(at)postgresql(dot)org
>>[mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of
>>Andreas Pflug
>>Sent: 21 April 2005 14:06
>>To: Joel Fradkin
>>Cc: 'John A Meinel'; josh(at)agliodbs(dot)com;
>>pgsql-performance(at)postgresql(dot)org
>>Subject: Re: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon
>>
>>Beware!
>> From the data, I can see that you're probably using pgAdmin3.
>>The time to execute your query including transfer of all data to the
>>client is 17s in this example, while displaying it (i.e. pure GUI and
>>memory alloc stuff) takes 72s. Execute to a file to avoid this.
>
>
> Perhaps we should add a guruhint there for longer runtimes?
Yup, easily done as replacement for the "max rows exceeded" message box.
Added to TODO.txt.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Dawid Kuroczko | 2005-04-22 10:08:50 | Re: immutable functions vs. join for lookups ? |
Previous Message | Richard van den Berg | 2005-04-22 09:04:17 | Re: When are index scans used over seq scans? |