Doc: Rename old name to Apache Cloudberry

This commit is used to modify the old brand name `Cloudberry Database`
to `Apache Cloudberry`. The files are located in the following
directories:

- contrib/*
- gpAux/*
- gpMgmt/*
- gpcontrib/*
- src/:
  - src/backend
  - src/bin
  - src/include
  - src/test

contrib/Makefile

@@ -4,7 +4,7 @@ subdir = contrib
 top_builddir = ..
 include $(top_builddir)/src/Makefile.global
 
-# Cloudberry Database specific changes to the targetlist:
+# Apache Cloudberry specific changes to the targetlist:
 # tsearch2 and postgres_fdw are currently disabled due to test failures.
 # cube and the related earthdistance are disabled since GPDB define CUBE
 # as a keyword. lo is disabled since large objects aren't supported.

contrib/auto_explain/expected/auto_explain.out

@@ -4,12 +4,12 @@
 -- end_matchsubs
 CREATE SCHEMA auto_explain_test;
 CREATE TABLE auto_explain_test.t1(a int);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 INSERT INTO auto_explain_test.t1 VALUES(generate_series(0, 1000));
 ANALYZE auto_explain_test.t1;
 CREATE TABLE auto_explain_test.t2(b int);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'b' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'b' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 INSERT INTO auto_explain_test.t2 VALUES(generate_series(0, 1000));
 ANALYZE auto_explain_test.t2;

contrib/auto_explain/expected/auto_explain_optimizer.out

@@ -4,12 +4,12 @@
 -- end_matchsubs
 CREATE SCHEMA auto_explain_test;
 CREATE TABLE auto_explain_test.t1(a int);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 INSERT INTO auto_explain_test.t1 VALUES(generate_series(0, 1000));
 ANALYZE auto_explain_test.t1;
 CREATE TABLE auto_explain_test.t2(b int);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'b' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'b' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 INSERT INTO auto_explain_test.t2 VALUES(generate_series(0, 1000));
 ANALYZE auto_explain_test.t2;

contrib/bloom/expected/bloom.out

@@ -3,7 +3,7 @@ CREATE TABLE tst (
 	i	int4,
 	t	text
 );
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'i' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'i' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 INSERT INTO tst SELECT i%10, substr(md5(i::text), 1, 1) FROM generate_series(1,2000) i;
 CREATE INDEX bloomidx ON tst USING bloom (i, t) WITH (col1 = 3);
@@ -154,7 +154,7 @@ CREATE UNLOGGED TABLE tstu (
 	i	int4,
 	t	text
 );
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'i' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'i' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 INSERT INTO tstu SELECT i%10, substr(md5(i::text), 1, 1) FROM generate_series(1,2000) i;
 CREATE INDEX bloomidxu ON tstu USING bloom (i, t) WITH (col2 = 4);

contrib/bloom/expected/bloom_optimizer.out

@@ -3,7 +3,7 @@ CREATE TABLE tst (
 	i	int4,
 	t	text
 );
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'i' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'i' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 INSERT INTO tst SELECT i%10, substr(md5(i::text), 1, 1) FROM generate_series(1,2000) i;
 CREATE INDEX bloomidx ON tst USING bloom (i, t) WITH (col1 = 3);
@@ -146,7 +146,7 @@ CREATE UNLOGGED TABLE tstu (
 	i	int4,
 	t	text
 );
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'i' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'i' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 INSERT INTO tstu SELECT i%10, substr(md5(i::text), 1, 1) FROM generate_series(1,2000) i;
 CREATE INDEX bloomidxu ON tstu USING bloom (i, t) WITH (col2 = 4);

contrib/btree_gist/init_file

@@ -7,7 +7,7 @@
 # modify the corresponding expected output. Hence we want to ignore these.
 # Some of the messages include:
 #
-# NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named '<colname>' as the Cloudberry Database data distribution key for this table.
+# NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named '<colname>' as the Apache Cloudberry data distribution key for this table.
 # NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause, defaulting to distribution columns from LIKE table
 # HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 #

contrib/file_fdw/init_file

@@ -12,7 +12,7 @@ m/^ Settings:.*/
 # modify the corresponding expected output. Hence we want to ignore these.
 # Some of the messages include:
 #
-# NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named '<colname>' as the Cloudberry Database data distribution key for this table.
+# NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named '<colname>' as the Apache Cloudberry data distribution key for this table.
 # NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause, defaulting to distribution columns from LIKE table
 # HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 #

