Rename Cloudberry Database to Apache Cloudberry

Rename the old name "Cloudberry Database" to "Apache Cloudberry" in the
directory doc/src/sgml/ref/*.sgml.

doc/src/sgml/ref/alter_resource_queue.sgml

@@ -245,7 +245,7 @@ ALTER RESOURCE QUEUE myqueue WITHOUT (MAX_COST, MEMORY_LIMIT);
 
   <para>
    There is no <command>ALTER RESOURCE QUEUE</command> in the SQL standard.
-   Resource scheduling is a feature of Cloudberry Database.
+   Resource scheduling is a feature of Apache Cloudberry.
   </para>
    </refsect1>
 

doc/src/sgml/ref/alter_table.sgml

@@ -1138,7 +1138,7 @@ Where column_reference_storage_directive is:
    has subpartition encodings, the new partition 
    inherits the storage directives for the subpartitions. 
    For more information, search for "Precedence of Compression Settings" 
-   in the Cloudberry Database Administrator Guide.
+   in the Apache Cloudberry Administrator Guide.
   </para>
 
   <para>

doc/src/sgml/ref/create_external_table.sgml

@@ -138,15 +138,15 @@ CREATE WRITABLE EXTERNAL WEB [TEMPORARY | TEMP] TABLE table_name
     SQL query against external data without requiring that data to first be loaded 
     into the database. External tables provide an easy way to perform basic extraction, 
     transformation, and loading (ETL) tasks that are common in data warehousing. 
-    External table files are read in parallel by the Cloudberry Database segment instances, 
+    External table files are read in parallel by the Apache Cloudberry segment instances, 
     so they also provide a means for fast data loading. External tables should not be used 
     for frequently queried tables.
   </para>
 
   <para>
     You may specify multiple external data sources or URIs (uniform resource identifiers) 
-    with the <literal>LOCATION</literal> clause � up to the number of primary segment instances 
-    in your Cloudberry Database array. Each URI points to an external data file or other data 
+    with the <literal>LOCATION</literal> clause � up to the number of primary segment instances 
+    in your Apache Cloudberry array. Each URI points to an external data file or other data 
     source. These URIs do not need to exist prior to defining an external table (<command>CREATE EXTERNAL TABLE</command> 
     does not validate the URIs specified). However you will get an error if they cannot be found 
     when querying the external table.
@@ -159,21 +159,21 @@ CREATE WRITABLE EXTERNAL WEB [TEMPORARY | TEMP] TABLE table_name
   </para>
 
   <para>
-    gpfdist � If using the <literal>gpfdist://</literal> protocol, you must have the 
+    gpfdist � If using the <literal>gpfdist://</literal> protocol, you must have the 
     Cloudberry file distribution program (<literal>gpfdist</literal>) running on the host where the external 
     data files reside. This program points to a given directory on the file host and 
-    serves external data files to all Cloudberry Database segments in parallel. 
+    serves external data files to all Apache Cloudberry segments in parallel. 
     All primary segments access the external file(s) in parallel regardless of how 
     many URIs you specify when defining the external table. <literal>gpfdist</literal> 
-    is located in <literal>$GPHOME/bin<literal> on your Cloudberry Database master host. 
+    is located in <literal>$GPHOME/bin<literal> on your Apache Cloudberry master host. 
   </para>
 
   <para>
-    file � If using the <literal>file://</literal> protocol the external data file(s) 
+    file � If using the <literal>file://</literal> protocol the external data file(s) 
     must reside on a segment host in a location accessible by the Cloudberry super user 
     (gpadmin). The number of URIs specified corresponds to the number of segment 
     instances that will work in parallel to access the external table. So for 
-    example, if you have a Cloudberry Database system with 8 primary segments and 
+    example, if you have a Apache Cloudberry system with 8 primary segments and 
     you specify 2 external files, only 2 of the 8 segments will access the external 
     table in parallel at query time. The number of external files per segment host 
     cannot exceed the number of primary segment instances on that host. For example, 
@@ -184,11 +184,11 @@ CREATE WRITABLE EXTERNAL WEB [TEMPORARY | TEMP] TABLE table_name
   </para>
 
   <para>
-    http � If using the <literal>http://</literal> protocol the external data file(s) 
+    http � If using the <literal>http://</literal> protocol the external data file(s) 
     must reside on a web server that is accessible by the Cloudberry segment hosts. 
     The number of URIs specified corresponds to the number of segment instances 
     that will work in parallel to access the external table. So for example, 
-    if you have a Cloudberry Database system with 8 primary segments and you specify 2 
+    if you have a Apache Cloudberry system with 8 primary segments and you specify 2 
     external files, only 2 of the 8 segments will access the external table in 
     parallel at query time.
     </para>
@@ -199,7 +199,7 @@ CREATE WRITABLE EXTERNAL WEB [TEMPORARY | TEMP] TABLE table_name
     or comma separated values (CSV) format. If the data in the file does not 
     use the default column delimiter, escape character, null string and so on, 
     you must specify the additional formatting options so that the data in 
-    the external file is read correctly by Cloudberry Database.
+    the external file is read correctly by Apache Cloudberry.
 </para>
 
 </refsect1>
@@ -418,7 +418,7 @@ CREATE WRITABLE EXTERNAL WEB [TEMPORARY | TEMP] TABLE table_name
   <title id="SQL-CREATEEXTERNALTABLE-compatibility-title">Compatibility</title>
 
   <para>
-   The <command>CREATE EXTERNAL TABLE</command> is a Cloudberry Database extension. 
+   The <command>CREATE EXTERNAL TABLE</command> is a Apache Cloudberry extension. 
    The <acronym>SQL</acronym> standard makes no provisions for external tables.
   </para>
  </refsect1>

doc/src/sgml/ref/create_resource_queue.sgml

@@ -43,7 +43,7 @@ where queue_attribute is:
 
   <para>
    <command>CREATE RESOURCE QUEUE</command> create a new resource queue 
-   for Cloudberry Database workload management. A resource queue must have 
+   for Apache Cloudberry workload management. A resource queue must have 
    either an ACTIVE_STATEMENTS or a MAX_COST value (or it can have both). 
    Only a superuser can create a resource queue.
   </para>
@@ -60,7 +60,7 @@ where queue_attribute is:
    Resource queues with a MAX_COST threshold set a maximum limit on the total 
    cost of queries that can be executed by roles assigned to that queue. Cost 
    is measured in the estimated total cost for the query as determined by the 
-   Cloudberry Database query planner (as shown in the EXPLAIN output for a query). 
+   Apache Cloudberry query planner (as shown in the EXPLAIN output for a query). 
    Therefore, an administrator must be familiar with the queries typically executed 
    on the system in order to set an appropriate cost threshold for a queue. Cost is 
    measured in units of disk page fetches; 1.0 equals one sequential disk page read. 
@@ -275,7 +275,7 @@ CREATE RESOURCE QUEUE myqueue WITH (ACTIVE_STATEMENTS=30, MAX_COST=5000.00);
 
   <para>
    There is no <command>CREATE RESOURCE QUEUE</command> in the SQL standard.
-   Resource scheduling is a feature of Cloudberry Database.
+   Resource scheduling is a feature of Apache Cloudberry.
   </para>
    </refsect1>
 

doc/src/sgml/ref/create_table.sgml

@@ -227,7 +227,7 @@ Where column_reference_storage_directive is:
    a column constraint is only a notational convenience for use when the
    constraint only affects one column.    For more information, search for 
 
-   "Column-level Compression" in the Cloudberry Database Administrator Guide.
+   "Column-level Compression" in the Apache Cloudberry Administrator Guide.
   </para>
 
   <para>

doc/src/sgml/ref/create_trigger.sgml

@@ -21,7 +21,7 @@ PostgreSQL documentation
 
  <refnamediv>
   <refname>CREATE TRIGGER</refname>
-  <refpurpose>define a new trigger (user-defined triggers are not fully supported in Cloudberry Database)</refpurpose>
+  <refpurpose>define a new trigger (user-defined triggers are not fully supported in Apache Cloudberry)</refpurpose>
  </refnamediv>
 
  <refsynopsisdiv>

doc/src/sgml/ref/drop_resource_queue.sgml

@@ -97,7 +97,7 @@ ALTER ROLE RESOURCE QUEUE none;
 
   <para>
    There is no <command>DROP RESOURCE QUEUE</command> in the SQL standard.
-   Resource scheduling is a feature of Cloudberry Database.
+   Resource scheduling is a feature of Apache Cloudberry.
   </para>
 
  </refsect1>