pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jim@nasby.net>
To: pgsql-performance@postgresql.org
Subject: Re: Odd explain estimate
Date: Sat, 2 Aug 2003 10:59:54 -0500
Message-ID: <20030802155954.GK55392@nasby.net> (raw)
In-Reply-To: <20030801121612.GD18200@libertyrms.info>
References: <20030731195145.GD55392@nasby.net>
	<20030731205921.GF16230@libertyrms.info>
	<20030731225959.GH55392@nasby.net>
	<20030801121612.GD18200@libertyrms.info>

On Fri, Aug 01, 2003 at 08:16:12AM -0400, Andrew Sullivan wrote:
> On Thu, Jul 31, 2003 at 05:59:59PM -0500, Jim C. Nasby wrote:
> >  
> > Well, if I don't do this it wants to seqscan a table that occupies 350k
> > pages, instead of pulling a couple thousand rows. I started running it
> > with the seqscan and it's already taken way longer than it does if I
> > disable seqscan.
> 
> That was indeed the question. 
> 
> If it uses a seqscan when it ought not to do, then there's something
> wrong with the statistics, or you haven't vacuum analysed correctly,
> or your table needs vacuum full (is it really 350k pages, or is that
> mostly dead space?), &c. -- all the usual bad-seqscan candidates.
> 
> enable_seqscan=off is probably not a good strategy for any moderately
> complicated query.  If the planner were perfect, of course, you'd
> never need it at all.
 
Set statistics on the ID colum to 1000, vacuum analyze, and it's good to
go now. Thanks for your help!
-- 
Jim C. Nasby, Database Consultant                  jim@nasby.net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"



view thread (5+ messages)

Message-ID: <20030802155954.GK55392@nasby.net>
Permalink:  ../20030802155954.GK55392@nasby.net/
Also on:    postgresql.org/message-id/20030802155954.GK55392@nasby.net

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: jim@nasby.net
  Subject: Re: Odd explain estimate
  In-Reply-To: <20030802155954.GK55392@nasby.net>
  References: <20030731195145.GD55392@nasby.net> <20030731205921.GF16230@libertyrms.info> <20030731225959.GH55392@nasby.net> <20030801121612.GD18200@libertyrms.info> <20030802155954.GK55392@nasby.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