Received: from druid.net (root@druid.net [216.126.72.98]) by hub.org (8.10.1/8.10.1) with ESMTP id e7UBgrC01828 for ; Wed, 30 Aug 2000 07:42:53 -0400 (EDT) Received: from localhost (1432 bytes) by druid.net via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Wed, 30 Aug 2000 07:42:48 -0400 (EDT) (Smail-3.2.0.109 1999-Oct-27 #3 built 2000-Jun-28) Message-Id: From: darcy@druid.net (D'Arcy J.M. Cain) Subject: Re: Create Primary Key? In-Reply-To: "from Stephan Szabo at Aug 29, 2000 06:10:23 pm" To: Stephan Szabo Date: Wed, 30 Aug 2000 07:42:48 -0400 (EDT) CC: Webb Sprague , pgsql-sql@postgresql.org Reply-To: pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL78 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200008/338 Thus spake Stephan Szabo > We don't currently support the SQL syntax for adding > a PK to a table. However, if you have the columns > as NOT NULL already, adding a unique index to the > columns in question has the same general effect. Except for interfaces such as PyGreSQL that recognize the primary key and use it. > > Is there syntax to create a primary key after the > > table has been defined and populated? I think I could > > speed things up quite a bit by not having any indexes > > at all when I do my mass copies. Why not just use the copy function? That's what it's for. -- D'Arcy J.M. Cain | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.