From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
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:21:41 -0400
Message-ID: <20210513182141.GA20432@alvherre.pgsql> (raw)
In-Reply-To: <1578747.1620929461@sss.pgh.pa.us>
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)
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: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, 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: <20210513182141.GA20432@alvherre.pgsql>
* 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