diff options
| author | Michael Paquier <michael@paquier.xyz> | 2018-12-17 10:36:21 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2018-12-17 10:36:21 +0900 |
| commit | da13d90a5fba051d16df3b4fdaac23abc9560f38 (patch) | |
| tree | 6c0cf2d30ec59c7a16e59a3ed4694886afe63641 /src/backend/access/gist/gist.c | |
| parent | f4290113f50d1bcd67a9e51b74927c59592ad2ea (diff) | |
| download | postgresql-da13d90a5fba051d16df3b4fdaac23abc9560f38.tar.gz postgresql-da13d90a5fba051d16df3b4fdaac23abc9560f38.zip | |
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
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions