Re: Setting a pre-existing index as a primary key

Tom Lane wrote:
> BTW, aside from selecting the index the command would have to verify
> that the indexed columns are all NOT NULL.  We could either have it
> just throw an error if they aren't, or have it silently try to do
> an ALTER SET NOT NULL, which would require a table scan.
>
> I'm going to argue for the "just throw an error" choice.  I don't like
> the idea of a utility command that takes exclusive lock and then is
> either near-instantaneous or slow depending on factors not immediately
> obvious.
>
> 			
>   

+1

cheers

andrew