pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Madison Kelly <linux@alteeve.com>
Cc: pgsql-performance@postgresql.org, Bruno Wolff III <bruno@wolff.to>
Subject: Re: Index ot being used
Date: Mon, 13 Jun 2005 14:13:23 -0400
Message-ID: <22127.1118686403@sss.pgh.pa.us> (raw)
In-Reply-To: <42ADC77B.7000007@alteeve.com>
References: <1825.216.209.137.1.1118419819.squirrel@mail.alteeve.com>
	<20050610155535.GO8451@tobias.nordicbet.com>
	<42AC42CB.8050703@alteeve.com>
	<24636.1118591783@sss.pgh.pa.us>
	<42ACBC95.9020404@alteeve.com>
	<20050613030001.GB17491@wolff.to>
	<20050613031317.GA18988@wolff.to>
	<42AD008D.4080600@alteeve.com>
	<20050613035346.GA20703@wolff.to>
	<42AD0B94.9090508@alteeve.com>
	<20050613132852.GA31142@wolff.to>
	<42ADC77B.7000007@alteeve.com>

Madison Kelly <linux@alteeve.com> writes:
> Bruno Wolff III wrote:
>> Please actually try this before changing anything else.

>    If I follow then I tried it but still got the sequential scan.

Given the fairly large number of rows being selected, it seems likely
that the planner thinks this is faster than an indexscan.  It could
be right, too.  Have you tried "set enable_seqscan = off" to see if
the index is used then?  If so, is it faster or slower?  Comparing
EXPLAIN ANALYZE results with enable_seqscan on and off would be useful.

			regards, tom lane



view thread (31+ messages)  latest in thread

Message-ID: <22127.1118686403@sss.pgh.pa.us>
Permalink:  ../22127.1118686403@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/22127.1118686403@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, linux@alteeve.com, bruno@wolff.to
  Subject: Re: Index ot being used
  In-Reply-To: <22127.1118686403@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