Fix pg_dump COMMENT dependency for separate domain constraints.

The COMMENT should depend on the separately-dumped constraint, not the
domain.  Sufficient restore parallelism might fail the COMMENT command
by issuing it before the constraint exists.  Back-patch to v13, like
commit 0858f0f96ebb891c8960994f023ed5a17b758a38.

Reviewed-by: Álvaro Herrera <[email protected]>
Discussion: https://postgr.es/m/20250913020233[email protected]
Backpatch-through: 13

diff --git a/src/bin/pg_dump/pg_dump.c b/src/bin/pg_dump/pg_dump.c
index 802637fb24ea84da3890d80da8d5c3f8d9defc9a..9fc3671cb350c5c93b63bff2214c3027d02530b2 100644 (file)
--- a/src/bin/pg_dump/pg_dump.c
+++ b/src/bin/pg_dump/pg_dump.c
@@ -18796,7 +18796,7 @@ dumpConstraint(Archive *fout, const ConstraintInfo *coninfo)
                dumpComment(fout, conprefix->data, qtypname,
                            tyinfo->dobj.namespace->dobj.name,
                            tyinfo->rolname,
-                           coninfo->dobj.catId, 0, tyinfo->dobj.dumpId);
+                           coninfo->dobj.catId, 0, coninfo->dobj.dumpId);
                destroyPQExpBuffer(conprefix);
                free(qtypname);
            }