pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Lubratt <mark.lubratt@indeq.com>
Cc: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com
Subject: Re: tsearch query plan
Date: Fri, 09 Apr 2004 01:26:51 -0400
Message-ID: <21349.1081488411@sss.pgh.pa.us> (raw)
In-Reply-To: <FD09DC53-89D5-11D8-80A0-000A9579AF50@indeq.com>
References: <D8C70D62-8982-11D8-90A0-000A9579AF50@indeq.com>
	<200404081633.40388.josh@agliodbs.com>
	<FD09DC53-89D5-11D8-80A0-000A9579AF50@indeq.com>

Mark Lubratt <mark.lubratt@indeq.com> writes:
> I guess I was looking more at the cost estimate and not so much at the 
> rows estimate.  I agree that the row estimate wasn't too bad.  But the 
> cost estimate seems way out of line.

The cost estimates are not even in the same units as the actual runtime.
Cost is in an arbitrary scale in which 1 unit = 1 sequential disk block
fetch.  It is unknown what this might equate to on your machine ... but
it's quite unlikely that it's 1.0 millisecond.  The thing to look at
when considering EXPLAIN results is whether the ratios of different cost
estimates are proportional to the actual runtimes.

			regards, tom lane



view thread (4+ messages)

Message-ID: <21349.1081488411@sss.pgh.pa.us>
Permalink:  ../21349.1081488411@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/21349.1081488411@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, mark.lubratt@indeq.com, josh@agliodbs.com
  Subject: Re: tsearch query plan
  In-Reply-To: <21349.1081488411@sss.pgh.pa.us>

* 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