From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: jacevedo@we-techs.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
Date: Thu, 13 May 2021 14:11:01 -0400
Message-ID: <1578747.1620929461@sss.pgh.pa.us> (raw)
In-Reply-To: <20210513165259.GA13629@alvherre.pgsql>
References: <20210513165259.GA13629@alvherre.pgsql>
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 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org, 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: <1578747.1620929461@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox