Received: from sss.pgh.pa.us ([192.204.191.242])
	by postgresql.org (8.11.3/8.11.4) with ESMTP id g0PKdhl72293
	for <pgsql-hackers@postgresql.org>;
	Fri, 25 Jan 2002 15:39:43 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g0PKdhf05241;
	Fri, 25 Jan 2002 15:39:43 -0500 (EST)
To: Vince Vielhaber <vev@michvhf.com>
cc: pgsql-hackers@postgresql.org
Subject: Re: sequence indexes 
In-reply-to: <Pine.BSF.4.40.0201251522300.47994-100000@paprika.michvhf.com> 
References: <Pine.BSF.4.40.0201251522300.47994-100000@paprika.michvhf.com>
Comments: In-reply-to Vince Vielhaber <vev@michvhf.com>
	message dated "Fri, 25 Jan 2002 15:24:10 -0500"
Date: Fri, 25 Jan 2002 15:39:42 -0500
Message-ID: <5238.1011991182@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200201/1236
X-Sequence-Number: 18204

Vince Vielhaber <vev@michvhf.com> writes:
> Is it safe to drop and recreate an index used by a sequence?

Uh, sequences haven't got indexes.  You mean an index on a "serial"
column, no?  Sure, there's no magic there.  Don't forget it's a
unique index, though, if you want to have the same error checking
as before.

			regards, tom lane