Re: Setting a pre-existing index as a primary key - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Setting a pre-existing index as a primary key
Date
Msg-id 200805100150.m4A1oNT28688@momjian.us
Whole thread Raw
In response to Setting a pre-existing index as a primary key  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Responses Re: Setting a pre-existing index as a primary key
List pgsql-hackers
Added to TODO:
       o Allow an existing index to be marked as a table's primary key


---------------------------------------------------------------------------

Jonah H. Harris wrote:
> Hey all,
> 
> I've run into a couple cases now where it would be helpful to easily
> assign an already-existing unique index as a primary key.  Unless I
> completely missed something, there's no way to do this now without a
> bit of catalog hackery.
> 
> My implementation idea is as follows:
> 
> Proposed Syntax (based on Oracle's syntax)
> 
> ALTER TABLE foo ADD CONSTRAINT bar PRIMARY KEY USING INDEX schema.tablename;
> 
> Proposed Implementation
> 
> 1. Verify that the index named is a unique index
> 2. Check index columns for NOT NULL constraints
> 3. If indexed columns are not already NOT NULL, apply NOT NULL
> 4. If NOT NULL succeeds, complete the operation (catalogs,
> dependencies, ...), else bail out.
> 
> Any comments, ideas, suggestions?
> 
> -- 
> Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
> EnterpriseDB Corporation | fax: 732.331.1301
> 499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com
> Edison, NJ 08837 | http://www.enterprisedb.com/
> 
> -- 
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Small TRUNCATE glitch
Next
From: Robert Hodges
Date:
Subject: Re: Deterministic locking in PostgreSQL