Date: Thu, 13 May 2021 14:21:41 -0400
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: jacevedo@we-techs.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
Message-ID: <20210513182141.GA20432@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1578747.1620929461@sss.pgh.pa.us>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/20210513182141.GA20432%40alvherre.pgsql>
Precedence: bulk

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)