> 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 sequen
Todd Kover writes:
> I saw issues around renaming tables and not renaming sequences in the TODO
> list but did not see anything about this. Apologies if I missed it.
> This is with a 9.1.4 server (enterprisedb download on mac os/x lion) and also
> seen on 9.1.3 built from netbsd pkgsrc.
> It ap
Excerpts from Todd Kover's message of mar ago 07 20:10:25 -0400 2012:
> Given this:
> --
> drop table IF EXISTS foo;
> drop table IF EXISTS foo_v26;
>
> create table foo (id serial not null, bar integer );
> alter table foo alter column id drop default;
>
> alter table foo rename to foo_v26;
I saw issues around renaming tables and not renaming sequences in the TODO
list but did not see anything about this. Apologies if I missed it.
This is with a 9.1.4 server (enterprisedb download on mac os/x lion) and also
seen on 9.1.3 built from netbsd pkgsrc.
It appears that something is amiss
