Re: Table Partitioning Advice Request

From: David Fetter <david(at)fetter(dot)org>
To: Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it>
Cc: Sam Jas <samjas33(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Table Partitioning Advice Request
Date: 2009-12-17 14:55:45
Message-ID: 20091217145545.GC3000@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Dec 17, 2009 at 02:41:40PM +0100, Vincenzo Romano wrote:
> > 2009/12/17 Sam Jas <samjas33(at)yahoo(dot)com>
> > Rule is not advisable, Trigger is the best solution.

> If you have to choose among a couple hundred partition tables, the
> trigger function body is far from trivial!

It's possible to generate such code and deploy it automatically.

> 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.

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

Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vincenzo Romano 2009-12-17 15:00:47 Re: Table Partitioning Advice Request
Previous Message Merlin Moncure 2009-12-17 14:43:49 Re: Justifying a PG over MySQL approach to a project