aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2019-01-18 14:49:27 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2019-01-18 14:57:49 -0300
commitfca6cabed17c4960224408d44e3d384b560b78f5 (patch)
tree54fc485341bac9557e85bb1e67bf7a86db964903 /src/backend/executor/nodeModifyTable.c
parente974f223abb473ba62577261378ca740c641814f (diff)
downloadpostgresql-fca6cabed17c4960224408d44e3d384b560b78f5.tar.gz
postgresql-fca6cabed17c4960224408d44e3d384b560b78f5.zip
Move CloneForeignKeyConstraints to tablecmds.c
My commit 3de241dba86f introduced some code to create a clone of a foreign key to a partition, but I put it in pg_constraint.c because it was too close to the contents of the pg_constraint row. With the previous commit that split out the constraint tuple deconstruction into its own routine, it makes more sense to have the FK-cloning function in tablecmds.c, mostly because its static subroutine can then be used by a future bugfix. My initial posting of this patch had this routine as static in tablecmds.c, but sadly this function is already part of the Postgres 11 ABI as exported from pg_constraint.c, so keep it as exported also just to avoid breaking any possible users of it.
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions