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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: 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 00:17:48
Message-ID: CAKFQuwbpUZbxXV696JKa5VukS6DmotfrvU2XX1duNNx1gipCMQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Aug 16, 2019, 4:25 PM PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the
>

Looking at the properties of the sequence I still see it tied to the older
> table
> Column d2_search_history_2019050.search_id auto
> Column d2_search_history.search_id normal
>
> 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?

David J.

>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-08-17 05:01:36 BUG #15963: DB Connection Error at regular time periods
Previous Message PG Bug reporting form 2019-08-16 23:24:05 BUG #15962: Cannot drop table that previously had a 'serial' column