postgres.git / summary / log / commit / refs

commit    e0047269a8c92e5af30eaa2c587e60ff21ec64fb
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Tue Jun 14 21:47:09 2022 +0000
First released in: 15.0, 10.22, 11.17, 12.12, 13.8, 14.5

    Doc: clarify the default collation behavior of domains.
    
    The previous wording was "the underlying data type's default collation
    is used", which is wrong or at least misleading.  The domain inherits
    the base type's collation behavior, which if "default" actually can
    mean that we use some non-default collation obtained from elsewhere.
    
    Per complaint from Jian He.
    
    Discussion: https://postgr.es/m/CACJufxHMR8_4WooDPjjvEdaxB2hQ5a49qthci8fpKP0MKemVRQ@mail.gmail.com


 doc/src/sgml/ref/create_domain.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/create_domain.sgml b/doc/src/sgml/ref/create_domain.sgml
index 6b426d21708..1ea87681c80 100644
--- a/doc/src/sgml/ref/create_domain.sgml
+++ b/doc/src/sgml/ref/create_domain.sgml
@@ -94,7 +94,8 @@ CREATE DOMAIN <replaceable class="parameter">name</replaceable> [ AS ] <replacea
       <listitem>
        <para>
         An optional collation for the domain.  If no collation is
-        specified, the underlying data type's default collation is used.
+        specified, the domain has the same collation behavior as its
+        underlying data type.
         The underlying type must be collatable if <literal>COLLATE</>
         is specified.
        </para>


[parent: db713aa7fcbe]