pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adam Palmblad <adam@aers.ca>
To: Postgres Performance <pgsql-performance@postgresql.org>
Subject: Bad Index Choices with user defined data type
Date: Mon, 3 Jan 2005 13:44:27 -0800
Message-ID: <001d01c4f1dd$7eb98390$97019696@AERS04> (raw)

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.

Any thoughts?

-Adam

view thread (2+ messages)  latest in thread

Message-ID: <001d01c4f1dd$7eb98390$97019696@AERS04>
Permalink:  ../001d01c4f1dd$7eb98390$97019696@AERS04/
Also on:    postgresql.org/message-id/001d01c4f1dd$7eb98390$97019696@AERS04

 · 

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: adam@aers.ca
  Subject: Re: Bad Index Choices with user defined data type
  In-Reply-To: <001d01c4f1dd$7eb98390$97019696@AERS04>

* 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