Re: Query not using index for user defined type

From: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
To: Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Query not using index for user defined type
Date: 2013-04-15 20:27:07
Message-ID: CAJKUy5gdewPX2Fs+A=HOv_D39SuY1-kHnBV=O=zAdgqocNxXKQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 15, 2013 at 3:08 PM, Rodrigo Barboza
<rodrigombufrj(at)gmail(dot)com> wrote:
>
> Here is the explain analyze with 1000 entries:
>
> explain analyze select * from mytable where a > 120::mytype and a <
> 530::mytype;
>

I'm not sure this is appropiate for -hackers, maybe should post on -general.
Also provide scripts with the creation of the datatype and/or the
OPERATOR FAMILY

anyway, this explain is completely useless to prove your point. if you
are selecting almost half of the table it will use a seq scan. try
again with more rows in the table and a narrow filter

--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2013-04-15 20:32:29 Re: COPY and Volatile default expressions
Previous Message Tom Lane 2013-04-15 20:21:31 Re: COPY and Volatile default expressions