Re: sub-select in IN clause results in sequential scan
От
Grzegorz Jaśkiewicz
Тема
Re: sub-select in IN clause results in sequential scan
Дата
Msg-id
2f4958ff0910290254j567c46ffkcdf3f83b78a521f6@mail.gmail.com
Ответ на
Список
Дерево обсуждения
sub-select in IN clause results in sequential scan Anj Adu <fotographs@gmail.com>
Re: sub-select in IN clause results in sequential scan Grzegorz Jaśkiewicz <gryzman@gmail.com>
Re: sub-select in IN clause results in sequential scan Angayarkanni <kangayarkanni@gmail.com>
Re: sub-select in IN clause results in sequential scan Anj Adu <fotographs@gmail.com>
Re: sub-select in IN clause results in sequential scan Robert Haas <robertmhaas@gmail.com>
Re: sub-select in IN clause results in sequential scan Anj Adu <fotographs@gmail.com>
Re: sub-select in IN clause results in sequential scan Grzegorz Jaśkiewicz <gryzman@gmail.com>
Re: sub-select in IN clause results in sequential scan Robert Haas <robertmhaas@gmail.com>
Re: sub-select in IN clause results in sequential scan Bob Lunney <bob_lunney@yahoo.com>
On Wed, Oct 28, 2009 at 6:13 PM, Anj Adu <fotographs@gmail.com> wrote:
Postgres consistently does a sequential scan on the child partitions
for this query
select * from partitioned_table
where partitioned_column > current_timestamp - interval 8 days
where x in (select yy from z where colname like 'aaa%')
If I replace the query with
select * from partitioned_table
where partitioned_column > current_timestamp - interval 8 days
where x in (hardcode_value)
The results are in line with expectation (very fast and uses a Bitmap
Index Scan on the column X)
\
use JOIN luke..
--
GJ
В списке pgsql-performance по дате отправления