From: Kevin Brown <kevin@sysexperts.com>
To: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon
Date: Fri, 22 Apr 2005 23:30:45 -0700
Message-ID: <20050423063044.GI19518@filer> (raw)
In-Reply-To: <20050423020151.GW58835@decibel.org>
References: <4266F7B3.7050004@arbash-meinel.com>
<000f01c54679$8d2f1f70$797ba8c0@jfradkin>
<20050423020151.GW58835@decibel.org>
Jim C. Nasby wrote:
> Hrm... I was about to suggest that for timing just the query (and not
> output/data transfer time) using explain analyze, but then I remembered
> that explain analyze can incur some non-trivial overhead with the timing
> calls. Is there a way to run the query but have psql ignore the output?
> If so, you could use \timing.
Would timing "SELECT COUNT(*) FROM (query)" work?
--
Kevin Brown kevin@sysexperts.com
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: kevin@sysexperts.com
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon
In-Reply-To: <20050423063044.GI19518@filer>
* 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