Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
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:11:01
Message-ID: 1578747.1620929461@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2021-May-13, PG Bug reporting form wrote:
>> I'm using pg_dump to dump my database version 12.5 (RDS), pg_dump version
>> 12.6 but I have a the following table

> How did you get this table definition?

Indeed. It seems unlikely to me that this is pg_dump's fault;
I think it's just reporting the way things are in the source
database. If projects_historydata_id_seq is the wrong width,
that's probably because it was manually created that way and
then manually attached to projects_historydata.id.

> 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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jaime Acevedo 2021-05-13 18:20:35 Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
Previous Message varun kamal 2021-05-13 16:54:11 Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault