]> granicus.if.org Git - postgresql/commit
Make constraint rename issue relcache invalidation on target relation
authorMichael Paquier <michael@paquier.xyz>
Mon, 17 Dec 2018 01:36:29 +0000 (10:36 +0900)
committerMichael Paquier <michael@paquier.xyz>
Mon, 17 Dec 2018 01:36:29 +0000 (10:36 +0900)
commitd79cd555da115a15f6e63f5e687521d1e274ff9a
tree3b48abfcd4d10bcbbb0451a3820515220a1afee5
parentf7642cf31601b206cb7cfb99339e6b4edfec0b58
Make constraint rename issue relcache invalidation on target relation

When a constraint gets renamed, it may have associated with it a target
relation (for example domain constraints don't have one).  Not
invalidating the target relation cache when issuing the renaming can
result in issues with subsequent commands that refer to the old
constraint name using the relation cache, causing various failures.  One
pattern spotted was using CREATE TABLE LIKE after a constraint
renaming.

Reported-by: Stuart <sfbarbee@gmail.com>
Author: Amit Langote
Reviewed-by: Michael Paquier
Discussion: https://postgr.es/m/2047094.V130LYfLq4@station53.ousa.org
src/backend/commands/tablecmds.c
src/test/regress/expected/alter_table.out
src/test/regress/sql/alter_table.sql