Merge pull request #6586 from EnterpriseDB/release/2025-03-05b

Release: 2025-03-05b

Author: gvasquezvargas

product_docs/docs/epas/13/epas_guide/14_edb_clone_schema.mdx

@@ -63,6 +63,7 @@ In addition, the following limitations apply:
 -   For remote cloning, if an object in the source schema is dependent upon an extension, then this extension must be created in the public schema of the remote database before invoking the remote cloning function.
 -   At most, 16 copy jobs can run in parallel to clone schemas, whereas each job can have at most 16 worker processes to copy table data in parallel.
 -   Queries being run by background workers cannot be cancelled.
+-   Non-blocking cloning functions such as `localcopyschema_nb` and `remotecopyschema_nb` must be performed by a superuser. Only blocking cloning functions like `localcopyschema` and `remotecopyschema` can be performed by a non-superuser. Although these functions don't enforce the superuser requirement, using them as a non-superuser can lead to unexpected behavior.
 
 The following section describes how to set up EDB Clone Schema on the databases.
 
@@ -190,7 +191,7 @@ This command also drops the `edb_cloneschema` extension.
 **Step 2:** Install the extensions using the following commands:
 
 ```text
-CREATE EXTENSION parallel_clone SCHEMA public;
+CREATE EXTENSION parallel_clone;
 
 CREATE EXTENSION edb_cloneschema;
 ```

product_docs/docs/epas/14/epas_guide/14_edb_clone_schema.mdx

@@ -66,6 +66,7 @@ The following limitations apply:
 -   For remote cloning, if an object in the source schema depends on an extension, then you must create this extension in the public schema of the remote database before invoking the remote cloning function.
 -   At most, 16 copy jobs can run in parallel to clone schemas. Each job can have at most 16 worker processes to copy table data in parallel.
 -   You can't cancel queries run by background workers.
+-   Non-blocking cloning functions such as `localcopyschema_nb` and `remotecopyschema_nb` must be performed by a superuser. Only blocking cloning functions like `localcopyschema` and `remotecopyschema` can be performed by a non-superuser. Although these functions don't enforce the superuser requirement, using them as a non-superuser can lead to unexpected behavior.
 
 ## Setup process
 
@@ -178,7 +179,7 @@ Install the EDB Clone Schema on any database to be used as the source or target
 
 
   ```text
-  CREATE EXTENSION parallel_clone SCHEMA public;
+  CREATE EXTENSION parallel_clone;
 
   CREATE EXTENSION edb_cloneschema;
   ```

product_docs/docs/epas/15/database_administration/14_edb_clone_schema/edb_clone_schema_overview.mdx

@@ -81,3 +81,4 @@ The following limitations apply:
 -   For remote cloning, if an object in the source schema depends on an extension, then you must create this extension in the public schema of the remote database before invoking the remote cloning function.
 -   At most, 16 copy jobs can run in parallel to clone schemas. Each job can have at most 16 worker processes to copy table data in parallel.
 -   You can't cancel queries run by background workers.
+-   Non-blocking cloning functions such as `localcopyschema_nb` and `remotecopyschema_nb` must be performed by a superuser. Only blocking cloning functions like `localcopyschema` and `remotecopyschema` can be performed by a non-superuser. Although these functions don't enforce the superuser requirement, using them as a non-superuser can lead to unexpected behavior.

product_docs/docs/epas/15/database_administration/14_edb_clone_schema/setting_up_edb_clone_schema.mdx

@@ -104,7 +104,7 @@ Install the EDB Clone Schema on any database to be used as the source or target
 1.  Install the extensions. Make sure that you create the `parallel_clone` extension before creating the `edb_cloneschema` extension.
 
   ```sql
-  CREATE EXTENSION parallel_clone SCHEMA public;
+  CREATE EXTENSION parallel_clone;
 
   CREATE EXTENSION edb_cloneschema;
   ```

product_docs/docs/epas/16/database_administration/14_edb_clone_schema/cloning_with_a_non_super_user.mdx

@@ -128,7 +128,8 @@ Create the following extensions:
 CREATE EXTENSION postgres_fdw;
 CREATE EXTENSION dblink;
 CREATE EXTENSION adminpack;
