Received: from megazone.bigpanda.com ([63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g19HhrE09833 for ; Sat, 9 Feb 2002 12:43:53 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id C0BACD5FD; Sat, 9 Feb 2002 09:43:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id B67195BF8; Sat, 9 Feb 2002 09:43:58 -0800 (PST) Date: Sat, 9 Feb 2002 09:43:58 -0800 (PST) From: Stephan Szabo To: Bhuvan A Cc: Subject: Re: Adding a New Composite Constraint to an Existing Table. In-Reply-To: Message-ID: <20020209093613.L59069-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200202/98 X-Sequence-Number: 6526 On Sat, 9 Feb 2002, Bhuvan A wrote: > I am using postgresql 7.1. I was unable to add a new PRIMARY KEY > constraint to an existing table. > > i have table, > CREATE TABLE xx > ( > id int, > name text, > amount int > ); > > I have say some 10 records in this table, which are unique and not > null (primary). Fine! Now, i am willing to have primary key constraint > to all the 3 fields. > > I tried, > > bhuvan=> ALTER TABLE xx ADD primary key (id, name, amount); > ERROR: ALTER TABLE / ADD CONSTRAINT is not implemented for that > constraint type. > > Where i am wrong? How else, can i get that primary key constraint > WITHOUT RECREATING that table? On 7.1 you need a little magic depending on how exactly you want to make the primary key. I don't have a 7.1 machine available, but... You should make a unique index xx_pkey on xx(id, name, amount) You may want to update pg_index to set the indisprimary for that index, but I don't think that'll affect the actual running of the constraint. You'll then need to set the three columns NOT NULL by something like: update pg_attribute set attnotnull=true from pg_class where pg_class.oid=attrelid and relname='xx' and attname in ('id', 'name', 'amount');