From: Yann Michel <yann-postgresql@spline.de>
To: Matteo Beccati <php@beccati.com>
Cc: Matt Casters <Matt.Casters@advalvas.be>
Cc: pgsql-performance@postgresql.org
Subject: Re:
Date: Fri, 21 Jan 2005 17:05:39 +0100
Message-ID: <20050121160539.GA15734@zoom.spline.inf.fu-berlin.de> (raw)
In-Reply-To: <41F113A0.1020908@beccati.com>
References: <16153.193.190.212.113.1106213675.squirrel@193.190.212.113>
<20050120142603.GM10437@ns.snowman.net>
<33c6269f050120083177fa0e83@mail.gmail.com>
<20050121001427.GA10806@wolff.to>
<12670.193.190.212.113.1106297446.squirrel@193.190.212.113>
<20050121123008.GA13904@zoom.spline.inf.fu-berlin.de>
<41F113A0.1020908@beccati.com>
Hi,
On Fri, Jan 21, 2005 at 03:37:20PM +0100, Matteo Beccati wrote:
>
> >>>> 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.
Yes, a pl/pgsql function or any software solution can solve this
problem, but what you normally expect from a partitioning support is
that you don't have to care about where to put your data due to the db
will take care for that.
Of cause a trigger could do this as well, but don't forget, that a
trigger in dwh environments, where you process thousands of row at once
during data loading, is very expensive and therefore no solution for
production use.
Regards,
Yann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: yann-postgresql@spline.de, php@beccati.com, Matt.Casters@advalvas.be
Subject: Re:
In-Reply-To: <20050121160539.GA15734@zoom.spline.inf.fu-berlin.de>
References: <16153.193.190.212.113.1106213675.squirrel@193.190.212.113> <20050120142603.GM10437@ns.snowman.net> <33c6269f050120083177fa0e83@mail.gmail.com> <20050121001427.GA10806@wolff.to> <12670.193.190.212.113.1106297446.squirrel@193.190.212.113> <20050121123008.GA13904@zoom.spline.inf.fu-berlin.de> <41F113A0.1020908@beccati.com> <20050121160539.GA15734@zoom.spline.inf.fu-berlin.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox