Skip site navigation (1) Skip section navigation (2)

Re: Problem identifying constraints which should not be inherited

From: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
To: "NikhilS" <nikkhils(at)gmail(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Alvaro Herrera" <alvherre(at)commandprompt(dot)com>,"Bruce Momjian" <bruce(at)momjian(dot)us>,"Chris Fischer" <Chris(dot)Fischer(at)channeladvisor(dot)com>,<pgsql-bugs(at)postgresql(dot)org>,"PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Problem identifying constraints which should not be inherited
Date: 2008-03-27 11:52:26
Message-ID: 47EB8A7A.9010208@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
NikhilS wrote:
> Am important decision here is about adding a new attribute to pg_constraint
> as it is the only sane way of determining inherited constraints, but that
> will require an initdb. Comments?

There's no problem forcing an initdb at this point in the release cycle. 
We will do that for sure many times before we reach beta stage.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

In response to

pgsql-hackers by date

Next:From: Zdenek KotalaDate: 2008-03-27 12:15:48
Subject: Re: Script binaries renaming
Previous:From: Alvaro HerreraDate: 2008-03-27 11:14:57
Subject: Re: [DOCS] pg_total_relation_size() and CHECKPOINT

pgsql-bugs by date

Next:From: Tom LaneDate: 2008-03-27 15:24:29
Subject: Re: Problem identifying constraints which should not be inherited
Previous:From: NikhilSDate: 2008-03-27 11:14:19
Subject: Re: Problem identifying constraints which should not be inherited

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group