From: Andreas Pflug <pgadmin@pse-consulting.de>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: ryan groth <postgres@cpusoftware.com>
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Steinar H. Gunderson <sgunderson@bigfoot.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Joins and full index scans...mysql vs postgres?
Date: Thu, 23 Feb 2006 10:21:26 +0000
Message-ID: <43FD8CA6.10802@pse-consulting.de> (raw)
In-Reply-To: <43FD235B.7000207@familyhealth.com.au>
References: <E1FBz6X-0007Do-9z@zeus.liquidweb.com>
<43FD235B.7000207@familyhealth.com.au>
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
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, chriskl@familyhealth.com.au, postgres@cpusoftware.com, sszabo@megazone.bigpanda.com, sgunderson@bigfoot.com
Subject: Re: Joins and full index scans...mysql vs postgres?
In-Reply-To: <43FD8CA6.10802@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