-CREATE EXTENSION pgAgent;
+CREATE EXTENSION edb_job_scheduler;
+CREATE EXTENSION dbms_job;
 CREATE EXTENSION parallel_clone;
 CREATE EXTENSION edb_cloneschema;
 __OUTPUT__
@@ -239,7 +240,8 @@ Create the following extensions:
 CREATE EXTENSION postgres_fdw;
 CREATE EXTENSION dblink;
 CREATE EXTENSION adminpack;
-CREATE EXTENSION pgAgent;
+CREATE EXTENSION edb_job_scheduler;
+CREATE EXTENSION dbms_job;
 CREATE EXTENSION parallel_clone;
 CREATE EXTENSION edb_cloneschema;
 __OUTPUT__

product_docs/docs/epas/16/database_administration/14_edb_clone_schema/edb_clone_schema_overview.mdx

@@ -18,6 +18,19 @@ Verify the following conditions before using an EDB Clone Schema function:
 -   When using the remote copy functions, if the `on_tblspace` parameter is set to `true`, then the target database cluster contains all tablespaces that are referenced by objects in the source schema. Otherwise, creating the DDL statements for those database objects fails in the target schema, which causes a failure of the cloning process.
 -   When using the remote copy functions, if you set the `copy_acls` parameter to `true`, then all roles that have `GRANT` privileges on objects in the source schema exist in the target database cluster. Otherwise granting privileges to those roles fails in the target schema, which causes a failure of the cloning process.
 -   pgAgent is running against the target database if you're using the non-blocking form of the function.
