From: Andreas Pflug <pgadmin@pse-consulting.de>
To: Dave Page <dpage@vale-housing.co.uk>
Cc: pgsql-performance@postgresql.org
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon
Date: Fri, 22 Apr 2005 09:47:31 +0000
Message-ID: <4268C833.8080302@pse-consulting.de> (raw)
In-Reply-To: <E7F85A1B5FF8D44C8A1AF6885BC9A0E472C40A@ratbert.vale-housing.co.uk>
References: <E7F85A1B5FF8D44C8A1AF6885BC9A0E472C40A@ratbert.vale-housing.co.uk>
Dave Page wrote:
>
>
>
>>-----Original Message-----
>>From: pgsql-performance-owner@postgresql.org
>>[mailto:pgsql-performance-owner@postgresql.org] On Behalf Of
>>Andreas Pflug
>>Sent: 21 April 2005 14:06
>>To: Joel Fradkin
>>Cc: 'John A Meinel'; josh@agliodbs.com;
>>pgsql-performance@postgresql.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pgadmin@pse-consulting.de, dpage@vale-housing.co.uk
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon
In-Reply-To: <4268C833.8080302@pse-consulting.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox