Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wCHB3-001pHP-0I for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Apr 2026 13:18:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wCHB1-0078UD-1k for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Apr 2026 13:18:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wCGiy-006lIt-0K for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2026 12:49:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wCGiw-00000000pqj-16AJ for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2026 12:49:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=7h3cCBpBpjmP7F2l39qvjY25NcYA8pIAjB/6Tzo/Zj8=; b=FYjo7xUm/nQTjAcDP1qwddp6Af QXyFdwqv48rLS2YSU0YkSGMs7hfufad7pjKZ20dG0m/zSSpnQy0bcSfh5WqOh/UhLdfiTc30Y6Pia KCZNhsMVzv0rSoLOM6pxfIT4BdePAg0zJlW8g2UVNpKhFCUwmWHdz6+2yTk40sDZIUa8g/DZarNG1 iA52iqU1BvKJFDB5vaa6KHQpMVCn1sjOCv5er2gX6FTvmVf5MBmPN3RJg063TEnPqPZLDNd/xL5TU zzVZlgdmoUaM4l+W7Zox6zHOaVzWQmbSOf8M6r4STLyFzMBAl4qVG8zDcq5LqEtSdzUAG4t6Cy76c LX3o2psg==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wCGiu-002NYY-1E for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2026 12:49:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wCGis-004ufR-2k for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2026 12:49:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19455: ALTER TABLE RENAME will rename a sequence To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: bsislow@accertify.com Reply-To: bsislow@accertify.com, pgsql-bugs@lists.postgresql.org Date: Mon, 13 Apr 2026 12:48:35 +0000 Message-ID: <19455-8dabf39f306c3ccc@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19455 Logged by: Bob Sislow Email address: bsislow@accertify.com PostgreSQL version: 15.2 Operating system: Red Hat Enterprise Linux release 8.7 (Ootpa) Description: =20 Is this expected behavior? ALTER TABLE RENAME will rename a sequence. postgres=3D# create sequence test; CREATE SEQUENCE postgres=3D# \ds List of relations Schema | Name | Type | Owner ----------+------+----------+---------- dbaadmin | test | sequence | postgres (1 row) postgres=3D# alter table test rename to test2; ALTER TABLE postgres=3D# \ds List of relations Schema | Name | Type | Owner ----------+-------+----------+---------- dbaadmin | test2 | sequence | postgres (1 row)