Re: Problem with nested query

From: Denis Perchine <dyp(at)perchine(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem with nested query
Date: 2000-10-03 10:19:09
Message-ID: 0010031719090E.00490@dyp.perchine.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Denis Perchine <dyp(at)perchine(dot)com> writes:
> > As far as you can see it uses sequence scan for inner select. This is
> > quite strange as if I do this select with a constant it will use index
> > scan:
>
> Are the two tables' "email" fields declared as exactly the same
> datatype?

No...

> IIRC, 7.0.* has a problem with recognizing that a type-coerced parameter
> to an inner query is useful as an indexscan reference constant. This is
> fixed in current sources, but in the meantime avoiding an implicit type
> coercion is the easiest workaround.

OK. Thanks.

--
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp(at)perchine(dot)com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Mount 2000-10-03 10:57:37 Re: Re: JDBC Performance
Previous Message Michael Ansley 2000-10-03 10:15:15 OIDs