Horton
Menu

Re: Joins and full index scans...mysql vs postgres?

Andreas Pflug <pgadmin@pse-consulting.de>

View thread
From: Andreas Pflug <pgadmin@pse-consulting.de>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: ryan groth <postgres@cpusoftware.com>, Stephan Szabo <sszabo@megazone.bigpanda.com>, "Steinar H. Gunderson" <sgunderson@bigfoot.com>, pgsql-performance@postgresql.org
Date: 2006-02-23T10:21:26Z
Lists: pgsql-performance 
Christopher Kings-Lynne wrote:
> The pgAdmin query tool is known to give an answer about 5x the real 
> answer - don't believe it!

Everybody please forget immediately the factor 5. It's no factor at all, 
but the GUI update time that is *added*, which depends on rows*columns.


> ryan groth wrote:
> 
>> the pgadmin query tool saying that the query runs
>> "997+3522 ms".

Means 997ms until all data is at the client (libpq reports the rowset), 
the rest is GUI overhead.

Regards,
Andreas