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-29 19:36:29
Message-ID: 396486430906291236k76794fd3j407ef99c71ec918a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Mon, Jun 29, 2009 at 12:19 PM, Bhella
Paramjeet-PFCW67<PBhella(at)motorola(dot)com> wrote:

> I tested a scenario where in one terminal window
> I insert rows in the eventlog table in the BEGIN END loop and do not
> commit the transaction. In another terminal window I create a new
> partition but when I create a rule for the new partition it hangs until
> I commit the
> transaction(insert) in the first terminal window.  Just want to know if
> this is a limitation in postgres partitioning ?

Actually I would say that transactional ddl is a feature of PostgreSQL
rather than a limitation. But is sounds like this feature isn't
playing well with your current design.

> Is there a work around
> for this problem? In our production environment we want to  be able to
> create new partitions and rule for new partition while data is being
> inserted into the eventlog table.

You probably need break up your insert transactions into smaller
segments that coincide DDL changes.

--
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 Kevin Kempter 2009-06-29 23:50:00 how much memory (work_mem) is a query using?
Previous Message Bhella Paramjeet-PFCW67 2009-06-29 19:19:17 Partioning in postgres