Merge pull request #2696 from EnterpriseDB/release/2022-05-19

Release: 2022-05-19

product_docs/docs/bdr/4/index.mdx

@@ -26,7 +26,6 @@ navigation:
   - twophase
   - catalogs
   - functions
-  - known-issues
 title: BDR (Bi-Directional Replication)
 directoryDefaults:
   description: >-

product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/index.mdx

@@ -1,6 +1,8 @@
 ---
 title: "Checking your cloud readiness"
 indexCards: simple
+redirects:
+ - /biganimal/latest/getting_started/01_check_resource_limits/
 ---
 
 Each time you create a new cluster you must ensure the readiness of your cloud to work with BigAnimal.  

product_docs/docs/epas/10/epas_compat_sql/11a_alter_synonym.mdx

@@ -0,0 +1,65 @@
+---
+title: "ALTER SYNONYM"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.026.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.056.html"
+---
+
+## Name
+
+`ALTER SYNONYM` -- change ownership of synonym object 
+
+## Synopsis
+
+```text
+ALTER SYNONYM <syn_name> OWNER TO <new_owner>
+```
+
+## Description
+
+The `ALTER SYNONYM` command changes owner of the synonym. 
+
+
+## Examples
+
+```text
+-- create user t1 and t2
+edb=# create user t1;
+CREATE ROLE
+edb=# create user t2;
+CREATE ROLE
+
+-- grant all the privileges to user t1 and t2 on public schema
+edb=# GRANT ALL PRIVILEGES ON SCHEMA public TO GROUP t1;
+GRANT
+edb=# GRANT ALL PRIVILEGES ON SCHEMA public TO GROUP t2;
+GRANT
+
+-- connect to the database as user t1 and create the table
+edb=# \c - t1
+You are now connected to database "edb" as user "t1".
+edb=> create table t(n int); 
+CREATE TABLE
+
+-- create a synonym for table t
+edb=> create public synonym x for  t;
+CREATE SYNONYM
+
+-- check the owner of the synonym x is t1
+edb=# select * from all_synonyms;
+ owner | schema_name | objid | synonym_name | table_owner | table_schema_name | table_name | db_link 
+-------+-------------+-------+--------------+-------------+-------------------+------------+---------
+ T1    | PUBLIC      | 16390 | X            | T1          | PUBLIC            | T          | 
+
+-- connect the database as user edb and change the owner of the synonym x to user t2
+edb=> \c - edb
+You are now connected to database "edb" as user "edb".
+edb=# alter synonym x owner to t2;
+
+-- check the owner of the synonym x is changed to t2
+edb=# select * from all_synonyms;
+ owner | schema_name | objid | synonym_name | table_owner | table_schema_name | table_name | db_link 
+-------+-------------+-------+--------------+-------------+-------------------+------------+---------
+ T2    | PUBLIC      | 16390 | X            | T1          | PUBLIC            | T          |          
+```

product_docs/docs/epas/10/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx

@@ -1,16 +1,16 @@
 ---
 title: "Audit Logging Configuration Parameters"
-
 ---
 
