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

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: ryan groth <postgres(at)cpusoftware(dot)com>, Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, "Steinar H(dot) Gunderson" <sgunderson(at)bigfoot(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Joins and full index scans...mysql vs postgres?
Date: 2006-02-23 10:21:26
Message-ID: 43FD8CA6.10802@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Kjeld Peters 2006-02-23 12:35:51 Created Index is not used
Previous Message Greg Stark 2006-02-23 03:52:48 Re: Good News re count(*) in 8.1