BUG #10526: bad sequence rename

Started by Nonamealmost 12 years ago3 messagesbugs
Jump to latest
#1Noname
gnuplanet@gmail.com

The following bug has been logged on the website:

Bug reference: 10526
Logged by: Alexey
Email address: gnuplanet@gmail.com
PostgreSQL version: 9.3.4
Operating system: Debian GNU/Linux
Description:

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)
xxx=> select version();
version

----------------------------------------------------------------------------------------------
PostgreSQL 9.3.4 on x86_64-unknown-linux-gnu, compiled by gcc (Debian
4.8.3-2) 4.8.3, 64-bit
(1 row)

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#2Vik Fearing
vik@postgresfriends.org
In reply to: Noname (#1)
Re: BUG #10526: bad sequence rename

On 06/04/2014 01:16 PM, gnuplanet@gmail.com wrote:

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)
xxx=> select version();
version

----------------------------------------------------------------------------------------------
PostgreSQL 9.3.4 on x86_64-unknown-linux-gnu, compiled by gcc (Debian
4.8.3-2) 4.8.3, 64-bit
(1 row)

This is a duplicate of bug #7920. The decision on that was to do nothing:
/messages/by-id/14588.1362580075@sss.pgh.pa.us
--
Vik

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Noname (#1)
Re: BUG #10526: bad sequence rename

gnuplanet@gmail.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

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs