Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fBAL9hm19468 for ; Mon, 10 Dec 2001 16:09:44 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id A0068D5E9; Mon, 10 Dec 2001 13:09:39 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 93B435BEE; Mon, 10 Dec 2001 13:09:39 -0800 (PST) Date: Mon, 10 Dec 2001 13:09:39 -0800 (PST) From: Stephan Szabo To: mcornell Cc: Subject: Re: serial sequences not automatically dropped In-Reply-To: Message-ID: <20011210130658.X70079-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200112/111 X-Sequence-Number: 5934 On 7 Dec 2001, mcornell wrote: > We're new to postgres and using it on Linux and OS X. We've had to > change our code to work around what looks like a bug: When a table > that contains a SERIAL column is dropped, the corresponding sequence > for that column is *not* dropped. This is a pain, because we are > trying to support multiple RDBMSs, and only postgres requires this. It > seems like it should be keeping track of which columns are serial and > drop them when the table is dropped. Please tell us: Any plans to > address this in the near future? Thanks! There's been discussion about this in the past. This will probably be dealt with as soon as we start doing a more meaningful list of what objects depend on what other objects. Right now, there's no good way to make sure that the sequence isn't being refered to from something else, and I'm not sure what the correct behavior would be in that case (probably depends on the whole restrict/cascade thing I guess).