Re: Partioning in postgres - Mailing list pgsql-admin

From Richard Broersma
Subject Re: Partioning in postgres
Date
Msg-id 396486430906291236k76794fd3j407ef99c71ec918a@mail.gmail.com
Whole thread Raw
In response to Partioning in postgres  ("Bhella Paramjeet-PFCW67" <PBhella@Motorola.com>)
Responses Re: Partioning in postgres  ("Bhella Paramjeet-PFCW67" <PBhella@Motorola.com>)
List pgsql-admin
On Mon, Jun 29, 2009 at 12:19 PM, Bhella
Paramjeet-PFCW67<PBhella@motorola.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

pgsql-admin by date:

Previous
From: "Bhella Paramjeet-PFCW67"
Date:
Subject: Partioning in postgres
Next
From: Kevin Kempter
Date:
Subject: how much memory (work_mem) is a query using?