From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, "Joel Fradkin" <jfradkin(at)wazagua(dot)com> |
Cc: | "John A Meinel" <john(at)arbash-meinel(dot)com>, <josh(at)agliodbs(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Joel's Performance Issues WAS : Opteron vs Xeon |
Date: | 2005-04-22 08:08:01 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E472C40A@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> -----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?
Regards, dave
From | Date | Subject | |
---|---|---|---|
Next Message | David Roussel | 2005-04-22 08:44:05 | Re: Index bloat problem? |
Previous Message | Tom Lane | 2005-04-22 05:57:11 | Re: Index bloat problem? |