pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Paul Thomas <paul@tmsl.demon.co.uk>
To: Fabian Kreitner <fabian.kreitner@ainea-ag.de>
Cc: pgsql-performance @ postgresql . org <pgsql-performance@postgresql.org>
Subject: Re: index / sequential scan problem
Date: Thu, 17 Jul 2003 15:38:25 +0100
Message-ID: <20030717153825.C27991@bacon> (raw)
In-Reply-To: <5.1.0.14.0.20030717144625.039c4a10@195.145.148.245>
References: <5.1.0.14.0.20030717131157.03957fa0@195.145.148.245>
	<5.1.0.14.0.20030717105203.03d2b5c0@195.145.148.245>
	<5.1.0.14.0.20030717105203.03d2b5c0@195.145.148.245>
	<20030717111248.C27264@bacon>
	<5.1.0.14.0.20030717131157.03957fa0@195.145.148.245>
	<20030717133445.A27991@bacon>
	<5.1.0.14.0.20030717144625.039c4a10@195.145.148.245>


On 17/07/2003 13:50 Fabian Kreitner wrote:
> [snip]
> Im afraid, no.
> Database has been stopped / started right before this.
> [snip]

1) enable_seqscan = true
> Seq Scan on notiz_objekt a  (cost=0.00..56125.80 rows=15561 width=12) 
> (actual time=0.28..2298.71 rows=31122 loops=1)
> [snip]

2) enable_seqscan = false
> Seq Scan on notiz_objekt a  (cost=100000000.00..100111719.36 rows=15561 
> width=12) (actual time=0.25..535.75 rows=31122 loops=1)

I've just noticed this. Something is not right here. Look at the crazy 
cost estimation for the second query. It looks to me like 
enable_indexscan, enable_tidscan, enable_sort, enable_nestloop, 
enable_mergejoin or enable_hashjoin have been set to false. Looking at the 
source, thats the only way I can see that such large numbers can be 
produced.

HTH

-- 
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for the Smaller 
Business |
| Computer Consultants         | 
http://www.thomas-micro-systems-ltd.co.uk   |
+------------------------------+---------------------------------------------+



view thread (19+ messages)  latest in thread

Message-ID: <20030717153825.C27991@bacon>
Permalink:  ../20030717153825.C27991@bacon/
Also on:    postgresql.org/message-id/20030717153825.C27991@bacon

 · 

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: paul@tmsl.demon.co.uk, fabian.kreitner@ainea-ag.de
  Subject: Re: index / sequential scan problem
  In-Reply-To: <20030717153825.C27991@bacon>
  References: <5.1.0.14.0.20030717131157.03957fa0@195.145.148.245> <5.1.0.14.0.20030717105203.03d2b5c0@195.145.148.245> <20030717111248.C27264@bacon> <20030717133445.A27991@bacon> <5.1.0.14.0.20030717144625.039c4a10@195.145.148.245> <20030717153825.C27991@bacon>

* 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