contrib/file_fdw/input/gp_file_fdw.source

@@ -1,5 +1,5 @@
 --
--- Test foreign-data wrapper file_fdw. Cloudberry Database MPP specific
+-- Test foreign-data wrapper file_fdw. Apache Cloudberry MPP specific
 --
 
 -- Clean up in case a prior regression run failed

contrib/file_fdw/output/gp_file_fdw.source

@@ -1,5 +1,5 @@
 --
--- Test foreign-data wrapper file_fdw. Cloudberry Database MPP specific
+-- Test foreign-data wrapper file_fdw. Apache Cloudberry MPP specific
 --
 -- Clean up in case a prior regression run failed
 SET client_min_messages TO 'error';

contrib/formatter_fixedwidth/output/readable_query10.source

@@ -21,7 +21,7 @@ NOTICE:  table "heap_col_null" does not exist, skipping
 CREATE TABLE heap_col_null (
     s1 char(10), s2 varchar(10), s3 text,
     col_empty character(5),col_null character varying(5) default 'NULL' );
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 's1' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 's1' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 \d heap_col_null
                              Table "public.heap_col_null"

contrib/hstore/expected/hstore.out

@@ -922,10 +922,10 @@ select hstore(v) from (values (1, 'foo', 1.2, 3::float8)) v(a,b,c,d);
 
 create domain hstestdom1 as integer not null default 0;
 create table testhstore0 (a integer, b text, c numeric, d float8);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 create table testhstore1 (a integer, b text, c numeric, d float8, e hstestdom1);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 insert into testhstore0 values (1, 'foo', 1.2, 3::float8);
 insert into testhstore1 values (1, 'foo', 1.2, 3::float8);
@@ -1273,7 +1273,7 @@ select 'a=>b, b=>1, c=>NULL'::hstore @> 'a=>b, c=>q';
 (1 row)
 
 CREATE TABLE testhstore (h hstore);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'h' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'h' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 \copy testhstore from 'data/hstore.data'
 select count(*) from testhstore where h @> 'wait=>NULL';

contrib/hstore_plperl/expected/create_transform.out

@@ -42,7 +42,7 @@ NOTICE:  transform for type hstore language "plperl" does not exist, skipping
 -- test pg_stat_last_operation
 CREATE TRANSFORM FOR hstore LANGUAGE plperl (FROM SQL WITH FUNCTION hstore_to_plperl(internal), TO SQL WITH FUNCTION plperl_to_hstore(internal));
 SELECT oid INTO temp transform_oid FROM pg_transform WHERE trfFROMsql='hstore_to_plperl'::regproc AND trftosql='plperl_to_hstore'::regproc;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'oid' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'oid' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 SELECT COUNT(*) = 1 FROM pg_stat_last_operation WHERE classid='pg_transform'::regclass AND objid=(SELECT oid FROM transform_oid limit 1);
  ?column? 

contrib/indexscan/expected/read_ao_index.out

@@ -1,7 +1,7 @@
 drop table if exists ao_t1;
 drop index if exists ao_i1;
 create table ao_t1 (a integer, b integer) with (appendonly=true);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 insert into ao_t1 select 1 as a, * from generate_series(1, 1000) as b;
 create index ao_i1 on ao_t1(b);

contrib/indexscan/expected/read_co_index.out

@@ -1,7 +1,7 @@
 drop table if exists co_t1;
 drop index if exists co_i1;
 create table co_t1 (a integer, b integer) with (appendonly=true, orientation=column);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 insert into co_t1 select 1 as a, * from generate_series(1, 1000) as b;
 create index co_i1 on co_t1(b);

contrib/indexscan/expected/read_heap_index.out

@@ -1,7 +1,7 @@
 drop table if exists heap_t1;
 drop index if exists heap_i1;
 create table heap_t1 (a integer, b integer);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 insert into heap_t1 select 1 as a, * from generate_series(1, 1000) as b;
 create index heap_i1 on heap_t1(b);

contrib/intarray/expected/_int.out

@@ -399,7 +399,7 @@ SELECT '1&(2&(4&(5|!6)))'::query_int;
 (1 row)
 
 CREATE TABLE test__int( a int[] );
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 \copy test__int from 'data/test__int.data'
 ANALYZE test__int;

contrib/intarray/package/gppkg_spec.yml.in

@@ -3,6 +3,6 @@ Architecture: #arch
 Version: ossv1.1_pv1.2_gpdb4.3orca
 OS: #os
 GPDBVersion: 4.3
