From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: jacevedo@we-techs.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
In-reply-to: <20210513165259.GA13629@alvherre.pgsql>
References: <20210513165259.GA13629@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
	message dated "Thu, 13 May 2021 12:52:59 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1578746.1620929461.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 13 May 2021 14:11:01 -0400
Message-ID: <1578747.1620929461@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1578747.1620929461%40sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.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 versi=
on
>> 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_hi=
storydata.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