Re: Joins and full index scans...mysql vs postgres? - Mailing list pgsql-performance

From Andreas Pflug
Subject Re: Joins and full index scans...mysql vs postgres?
Date
Msg-id 43FD8CA6.10802@pse-consulting.de
Whole thread Raw
In response to Re: Joins and full index scans...mysql vs postgres?  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List 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

pgsql-performance by date:

Previous
From: Greg Stark
Date:
Subject: Re: Good News re count(*) in 8.1
Next
From: Kjeld Peters
Date:
Subject: Created Index is not used