Received: from news.tht.net (news.hub.org [216.126.91.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fB7J9Fm96248 for ; Fri, 7 Dec 2001 14:09:15 -0500 (EST) (envelope-from news@news.tht.net) Received: (from news@localhost) by news.tht.net (8.11.4/8.11.4) id fB7IivQ43111 for pgsql-sql@postgresql.org; Fri, 7 Dec 2001 13:44:57 -0500 (EST) (envelope-from news) From: mcornell@spamcop.net (mcornell) X-Newsgroups: comp.databases.postgresql.sql Subject: serial sequences not automatically dropped Date: 7 Dec 2001 10:44:55 -0800 Organization: http://groups.google.com/ Lines: 13 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: groups-abuse@google.com To: pgsql-sql@postgresql.org X-Archive-Number: 200112/94 X-Sequence-Number: 5917 Hi Folks, 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! matt mcornell@spamcop.net