BUG #2073: Can't drop sequence when created via SERIAL column

From: "Aaron Dummer" <aaron(at)dummer(dot)info>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2073: Can't drop sequence when created via SERIAL column
Date: 2005-11-28 21:10:33
Message-ID: 20051128211033.EECFCF0ACA@svr2.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 2073
Logged by: Aaron Dummer
Email address: aaron(at)dummer(dot)info
PostgreSQL version: 8.0.3
Operating system: Debian Linux
Description: Can't drop sequence when created via SERIAL column
Details:

If I create a table named foo with a column named bar, column type SERIAL,
it auto-generates a sequence named foo_bar_seq. Now if I manually create a
new sequence called custom_seq, and change the default value of foo.bar to
reference the new sequence, I still can't delete the old sequence
(foo_bar_seq).

In other words, from a user's point of view, the foo table is no longer
dependent on the foo_bar_seq, yet the system still sees it as dependent.

I brought this topic up on the #postgresql IRC channel and the behavior was
confirmed by AndrewSN, scampbell_, and mastermind.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2005-11-28 22:11:24 Re: segfault of autovacuum process during restore - coredumps included
Previous Message Jim C. Nasby 2005-11-28 20:53:54 Re: On-line backup