Dave Page wrote:
>>[mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of
>>Sent: 21 April 2005 14:06
>>To: Joel Fradkin
>>Cc: 'John A Meinel'; josh(at)agliodbs(dot)com;
>>Subject: Re: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon
>> 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.
In response to
pgsql-performance by date
|Next:||From: Dawid Kuroczko||Date: 2005-04-22 10:08:50|
|Subject: Re: immutable functions vs. join for lookups ?|
|Previous:||From: Richard van den Berg||Date: 2005-04-22 09:04:17|
|Subject: Re: When are index scans used over seq scans?|