pgsql: Assign constraint name when cloning FK definition forpartitions - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: Assign constraint name when cloning FK definition forpartitions
Date
Msg-id E1g8fdX-00025G-US@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Assign constraint name when cloning FK definition for partitions

This is for example used when attaching a partition to a partitioned
table which includes foreign keys, and in this case the constraint name
has been missing in the data cloned.  This could lead to hard crashes,
as when validating the foreign key constraint, the constraint name is
always expected.  Particularly, when using log_min_messages >= DEBUG1, a
log message would be generated with this unassigned constraint name,
leading to an assertion failure on HEAD.

While on it, rename a variable in ATExecAttachPartition which was
declared twice with the same name.

Author: Michael Paquier
Reviewed-by: Álvaro Herrera
Discussion: https://postgr.es/m/20181005042236.GG1629@paquier.xyz
Backpatch-through: 11

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/c905b67b79b72b88ba80d2486443c824232c6d85

Modified Files
--------------
src/backend/catalog/pg_constraint.c |  1 +
src/backend/commands/tablecmds.c    | 14 +++++++-------
2 files changed, 8 insertions(+), 7 deletions(-)


pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: pgsql: doc: update PG 11 release notes
Next
From: Dean Rasheed
Date:
Subject: pgsql: Improve the accuracy of floating point statistical aggregates.