Re: Help w/speeding up range queries?

Поиск
Список
Период
Сортировка
Искать
От
Luke Lonergan
Тема
Re: Help w/speeding up range queries?
Дата
Msg-id
C16D224A.592F%llonergan@greenplum.com
Ответ на
Список
Дерево обсуждения
Help w/speeding up range queries? John Major <major@cbio.mskcc.org>
Re: Help w/speeding up range queries? "Simon Riggs" <simon@2ndquadrant.com>
Re: Help w/speeding up range queries? Tom Lane <tgl@sss.pgh.pa.us>
Re: Help w/speeding up range queries? Jim Nasby <jim@nasby.net>
Re: Help w/speeding up range queries? "Luke Lonergan" <llonergan@greenplum.com>
Re: Help w/speeding up range queries? Tom Lane <tgl@sss.pgh.pa.us>
Re: Help w/speeding up range queries? Weslee Bilodeau <weslee.bilodeau@hypermediasystems.com>
Re: Help w/speeding up range queries? "Luke Lonergan" <llonergan@greenplum.com>
Re: Help w/speeding up range queries? "Luke Lonergan" <llonergan@greenplum.com>
John,

On 10/31/06 3:18 PM, "John Major"  wrote:

> Any advice on how I might be able to improve this situation would be
> very helpful.

I think table partitioning is exactly what you need.

There's a basic capability in current Postgres to divide tables into parent
+ children, each of which have a constraint for the rows inside (in your
case chromosome).  When you query the parent, the planner will exclude child
tables outside of the predicate range.

- Luke


В списке pgsql-performance по дате отправления
От: John Major
Дата:
От: Weslee Bilodeau
Дата:
FAQ