reshke commented on issue #1566:
URL: https://github.com/apache/cloudberry/issues/1566#issuecomment-3862195041

   ```
   reshke@yezzey-cbdb-bench:~/cbdb-pure$ git show be35a645690
   commit be35a6456901cfdf4df91697370dc5edac7e58c5
   Author: Tom Lane <[email protected]>
   Date:   Tue Jun 14 17:47:09 2022 -0400
   
       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_4woodpjjvedaxb2hq5a49qthci8fpkp0mkem...@mail.gmail.com
   
   diff --git a/doc/src/sgml/ref/create_domain.sgml 
b/doc/src/sgml/ref/create_domain.sgml
   index 81a89249260..e4b856d630c 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</literal>
            is specified.
           </para>
   ```
   
   
   already in, skip


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to