| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Fix use-after-free bug when renaming constraints |
| Date: | 2018-12-17 03:45:41 |
| Message-ID: | E1gYjqf-0000pe-Hk@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Fix use-after-free bug when renaming constraints
This is an oversight from recent commit b13fd344. While on it, tweak
the previous test with a better name for the renamed primary key.
Detected by buildfarm member prion which forces relation cache release
with -DRELCACHE_FORCE_RELEASE. Back-patch down to 9.4 as the previous
commit.
Branch
------
REL9_4_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/696c68c2be44d478403be5c76e6e8160fabdb083
Modified Files
--------------
src/backend/commands/tablecmds.c | 4 ++--
src/test/regress/expected/alter_table.out | 2 +-
src/test/regress/sql/alter_table.sql | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2018-12-17 09:03:50 | pgsql: Remove extra semicolons. |
| Previous Message | Michael Paquier | 2018-12-17 01:38:09 | pgsql: Make constraint rename issue relcache invalidation on target rel |