Partitioning by status?

Поиск
Список
Период
Сортировка
От Mike Blackwell
Тема Partitioning by status?
Дата
Msg-id CANPAkgt9mGoF7SyA_n7jX3t6siLGPyA=d1tR2bPwKiAex3bDMQ@mail.gmail.com
обсуждение исходный текст
Ответы Re: Partitioning by status?
Re: Partitioning by status?
Список pgsql-performance
Дерево обсуждения
We have a set of large tables.  One of the columns is a status indicator (active / archived).  The queries against these tables almost always include the status, so partitioning against that seems to makes sense from a logical standpoint, especially given most of the data is "archived" and most of the processes want active records.

Is it practical to partition on the status column and, eg, use triggers to move a row between the two partitions when status is updated?  Any surprises to watch for, given the status column is actually NULL for active data and contains a value when archived?

Mike

В списке pgsql-performance по дате отправления:

Предыдущее
От: darklow
Дата:
Сообщение: Query planner doesn't use index scan on tsvector GIN index if LIMIT is specified
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Query planner doesn't use index scan on tsvector GIN index if LIMIT is specifiedQuery planner doesn't use index scan on tsvector GIN index if LIMIT is specified