-Description: Intarray provides functionality and GiST indexing capabilities for integer arrays in the Cloudberry Database. 
+Description: Intarray provides functionality and GiST indexing capabilities for integer arrays in the Apache Cloudberry. 
 PostInstall:
 - Master:  "echo 'Please run psql -d mydatabase -f $GPHOME/share/postgresql/contrib/_int.sql to enable the package.'"

contrib/intarray/package/intarray.spec

@@ -10,7 +10,7 @@ AutoProv:       no
 Provides:       intarray = %{intarray_ver} 
 
 %description
-The intarray package provides integer array functions and GiST index support for Cloudberry Database
+The intarray package provides integer array functions and GiST index support for Apache Cloudberry
 
 %install
 mkdir -p %{buildroot}/temp

contrib/oid2name/oid2name.c

@@ -110,7 +110,7 @@ get_opts(int argc, char **argv, struct options *my_opts)
 		}
 		if (strcmp(argv[1], "--version") == 0 || strcmp(argv[1], "-V") == 0)
 		{
-			puts("oid2name (Cloudberry Database) " PG_VERSION);
+			puts("oid2name (Apache Cloudberry) " PG_VERSION);
 			exit(0);
 		}
 	}

contrib/pg_standby/pg_standby.c

@@ -652,7 +652,7 @@ main(int argc, char **argv)
 		}
 		if (strcmp(argv[1], "--version") == 0 || strcmp(argv[1], "-V") == 0)
 		{
-			puts("pg_standby (Cloudberry Database) " PG_VERSION);
+			puts("pg_standby (Apache Cloudberry) " PG_VERSION);
 			exit(0);
 		}
 	}

contrib/pgcrypto/package/gppkg_spec.yml.in

@@ -3,6 +3,6 @@ Architecture: #arch
 Version: ossv1.1_pv1.2_gpdb4.3orca
 OS: #os
 GPDBVersion: 4.3
-Description: Pgcrypto provides cryptographic functions for the Cloudberry Database. 
+Description: Pgcrypto provides cryptographic functions for the Apache Cloudberry. 
 PostInstall:
 - Master:  "echo 'Please run psql -d mydatabase -f $GPHOME/share/postgresql/contrib/pgcrypto.sql to enable the package.'"

contrib/pgcrypto/package/pgcrypto.spec

@@ -1,4 +1,4 @@
-Summary:        Cryptographic functions for Cloudberry Database 
+Summary:        Cryptographic functions for Apache Cloudberry 
 License:        PostgreSQL License        
 Name:           pgcrypto
 Version:        %{pgcrypto_ver}
@@ -10,7 +10,7 @@ AutoProv:       no
 Provides:       pgcrypto = %{pgcrypto_ver} 
 
 %description
-The Pgcrypto package provides cryptographic functions for the Cloudberry Database.
+The Pgcrypto package provides cryptographic functions for the Apache Cloudberry.
 
 %install
 mkdir -p %{buildroot}/temp

contrib/postgres_fdw/expected/gp_postgres_fdw.out

@@ -83,7 +83,7 @@ CREATE TABLE "S 1"."GP 1" (
 	f2 text,
 	f3 text
 );
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'f1' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'f1' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 -- ===================================================================
 -- create foreign tables

contrib/postgres_fdw/expected/mpp_postgres_fdw.out

@@ -29,28 +29,28 @@ CREATE DATABASE fdw2;
 CREATE DATABASE fdw3;
 \c fdw1
 create table t1(a int, b text);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 create table t2(a int, b text);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 insert into t1 values(1, 'fdw1');
 insert into t2 values(1, 'fdw1');
 \c fdw2
 create table t1(a int, b text);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 create table t2(a int, b text);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 insert into t1 values(1, 'fdw2');
 insert into t2 values(1, 'fdw2');
 \c fdw3
 create table t1(a int, b text);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 create table t2(a int, b text);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 insert into t1 values(1, 'fdw3');
 insert into t2 values(1, 'fdw3');

contrib/postgres_fdw/expected/postgres_fdw.out

@@ -9578,7 +9578,7 @@ SELECT count(*) FROM ft1;
 
 -- error here
 PREPARE TRANSACTION 'fdw_tpc';
-ERROR:  PREPARE TRANSACTION is not yet supported in Cloudberry Database
+ERROR:  PREPARE TRANSACTION is not yet supported in Apache Cloudberry
 ROLLBACK;
 WARNING:  there is no transaction in progress
 -- ===================================================================