Re: [GENERAL] typecast for index - Mailing list pgsql-general

From Ed Loehr
Subject Re: [GENERAL] typecast for index
Date
Msg-id 38A7939E.2CB0762E@austin.rr.com
Whole thread Raw
In response to typecast for index  ("John Henderson" <jrh@is.com.fj>)
List pgsql-general
John Henderson wrote:
>
> This is what I want to do:
> select user_name, date_trunc('minutes',sum(is_roundup_01(sess_time)))
>                         from sessions_feb2000_homer s where
>                         date_part('epoch',start)>'949316399' and
>                         date_part('epoch',start)<'951822000' and
> prob here>    user_name IN (select username from userdir
>                         where towncode = 'LAB')
>                         group by user_name
>                         order by user_name;
>
> The problem is that user_name = 'soandso' will use an index scan
> but user_name IN (select ...) uses a sequential scan.
>
> Any advice on how to force this to use an index?
> Yes the index exists, yes it has been vaccuumed. This is PG 6.5.3

IIRC, this is a known issue with 'IN', and that the traditional
solution was to replace use of 'IN' with 'EXISTS', i.e.,

    and EXISTS (select * from userdir where user_name = username and
towncode...)

Cheers,
Ed Loehr

pgsql-general by date:

Previous
From: "John Henderson"
Date:
Subject: typecast for index
Next
From: Yury Don
Date:
Subject: ...