Re: BUG #4582: Renaming sequences and default value - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4582: Renaming sequences and default value
Date
Msg-id 8160.1229367122@sss.pgh.pa.us
Whole thread Raw
In response to BUG #4582: Renaming sequences and default value  ("Jan-Peter Seifert" <jan-peter.seifert@gmx.de>)
Responses Re: BUG #4582: Renaming sequences and default value  (Jan-Peter Seifert <Jan-Peter.Seifert@gmx.de>)
List pgsql-bugs
"Jan-Peter Seifert" <jan-peter.seifert@gmx.de> writes:
> there's a problem with renaming sequences in our databases.

I don't think there's really a problem here.  You've apparently got some
obsolete syntax in your CREATE commands:

>   id integer NOT NULL DEFAULT nextval(('public.t2_id_seq'::text)::regclass)

This specifically says that 'public.t2_id_seq' is a string (text) constant,
which is not going to change in response to anything.  If you would
like it to track renamings of the sequence then it needs to be a
regclass constant:

    id integer NOT NULL DEFAULT nextval('public.t2_id_seq'::regclass)

Also, neither of these forms will by itself establish an OWNED BY
relationship --- you'll need a separate ALTER SEQUENCE OWNED BY
command if you want that.

If that doesn't help, you'll need to be a lot more specific about the
actions you took.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Scott Carey
Date:
Subject: Re: BUG #4575: All page cache in shared_buffers pinned (duplicated by OS, always)
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #4027: backslash escaping not disabled in plpgsql