Re: Partioning in postgres

From: Richard Broersma <richard(dot)broersma(at)gmail(dot)com>
To: Bhella Paramjeet-PFCW67 <PBhella(at)motorola(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Partioning in postgres
Date: 2009-06-30 17:45:28
Message-ID: 396486430906301045s53548611p8cdd012b40e4cf32@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Jun 30, 2009 at 10:26 AM, Bhella
Paramjeet-PFCW67<PBhella(at)motorola(dot)com> wrote:

> We're trying to simulate rolling window concept in postgres with partitions, without impacting application which does concurrent inserts into partitioned tables. We basically need to roll off data from older partition say 7 days older just to avoid the overhead from delete/vacuum etc, and keep adding future day partitions. Seems like adding rules on the fly for future day partitions blocks rows from being inserted into current day partition.
>
> Anyone implemented similar concept in postgres.

I'm not an expert on this, but I will tell you what I know. From what
I understand, partitioned tables and associated triggers are created
for date ranges ahead of time (before the date when the partition data
come into existence). Table creation is handled through CRON jobs and
scripts.

The following archived thread illustrates what one person did to
develop automatic creation of table partitions:
http://archives.postgresql.org/pgsql-general/2009-04/msg01077.php

The above mentioned email may give you a workable solution.
--
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Kenneth Marshall 2009-06-30 17:48:57 Re: Partioning in postgres
Previous Message Bhella Paramjeet-PFCW67 2009-06-30 17:26:23 Re: Partioning in postgres