[COMMITTERS] pgsql: Move autogenerated array types out of the way during ALTER ...R - Mailing list pgsql-committers

From Tom Lane
Subject [COMMITTERS] pgsql: Move autogenerated array types out of the way during ALTER ...R
Date
Msg-id E1dEKl3-0008Si-Gd@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Move autogenerated array types out of the way during ALTER ... RENAME.

Commit 9aa3c782c added code to allow CREATE TABLE/CREATE TYPE to not fail
when the desired type name conflicts with an autogenerated array type, by
dint of renaming the array type out of the way.  But I (tgl) overlooked
that the same case arises in ALTER TABLE/TYPE RENAME.  Fix that too.
Back-patch to all supported branches.

Report and patch by Vik Fearing, modified a bit by me

Discussion: https://postgr.es/m/0f4ade49-4f0b-a9a3-c120-7589f01d1eb8@2ndquadrant.com

Branch
------
REL9_4_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/8f62b388b5c946cc1c6e5c1c6fd5cff0865b46a9

Modified Files
--------------
src/backend/catalog/pg_type.c             | 38 ++++++++++++++++++------
src/test/regress/expected/alter_table.out | 49 +++++++++++++++++++++++++++++++
src/test/regress/sql/alter_table.sql      | 20 +++++++++++++
3 files changed, 98 insertions(+), 9 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Fix pg_dump to not emit invalid SQL for an empty operatorclass.
Next
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Fix typo in pg_dump's support for dumping collations frompre-v1