From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | jacevedo(at)we-techs(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type |
Date: | 2021-05-13 18:21:41 |
Message-ID: | 20210513182141.GA20432@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2021-May-13, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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)
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2021-05-13 18:29:31 | Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type |
Previous Message | Jaime Acevedo | 2021-05-13 18:20:35 | Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type |