Re: renaming+recreating table w/default sequence causes dependency seq issue

From: Todd Kover <kovert(at)omniscient(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: renaming+recreating table w/default sequence causes dependency seq issue
Date: 2012-08-08 23:42:51
Message-ID: 201208082342.q78NgpB2019292@guinness.omniscient.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


> I don't see any bug there. The ALTER DROP DEFAULT command does not
> remove the sequence's dependence on foo.id; nor for that matter
> does ALTER SET DEFAULT create an auto-drop dependency on the new
> table. See ALTER SEQUENCE OWNED BY if you want to dissociate a
> serial column's sequence from the column, or reattach it to another
> column.
>
> Formally speaking, a "serial column" is shorthand for creating an
> integer (or bigint) column, creating a sequence, associating them as
> though by ALTER SEQUENCE OWNED BY, and setting the column's default
> to nextval('sequence-name').

I stand corrected. It would be nice if \ds or \ds+ or something showed
this relationship so it was evident. That's more of a feature request
than a bug fix tho.

apologies for the misdirection.

-Todd

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2012-08-09 08:49:28 Re: BUG #6722: Debugger broken?
Previous Message kargor 2012-08-08 16:05:37 Re: BUG #6722: Debugger broken?