pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Fuhr <mike@fuhr.org>
To: Adam Palmblad <adam@aers.ca>
Cc: Postgres Performance <pgsql-performance@postgresql.org>
Subject: Re: Bad Index Choices with user defined data type
Date: Mon, 3 Jan 2005 22:06:21 -0700
Message-ID: <20050104050621.GA81266@winnie.fuhr.org> (raw)
In-Reply-To: <001d01c4f1dd$7eb98390$97019696@AERS04>
References: <001d01c4f1dd$7eb98390$97019696@AERS04>

On Mon, Jan 03, 2005 at 01:44:27PM -0800, Adam Palmblad wrote:

> I've got a table using a data type that I have created as the type for
> its primary key.  I (hope) I have the type set up properly - it seems
> okay, and does not have any problem creating a b-tree index for the
> type.  The problem I am having is that the index seems to never be
> chosen for use.  I can force the use of the index by setting
> enable_seqscan to off.  The table has about 1.2 million rows.  I have
> also analyzed the table - and immediately afterwards there is no affect
> on the index's behaviour.

Please post the query and the EXPLAIN ANALYZE output for both cases:
one query with enable_seqscan on and one with it off.  It might
also be useful to see the column's statistics from pg_stats, and
perhaps the SQL statements that create the table, the type, the
type's operators, etc.

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/



view thread (2+ messages)

Message-ID: <20050104050621.GA81266@winnie.fuhr.org>
Permalink:  ../20050104050621.GA81266@winnie.fuhr.org/
Also on:    postgresql.org/message-id/20050104050621.GA81266@winnie.fuhr.org

 · 

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: mike@fuhr.org, adam@aers.ca
  Subject: Re: Bad Index Choices with user defined data type
  In-Reply-To: <20050104050621.GA81266@winnie.fuhr.org>

* 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