Re: BUG #10526: bad sequence rename

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: gnuplanet(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #10526: bad sequence rename
Date: 2014-06-04 14:35:58
Message-ID: 19803.1401892558@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

gnuplanet(at)gmail(dot)com writes:
> xxx=> create sequence a;
> CREATE SEQUENCE
> xxx=> alter sequence a rename to b;
> ALTER SEQUENCE
> xxx=> select sequence_name from b;
> sequence_name
> ---------------
> a
> (1 row)

This is not a bug; it's just how sequences work.

20-20 hindsight would suggest that the sequence name should never have
been included in the sequence data at all, but it's there and it will
always represent the original sequence name.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Keith Fiske 2014-06-04 15:44:50 Re: [BUGS] BUG #9652: inet types don't support min/max
Previous Message Vik Fearing 2014-06-04 13:47:42 Re: BUG #10526: bad sequence rename