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.98.2) (envelope-from ) id 1xGziX-00000002lE9-1JQ0 for pgsql-bugs@arkaria.postgresql.org; Wed, 14 Oct 2026 14:12:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xGzhX-00000003Zb0-0G14 for pgsql-bugs@arkaria.postgresql.org; Wed, 14 Oct 2026 14:11:27 +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.98.2) (envelope-from ) id 1xGzbR-00000003ZTS-3mso for pgsql-bugs@lists.postgresql.org; Wed, 14 Oct 2026 14:05: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 1xGzbP-000000024jN-0jDo for pgsql-bugs@lists.postgresql.org; Wed, 14 Oct 2026 14:05:09 +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=GU4ChG0iV84E39q9bdSfy8HJ5sYTjoZV9wnZMM+rzxs=; b=xIC4QQLLCr05Nq+04N4Zr/RYpQ XOkGUAT6inpnxbhMPGYGRz6dWMyIEXxRkfxn/Hm/jIyFivCtJoX7JD90l5Ov9R7G84a8lbaKNilVj l/TSZcbnG//muSaJoq2wDz6Et6Kshukb2gnUia0sa5+MuJhGRvB4JQE2SLZZUfpiJLdq9/YE6ep48 8dfM2zjqKV/444wORvtuzxWNfEZSq5tqm93i/jwdNYSLSHSzjl+i6NpzBlUaXUBT8Y94hj8VHVOlo YYAsBxITdcUCMqlyuRKwcihOWWyYV4t5FQiOKer8fxNrlk29qp+SHhl9yxKbykxcu/c+OCvTvN3mv 3dcLpl8A==; 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.98.2) (envelope-from ) id 1xGzbN-00000005oUX-1U9m for pgsql-bugs@lists.postgresql.org; Wed, 14 Oct 2026 14:05:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xGzbM-00000000QbG-05aU for pgsql-bugs@lists.postgresql.org; Wed, 14 Oct 2026 14:05:04 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19757: attname in pg_attribute not strictly updated when renaming a column To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: jonas-lugner@gmx.de Reply-To: jonas-lugner@gmx.de, pgsql-bugs@lists.postgresql.org Date: Wed, 14 Oct 2026 14:04:55 +0000 Message-ID: <19757-c2dcdf7e64e5f1c7@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: 19757 Logged by: Jonas Email address: jonas-lugner@gmx.de PostgreSQL version: 16.15 Operating system: Alpine Linux via Docker Description: =20 Consider the following Code: CREATE TABLE employees ( email VARCHAR(255) UNIQUE ); ALTER TABLE employees RENAME COLUMN email TO contact_email; This generates two entries, but for one of those the attname remains `email` and is not updated to `contact_email` accordingly.