Re: Have I b0rked something? Slow comparisons on "where x in (...)"
От
Stephen Harris
Тема
Re: Have I b0rked something? Slow comparisons on "where x in (...)"
Дата
Msg-id
20070503135712.GA31220@pugwash.spuddy.org
Ответ на
Список
Дерево обсуждения
Have I b0rked something? Slow comparisons on "where x in (...)" Stephen Harris <lists@spuddy.org>
Re: Have I b0rked something? Slow comparisons on "where x in (...)" Tom Lane <tgl@sss.pgh.pa.us>
Re: Have I b0rked something? Slow comparisons on "where x in (...)" Stephen Harris <lists@spuddy.org>
Re: Have I b0rked something? Slow comparisons on "where x in (...)" Listmail <lists@peufeu.com>
Re: Have I b0rked something? Slow comparisons on "where
x in (...)" Alban Hertroys <alban@magproductions.nl>
Re: Have I b0rked something? Slow comparisons on "where x in (...)" Listmail <lists@peufeu.com>
Re: Have I b0rked something? Slow comparisons on "where x in (...)" "Dann Corbit" <DCorbit@connx.com>
Re: Have I b0rked something? Slow comparisons on "where x in (...)" Stephen Harris <lists@spuddy.org>
Re: Have I b0rked something? Slow comparisons on "where
x in (...)" Richard Huxton <dev@archonet.com>
Re: Have I b0rked something? Slow comparisons on "where x in (...)" Listmail <lists@peufeu.com>
On Wed, May 02, 2007 at 05:59:49PM -0400, Tom Lane wrote:
> Stephen Harris writes:
> > "select stuff from table where index_key in (" .
> > join(",",keys %hash) . ") AND non_index_row in ('xyz','abc','def')
> In what, a seq scan?
Yeah, if the number of comparisons exceeds 156 then it switched from
index scan to sequential scan.
> time, I can see where the time might get eaten up. Where is the
> index_key column in the tuples, exactly?
First column.
--
rgds
Stephen
В списке pgsql-general по дате отправления
