Thread: Re: Table access method not behaving like Oracle (index vs sequential

Re: Table access method not behaving like Oracle (index vs sequential

From
Daniel Schuchardt
Date:
Kevin Macdonald wrote:

>
> QUERY 2: select sobjid from p1_nrn_road where v = 1
>
> The plan is "Seq Scan on p1_nrn_road (cost=0.00..22158.54 rows=2 width=8)"
>
> The plan is wrong: "select min(v) from p1_nrn_road" returns
> 2226497481090365991, which indicates that the query will return 0 rows.
>


Hy Kevin,

please try

select sobjid from p1_nrn_road where v = '1'

(notice quotes)

I'm not sure but i think indexes that consists of more than 2 rows have
to be casted to char in PG.

Daniel.