Re: Dealing with big tables

Поиск
Список
Период
Сортировка
Искать
От
Matthew
Тема
Re: Dealing with big tables
Дата
Msg-id
Pine.LNX.4.58.0712031032220.3731@aragorn.flymine.org
Ответ на
Список
Дерево обсуждения
Dealing with big tables "Mindaugas" <ml@kilimas.com>
Re: Dealing with big tables Sami Dalouche <skoobi@free.fr>
Re: Dealing with big tables "Mindaugas" <ml@kilimas.com>
Re: Dealing with big tables "Guillaume Smet" <guillaume.smet@gmail.com>
Re: Dealing with big tables Mark Kirkwood <markir@paradise.net.nz>
Re: Dealing with big tables Matthew <matthew@flymine.org>
Re: Dealing with big tables Gregory Stark <stark@enterprisedb.com>
Re: Dealing with big tables "Mindaugas" <ml@kilimas.com>
Re: Dealing with big tables "Merlin Moncure" <mmoncure@gmail.com>
On Mon, 3 Dec 2007, Mark Kirkwood wrote:

> > And I cannot use some index organized table or table partitioned by
> > From :) because there are at least 2 similar indexes by which queries
> > can be executed - From and To.

> This makes things a bit tough. One trick is to vertically partition the
> table into two new tables - with "From" in one and "To" in the other...
> then you can (horizontally) partition or cluster on each of these
> columns separately.

Or you could even commit a capital sin and have several copies of the same
table, sorted by different columns. Just remember to select from the
correct table to get the performance, and to write all changes to all the
tables! Kind of messes up transactions and locking a little though.

Matthew

-- 
No, C++ isn't equal to D. 'C' is undeclared, so we assume it's an int,
with a default value of zero.  Hence, C++ should really be called 1.
-- met24, commenting on the quote "C++ -- shouldn't it be called D?"
В списке pgsql-performance по дате отправления
От: Tom Lane
Дата:
От: Paul Lindner
Дата:
Сообщение: Re: Training Recommendations
FAQ