Re: Table Partitioning Advice Request

Поиск
Список
Период
Сортировка
От Vincenzo Romano
Тема Re: Table Partitioning Advice Request
Дата
Msg-id 3eff28920912170700i7e99f149iab37c5fe7a741aaf@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Table Partitioning Advice Request  (David Fetter <david@fetter.org>)
Ответы Re: Table Partitioning Advice Request  (Dimitri Fontaine <dfontaine@hi-media.com>)
Список pgsql-general
2009/12/17 David Fetter <david@fetter.org>:
>> You really think that calling and running a trigger function for every
>> line is the best solution?
>
> Yes.  The trigger function is choosing from a small subset of the
> tables, or you know which tables exactly the rows are going into and
> insert them there.

So I understand that when a table has multiple RULEs, the planner just
browse all of them
to check the one(s) that will apply.
What I have in mind is a "side table" with some bookkeeping data to be
used by the trigger
function to select the actual table to be used.
Do you think this is faster than RULEs?

Is there any performance study for the trigger-based implementation?

> Oh, and please do trim, and don't top-post.  I've fix this in this
> post.

Sorry! :-)

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

Предыдущее
От: David Fetter
Дата:
Сообщение: Re: Table Partitioning Advice Request
Следующее
От: Justin Bailey
Дата:
Сообщение: Re: Automatic truncation of character values & casting to the type of a column type