+-   Add the name of the database where you want to install or use the clone schema in the postgresql.conf file. For example, if you want to install or use the clone schema on the `edb` database, then add the following entry in the postgresql.conf file:
+    
+    ```
+    edb_job_scheduler.database_list='edb'
+    ```
+
+    Also, add `parallel_clone` and `edb_job_scheduler` to the shared libraries in the postgresql.conf file:
+
+    ```
+    shared_preload_libraries='....,$libdir/parallel_clone, $libdir/edb_job_scheduler'
+    ```
+    
+    Restart the database server to load the changes in postgresql.conf file.
 
 EDB Postgres Advanced Server includes pgAgent as a component. For information about pgAgent, see the [pgAdmin documentation](https://www.pgadmin.org/docs/pgadmin4/dev/pgagent.html).
 
@@ -81,3 +94,4 @@ The following limitations apply:
 -   For remote cloning, if an object in the source schema depends on an extension, then you must create this extension in the public schema of the remote database before invoking the remote cloning function.
 -   At most, 16 copy jobs can run in parallel to clone schemas. Each job can have at most 16 worker processes to copy table data in parallel.
 -   You can't cancel queries run by background workers.
+-   Non-blocking cloning functions such as `localcopyschema_nb` and `remotecopyschema_nb` must be performed by a superuser. Only blocking cloning functions like `localcopyschema` and `remotecopyschema` can be performed by a non-superuser. Although these functions don't enforce the superuser requirement, using them as a non-superuser can lead to unexpected behavior.

product_docs/docs/epas/16/database_administration/14_edb_clone_schema/setting_up_edb_clone_schema.mdx

@@ -9,28 +9,24 @@ In addition, it might help to modify some configuration parameters in the `postg
 
 ## Installing extensions
 
-Perform this installation on any database to be used as the source or target database by an EDB Clone Schema function.
+Install the following extensions on any database to be used as the source or target database by an EDB Clone Schema function: `postgres_fdw`, `dblink`, `edb_job_scheduler`, and `dbms_job`.
 
-1. Install the following extensions on the database: `postgres_fdw`, `dblink`, `adminpack` and `pgagent`.
-1. Ensure that pgAgent is installed before creating the `pgagent` extension. On Linux, you can use the `edb-as<xx>-pgagent` RPM package, where `<xx>` is the EDB Postgres Advanced Server version number to install pgAgent. On Windows, use StackBuilder Plus to download and install pgAgent.
-
-  Install the extensions:
-
-  ```sql
-  CREATE EXTENSION postgres_fdw SCHEMA public;
-  CREATE EXTENSION dblink SCHEMA public;
-  CREATE EXTENSION adminpack;
-  CREATE EXTENSION pgagent;
-  ```
+```sql
+CREATE EXTENSION postgres_fdw SCHEMA public;
+CREATE EXTENSION dblink SCHEMA public;
+CREATE EXTENSION adminpack;
+CREATE EXTENSION edb_job_scheduler;
+CREATE EXTENSION dbms_job;
+```
 
-  For more information about using the `CREATE EXTENSION` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createextension.html).
+For more information about using the `CREATE EXTENSION` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createextension.html).
 
 ## Modifying the configuration file
 
 Modify the `postgresql.conf` file by adding `$libdir/parallel_clone` to the `shared_preload_libraries` configuration parameter:
 
   ```ini
-  shared_preload_libraries = '$libdir/dbms_pipe,$libdir/dbms_aq,$libdir/parallel_clone'
+  shared_preload_libraries = '$libdir/dbms_pipe,$libdir/dbms_aq,$libdir/parallel_clone,$libdir/edb_job_scheduler'
   ```
 To load the libraries with clone schema support, restart the database server.
 
@@ -103,7 +99,7 @@ Install the EDB Clone Schema on any database to be used as the source or target
 1.  Install the extensions. Make sure that you create the `parallel_clone` extension before creating the `edb_cloneschema` extension.
 
   ```sql
-  CREATE EXTENSION parallel_clone SCHEMA public;
+  CREATE EXTENSION parallel_clone;
 
   CREATE EXTENSION edb_cloneschema;
   ```

product_docs/docs/epas/17/database_administration/14_edb_clone_schema/edb_clone_schema_overview.mdx

@@ -87,3 +87,4 @@ The following limitations apply:
 -   For remote cloning, if an object in the source schema depends on an extension, then you must create this extension in the public schema of the remote database before invoking the remote cloning function.
 -   At most, 16 copy jobs can run in parallel to clone schemas. Each job can have at most 16 worker processes to copy table data in parallel.
 -   You can't cancel queries run by background workers.
+-   Non-blocking cloning functions such as `localcopyschema_nb` and `remotecopyschema_nb` must be performed by a superuser. Only blocking cloning functions like `localcopyschema` and `remotecopyschema` can be performed by a non-superuser. Although these functions don't enforce the superuser requirement, using them as a non-superuser can lead to unexpected behavior.

product_docs/docs/epas/17/database_administration/14_edb_clone_schema/setting_up_edb_clone_schema.mdx

@@ -9,20 +9,16 @@ In addition, it might help to modify some configuration parameters in the `postg
 
 ## Installing extensions
 
-Perform this installation on any database to be used as the source or target database by an EDB Clone Schema function.
+Install the following extensions on any database to be used as the source or target database by an EDB Clone Schema function: `postgres_fdw`, `dblink`, `edb_job_scheduler`, and `dbms_job`.
 
-1. Install the following extensions on the database: `postgres_fdw`, `dblink`, `edb_job_scheduler`, and `DBMS_JOB`.
-
-  Install the extensions:
-
-  ```sql
-  CREATE EXTENSION postgres_fdw SCHEMA public;
-  CREATE EXTENSION dblink SCHEMA public;
-  CREATE EXTENSION edb_job_scheduler;
-  CREATE EXTENSION dbms_job;
-  ```
+```sql
+CREATE EXTENSION postgres_fdw SCHEMA public;
+CREATE EXTENSION dblink SCHEMA public;
+CREATE EXTENSION edb_job_scheduler;
+CREATE EXTENSION dbms_job;
+```
 
-  For more information about using the `CREATE EXTENSION` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createextension.html).
+For more information about using the `CREATE EXTENSION` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createextension.html).
 
 ## Modifying the configuration file
 
@@ -103,7 +99,7 @@ Install the EDB Clone Schema on any database to be used as the source or target
 1.  Install the extensions. Make sure that you create the `parallel_clone` extension before creating the `edb_cloneschema` extension.
 
   ```sql
-  CREATE EXTENSION parallel_clone SCHEMA public;
+  CREATE EXTENSION parallel_clone;
 
   CREATE EXTENSION edb_cloneschema;
   ```