From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: jonas-lugner@gmx.de
Subject: BUG #19757: attname in pg_attribute not strictly updated when renaming a column
Date: Wed, 14 Oct 2026 14:04:55 +0000
Message-ID: <19757-c2dcdf7e64e5f1c7@postgresql.org> (raw)
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:
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, jonas-lugner@gmx.de
Subject: Re: BUG #19757: attname in pg_attribute not strictly updated when renaming a column
In-Reply-To: <19757-c2dcdf7e64e5f1c7@postgresql.org>
References: <19757-c2dcdf7e64e5f1c7@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox