BUG #19757: attname in pg_attribute not strictly updated when renaming a column

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: jonas-lugner(at)gmx(dot)de
Subject: BUG #19757: attname in pg_attribute not strictly updated when renaming a column
Date: 2026-10-14 14:04:55
Message-ID: 19757-c2dcdf7e64e5f1c7@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 19757
Logged by: Jonas
Email address: jonas-lugner(at)gmx(dot)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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sami Imseih 2026-10-14 14:41:24 Re: pg_stat_statements stores WITH HOLD cursor query with literals
Previous Message Narayanan Venkateswaran 2026-10-14 13:35:50 Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses