Re: BUG #15962: Cannot drop table that previously had a 'serial' column

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: steven(dot)morris(at)hypermediasystems(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15962: Cannot drop table that previously had a 'serial' column
Date: 2019-08-17 05:01:41
Message-ID: 23617.1566018101@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Fri, Aug 16, 2019, 4:25 PM PG Bug reporting form <noreply(at)postgresql(dot)org>
> wrote:
>> Any suggestions on how to remove the dependency it still has ? or will I
>> have to make a New sequence for the new table and call it ?

> Alter sequence?

ALTER SEQUENCE ... OWNED BY, in particular, should help here.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-08-17 19:06:33 BUG #15964: vacuumdb.c:187:10: error: use of undeclared identifier 'FD_SETSIZE'
Previous Message PG Bug reporting form 2019-08-17 05:01:36 BUG #15963: DB Connection Error at regular time periods