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

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: 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 16:52:59
Message-ID: 20210513165259.GA13629@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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
>
> CREATE TABLE public.projects_historydata
> (
> id bigint NOT NULL DEFAULT
> nextval('projects_historydata_id_seq'::regclass),
> value double precision NOT NULL,
> value_at timestamp with time zone NOT NULL,
> var_id integer NOT NULL,
> created timestamp with time zone NOT NULL,
> CONSTRAINT projects_historydata_pkey PRIMARY KEY (id),
> CONSTRAINT projects_historydata_var_id_21f99477_fk_projects_var_id
> FOREIGN KEY (var_id)
> REFERENCES public.projects_var (id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION
> DEFERRABLE INITIALLY DEFERRED
> )
>
> WITH (
> autovacuum_enabled = TRUE
> )
> TABLESPACE pg_default;

Hello Jaime

How did you get this table definition?

I suggest to run this:
ALTER SEQUENCE projects_historydata_id_seq OWNED BY public.projects_historydata.id
and then things will work better.

Cheers

--
Álvaro Herrera Valdivia, Chile

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message varun kamal 2021-05-13 16:54:11 Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault
Previous Message David G. Johnston 2021-05-13 16:31:42 Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type