From 5f286c02423f28c8e4c4d07569417a3d4f40f1a0 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 19 Mar 2015 13:02:09 -0400
Subject: [PATCH] doc:  ALTER DOMAIN VALIDATE CONSTRAINT can also fail
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

Document that ALTER DOMAIN VALIDATE CONSTRAINT can also fail for
composite types.

Report by Ondřej Bouda
---
 doc/src/sgml/ref/alter_domain.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/ref/alter_domain.sgml b/doc/src/sgml/ref/alter_domain.sgml
index f738b2948b..ac9a5b3f87 100644
--- a/doc/src/sgml/ref/alter_domain.sgml
+++ b/doc/src/sgml/ref/alter_domain.sgml
@@ -271,9 +271,9 @@ ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
   <title>Notes</title>
 
   <para>
-   Currently, <command>ALTER DOMAIN ADD CONSTRAINT</> and
-   <command>ALTER DOMAIN SET NOT NULL</> will fail if the validated named
-   domain or
+   Currently, <command>ALTER DOMAIN ADD CONSTRAINT</>, <command>ALTER
+   DOMAIN VALIDATE CONSTRAINT</>, and <command>ALTER DOMAIN SET NOT NULL</>
+   will fail if the validated named domain or
    any derived domain is used within a composite-type column of any
    table in the database.  They should eventually be improved to be
    able to verify the new constraint for such nested columns.
-- 
2.40.0