From: Dan Harris <fbsd@drivefaster.net>
To: pgsql-performance@postgresql.org
Subject: Re: Quad Opteron stuck in the mud
Date: Wed, 13 Jul 2005 14:20:24 -0600
Message-ID: <7C8917ED-62B8-4D76-AC02-90CF04002C97@drivefaster.net> (raw)
In-Reply-To: <20050713201715.GI24207@ns.snowman.net>
References: <E5E21B7B-FFE0-4D24-8CDD-62179AEBBB92@drivefaster.net>
<42D56772.6020408@arbash-meinel.com>
<862C6AD9-646B-4907-AB18-09F1AD08B5F5@drivefaster.net>
<20050713201715.GI24207@ns.snowman.net>
On Jul 13, 2005, at 2:17 PM, Stephen Frost wrote:
>
> Could you come up w/ a test case that others could reproduce where
> explain isn't returning?
This was simply due to my n00bness :) I had always been doing
explain analyze, instead of just explain. Next time one of these
queries comes up, I will be sure to do the explain without analyze.
FYI that update query I mentioned in the initial thread just finished
after updating 8.3 million rows.
-Dan
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: fbsd@drivefaster.net
Subject: Re: Quad Opteron stuck in the mud
In-Reply-To: <7C8917ED-62B8-4D76-AC02-90CF04002C97@drivefaster.net>
* 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