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

From Tom Lane
Subject Re: Setting a pre-existing index as a primary key
Date
Msg-id 2714.1210434929@sss.pgh.pa.us
Whole thread Raw
In response to Re: Setting a pre-existing index as a primary key  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Setting a pre-existing index as a primary key  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Setting a pre-existing index as a primary key  (Andrew Sullivan <ajs@commandprompt.com>)
List pgsql-hackers
"Joshua D. Drake" <jd@commandprompt.com> writes:
> As a counter point, I don't see any reason to make the DBA's life 
> harder. Sure it is just one step but it is a human step, prone to error 
> and taking more time than it should. Why not just make it easy? 

I don't see that decorating infrequently-used statements with bizarre
options that duplicate the functionality of other commands is "making it
easy".  Apparently your definition of "easy" depends entirely on
keystrokes and not at all on memory/cognitive burden.

IMHO a utility command should do one easily-explained thing.  The fewer
options the better.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Setting a pre-existing index as a primary key
Next
From: Andrew Dunstan
Date:
Subject: Re: constraint exclusion analysis caching