Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
Date
Msg-id 20210513182141.GA20432@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 2021-May-13, Tom Lane wrote:

> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:

> > I suggest to run this:
> >   ALTER SEQUENCE projects_historydata_id_seq OWNED BY public.projects_historydata.id 
> > and then things will work better.
> 
> This won't in itself fix the sequence's width; you'd need
> to do some additional ALTERs if that's wrong.

True.

What I'm thinking is that Jaime misunderstood what the actual problem
is; note that he posted the CREATE SEQUENCE statement for an unrelated
sequence, and didn't post any statement for the correct one.  He thinks
the problem is related to the sequence being bigint, but I doubt it
really is.

-- 
Álvaro Herrera       Valdivia, Chile
"No tengo por qué estar de acuerdo con lo que pienso"
                             (Carlos Caszeli)



pgsql-bugs by date:

Previous
From: Jaime Acevedo
Date:
Subject: Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type