From: | Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Sam Jas <samjas33(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Table Partitioning Advice Request |
Date: | 2009-12-17 15:00:47 |
Message-ID: | 3eff28920912170700i7e99f149iab37c5fe7a741aaf@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2009/12/17 David Fetter <david(at)fetter(dot)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! :-)
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Bailey | 2009-12-17 15:15:58 | Re: Automatic truncation of character values & casting to the type of a column type |
Previous Message | David Fetter | 2009-12-17 14:55:45 | Re: Table Partitioning Advice Request |