-<div id="audit_logging_configuration_parameters" class="registered_link"></div>
-
 Use the following configuration parameters to control database auditing. See [Summary of Configuration Parameters](../01_configuration_parameters/02_summary_of_configuration_parameters/#summary_of_configuration_parameters) to determine if a change to the configuration parameter takes effect immediately, or if the configuration needs to be reloaded, or if the database server needs to be restarted.
 
 `edb_audit`
 
  Enables or disables database auditing. The values `xml` or `csv` will enable database auditing. These values represent the file format in which auditing information will be captured. `none` will disable database auditing and is also the default.
 
+!!! Note
+    The `logging_collector` parameter must be set to `on` to enable the `edb_audit` parameter.
+
 `edb_audit_directory`
 
  Specifies the directory where the log files will be created. The path of the directory can be relative or absolute to the data folder. The default is the `PGDATA/edb_audit` directory.

product_docs/docs/epas/11/epas_compat_sql/11a_alter_synonym.mdx

@@ -0,0 +1,65 @@
+---
+title: "ALTER SYNONYM"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.026.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.056.html"
+---
+
+## Name
+
+`ALTER SYNONYM` -- change ownership of synonym object 
+
+## Synopsis
+
+```text
+ALTER SYNONYM <syn_name> OWNER TO <new_owner>
+```
+
+## Description
+
+The `ALTER SYNONYM` command changes owner of the synonym. 
+
+
+## Examples
+
+```text
+-- create user t1 and t2
+edb=# create user t1;
+CREATE ROLE
+edb=# create user t2;
+CREATE ROLE
+
+-- grant all the privileges to user t1 and t2 on public schema
+edb=# GRANT ALL PRIVILEGES ON SCHEMA public TO GROUP t1;
+GRANT
+edb=# GRANT ALL PRIVILEGES ON SCHEMA public TO GROUP t2;
+GRANT
+
+-- connect to the database as user t1 and create the table
+edb=# \c - t1
+You are now connected to database "edb" as user "t1".
+edb=> create table t(n int); 
+CREATE TABLE
+
+-- create a synonym for table t
+edb=> create public synonym x for  t;
+CREATE SYNONYM
+
+-- check the owner of the synonym x is t1
+edb=# select * from all_synonyms;
+ owner | schema_name | objid | synonym_name | table_owner | table_schema_name | table_name | db_link 
+-------+-------------+-------+--------------+-------------+-------------------+------------+---------
+ T1    | PUBLIC      | 16390 | X            | T1          | PUBLIC            | T          | 
+
+-- connect the database as user edb and change the owner of the synonym x to user t2
+edb=> \c - edb
+You are now connected to database "edb" as user "edb".
+edb=# alter synonym x owner to t2;
+
+-- check the owner of the synonym x is changed to t2
+edb=# select * from all_synonyms;
+ owner | schema_name | objid | synonym_name | table_owner | table_schema_name | table_name | db_link 
+-------+-------------+-------+--------------+-------------+-------------------+------------+---------
+ T2    | PUBLIC      | 16390 | X            | T1          | PUBLIC            | T          |          
+```

product_docs/docs/epas/11/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx

@@ -3,14 +3,15 @@ title: "Audit Logging Configuration Parameters"
 
 ---
 
-<div id="audit_logging_configuration_parameters" class="registered_link"></div>
-
 Use the following configuration parameters to control database auditing. See [Summary of Configuration Parameters](../01_configuration_parameters/02_summary_of_configuration_parameters/#summary_of_configuration_parameters) to determine if a change to the configuration parameter takes effect immediately, or if the configuration needs to be reloaded, or if the database server needs to be restarted.
 
 `edb_audit`
 
  Enables or disables database auditing. The values `xml` or `csv` will enable database auditing. These values represent the file format in which auditing information will be captured. `none` will disable database auditing and is also the default.
 
+!!! Note
+    The `logging_collector` parameter must be set to `on` to enable the `edb_audit` parameter.
+
 `edb_audit_directory`
 
  Specifies the directory where the log files will be created. The path of the directory can be relative or absolute to the data folder. The default is the `PGDATA/edb_audit` directory.

product_docs/docs/epas/12/epas_compat_sql/11a_alter_synonym.mdx

@@ -0,0 +1,65 @@
+---
+title: "ALTER SYNONYM"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.026.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.056.html"
+---
+
+## Name
+
+`ALTER SYNONYM` -- change ownership of synonym object 
+
+## Synopsis
+
+```text
+ALTER SYNONYM <syn_name> OWNER TO <new_owner>
+```
+
+## Description
+
+The `ALTER SYNONYM` command changes owner of the synonym. 
+
+
+## Examples
+
+```text
+-- create user t1 and t2
+edb=# create user t1;
+CREATE ROLE
+edb=# create user t2;
+CREATE ROLE
+
+-- grant all the privileges to user t1 and t2 on public schema
+edb=# GRANT ALL PRIVILEGES ON SCHEMA public TO GROUP t1;
+GRANT
+edb=# GRANT ALL PRIVILEGES ON SCHEMA public TO GROUP t2;
+GRANT
+
+-- connect to the database as user t1 and create the table
+edb=# \c - t1
+You are now connected to database "edb" as user "t1".
+edb=> create table t(n int); 
+CREATE TABLE
+
+-- create a synonym for table t
+edb=> create public synonym x for  t;
+CREATE SYNONYM
+
+-- check the owner of the synonym x is t1
+edb=# select * from all_synonyms;
+ owner | schema_name | objid | synonym_name | table_owner | table_schema_name | table_name | db_link 
+-------+-------------+-------+--------------+-------------+-------------------+------------+---------
+ T1    | PUBLIC      | 16390 | X            | T1          | PUBLIC            | T          | 
+
+-- connect the database as user edb and change the owner of the synonym x to user t2
+edb=> \c - edb
+You are now connected to database "edb" as user "edb".
+edb=# alter synonym x owner to t2;
+
+-- check the owner of the synonym x is changed to t2
+edb=# select * from all_synonyms;
+ owner | schema_name | objid | synonym_name | table_owner | table_schema_name | table_name | db_link 
+-------+-------------+-------+--------------+-------------+-------------------+------------+---------
+ T2    | PUBLIC      | 16390 | X            | T1          | PUBLIC            | T          |          
+```

product_docs/docs/epas/12/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx

@@ -3,14 +3,15 @@ title: "Audit Logging Configuration Parameters"
 
 ---
 
-<div id="audit_logging_configuration_parameters" class="registered_link"></div>
-
 Use the following configuration parameters to control database auditing. See [Summary of Configuration Parameters](../01_configuration_parameters/02_summary_of_configuration_parameters/#summary_of_configuration_parameters) to determine if a change to the configuration parameter takes effect immediately, or if the configuration needs to be reloaded, or if the database server needs to be restarted.
 
 `edb_audit`
 
  Enables or disables database auditing. The values `xml` or `csv` will enable database auditing. These values represent the file format in which auditing information will be captured. `none` will disable database auditing and is also the default.
 
+!!! Note
+    The `logging_collector` parameter must be set to `on` to enable the `edb_audit` parameter.
+
 `edb_audit_directory`
 
  Specifies the directory where the log files will be created. The path of the directory can be relative or absolute to the data folder. The default is the `PGDATA/edb_audit` directory.

product_docs/docs/epas/13/epas_compat_sql/11a_alter_synonym.mdx

@@ -0,0 +1,65 @@
+---
+title: "ALTER SYNONYM"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.026.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.056.html"
+---
+
+## Name
+
+`ALTER SYNONYM` -- change ownership of synonym object 
+
+## Synopsis
+
+```text
+ALTER SYNONYM <syn_name> OWNER TO <new_owner>
+```
+
+## Description
+
+The `ALTER SYNONYM` command changes owner of the synonym. 
+
+
+## Examples
+
+```text
+-- create user t1 and t2
+edb=# create user t1;
+CREATE ROLE
+edb=# create user t2;
+CREATE ROLE
+
+-- grant all the privileges to user t1 and t2 on public schema
+edb=# GRANT ALL PRIVILEGES ON SCHEMA public TO GROUP t1;
+GRANT
+edb=# GRANT ALL PRIVILEGES ON SCHEMA public TO GROUP t2;
+GRANT
+
+-- connect to the database as user t1 and create the table
+edb=# \c - t1
+You are now connected to database "edb" as user "t1".
+edb=> create table t(n int); 
+CREATE TABLE
+
+-- create a synonym for table t
+edb=> create public synonym x for  t;
+CREATE SYNONYM
+
+-- check the owner of the synonym x is t1
+edb=# select * from all_synonyms;
+ owner | schema_name | objid | synonym_name | table_owner | table_schema_name | table_name | db_link 
+-------+-------------+-------+--------------+-------------+-------------------+------------+---------
+ T1    | PUBLIC      | 16390 | X            | T1          | PUBLIC            | T          | 
+
+-- connect the database as user edb and change the owner of the synonym x to user t2
+edb=> \c - edb
+You are now connected to database "edb" as user "edb".
+edb=# alter synonym x owner to t2;
+
+-- check the owner of the synonym x is changed to t2
+edb=# select * from all_synonyms;
+ owner | schema_name | objid | synonym_name | table_owner | table_schema_name | table_name | db_link 
+-------+-------------+-------+--------------+-------------+-------------------+------------+---------
+ T2    | PUBLIC      | 16390 | X            | T1          | PUBLIC            | T          |          
+```

product_docs/docs/epas/13/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx

@@ -6,14 +6,16 @@ legacyRedirectsGenerated:
   - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/13/audit_logging_configuration_parameters.html"
 ---
 
-<div id="audit_logging_configuration_parameters" class="registered_link"></div>
 
 Use the following configuration parameters to control database auditing. See [Summary of Configuration Parameters](../01_configuration_parameters/02_summary_of_configuration_parameters/#summary_of_configuration_parameters) to determine if a change to the configuration parameter takes effect immediately, or if the configuration needs to be reloaded, or if the database server needs to be restarted.
 
 `edb_audit`
 
  Enables or disables database auditing. The values `xml` or `csv` will enable database auditing. These values represent the file format in which auditing information will be captured. `none` will disable database auditing and is also the default.
 
+!!! Note
+    The `logging_collector` parameter must be set to `on` to enable the `edb_audit` parameter.
+
 `edb_audit_directory`
 
  Specifies the directory where the log files will be created. The path of the directory can be relative or absolute to the data folder. The default is the `PGDATA/edb_audit` directory.