Re: Auto creation of Partitions

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: NikhilS <nikkhils(at)gmail(dot)com>
Subject: Re: Auto creation of Partitions
Date: 2007-03-06 12:40:02
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers pgsql-patches

NikhilS wrote:
> iv) Based on the PRIMARY, UNIQUE, REFERENCES information specified,
> pass it on to the children tables.

How will you maintain a primary key in such a table, considering that
indexes can't span multiple tables?

> 1) Whether we should use triggers/rules for step number (iii) above.
> Maybe rules is the way to go.

Since this would basically be a case of the updatable rules problem, you
should review those discussions in the past to check whether the issues
mentioned there don't interfere with that plan.

> 2) What other attributes (access permissions e.g.) of the master
> along with the ones specified in (iv) should be passed on to the
> children.

Moreover, how are later changes of those attributes propagated?

Peter Eisentraut

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2007-03-06 12:42:28 Re: GIST and TOAST
Previous Message Florian G. Pflug 2007-03-06 12:23:30 Re: Updated propsoal for read-only queries on PITR slaves (SoC 2007)

Browse pgsql-patches by date

  From Date Subject
Next Message Mike Rylander 2007-03-06 13:01:24 Re: [PATCHES] xml2 contrib patch supporting default XML namespaces
Previous Message NikhilS 2007-03-06 11:57:50 Auto creation of Partitions