From: | Matteo Beccati <php(at)beccati(dot)com> |
---|---|
To: | Yann Michel <yann-postgresql(at)spline(dot)de> |
Cc: | Matt Casters <Matt(dot)Casters(at)advalvas(dot)be>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: |
Date: | 2005-01-21 14:37:20 |
Message-ID: | 41F113A0.1020908@beccati.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
>>>> CREATE TABLE super_foo ( partition NUMERIC, bar NUMERIC );
>>>> ANALYZE super_foo ;
>>>>
>>>> CREATE TABLE sub_foo1 () INHERITS ( super_foo );
>>>> CREATE TABLE sub_foo2 () INHERITS ( super_foo );
>
> Yes, this could be used instead of a view. But there is one thing
> missing. You can't just insert into super_foo and aquire the "correct
> partition". You will still have to insert into the correct underlying
> table. "Real" partitioning will take care of correct partition
> selection.
I've recently used this method for partitioning data. In my setup
inserts are done inside a pl/pgsql function called at regular intervals,
so this isn't a problem for me. I didn't test it, but I think some rules
(or a trigger) could do the trick.
Best regards
--
Matteo Beccati
http://phpadsnew.com
http://phppgads.com
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2005-01-21 15:40:57 | Re: PostgreSQL clustering VS MySQL clustering |
Previous Message | Merlin Moncure | 2005-01-21 13:33:24 | Re: [SQL] OFFSET impact on Performance??? |