From b278fb3cd4243ef35ee5cac4505b3822c0d6f2bd Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 10 Aug 2023 17:16:05 -0400 Subject: [PATCH 001/223] Edits to PR4538 First pass --- .../01_setting_new_parameters.mdx | 16 ++++---- .../01_configuration_parameters/index.mdx | 2 +- .../02_edb_loader/data_loading_methods.mdx | 6 +-- .../edb_loader_overview_and_restrictions.mdx | 4 +- .../running_edb_loader.mdx | 39 +++++++++++-------- .../dirty_buffer_throttling.mdx | 4 +- .../copying_a_remote_schema.mdx | 2 +- .../setting_up_edb_clone_schema.mdx | 4 +- 8 files changed, 42 insertions(+), 35 deletions(-) diff --git a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx index b8ce0d69c9d..4a30417ed58 100644 --- a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx +++ b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx @@ -14,7 +14,7 @@ redirects: -Set each configuration parameter using a name/value pair. Parameter names are not case sensitive. The parameter name is typically separated from its value by an optional equals sign (`=`). +Set each configuration parameter using a name/value pair. Parameter names aren't case sensitive. The parameter name is typically separated from its value by an optional equals sign (`=`). This example shows some configuration parameter settings in the `postgresql.conf` file: @@ -56,19 +56,19 @@ The multiplier for memory units is 1024. A number of parameter settings are set when the EDB Postgres Advanced Server database product is built. These are read-only parameters, and you can't change their values. A couple of parameters are also permanently set for each database when the database is created. These parameters are read-only and you can't later change them for the database. However, there are a number of ways to specify the configuration parameter settings: -- The initial settings for almost all configurable parameters across the entire database cluster are listed **in the `postgresql.conf`** configuration file. These settings are put into effect upon database server start or restart. You can override some of these initial parameter settings. All configuration parameters have built-in default settings that are in effect unless they are explicitly overridden. +- The initial settings for almost all configurable parameters across the entire database cluster are listed in the `postgresql.conf` configuration file. These settings are put into effect upon database server start or restart. You can override some of these initial parameter settings. All configuration parameters have built-in default settings that are in effect unless they're explicitly overridden. -- Configuration parameters in the `postgresql.conf` file are overridden when the same parameters are included **in the `postgresql.auto.conf` file**. The `ALTER SYSTEM` command is used to manage the configuration parameters in the `postgresql.auto.conf` file. +- Configuration parameters in the `postgresql.conf` file are overridden when the same parameters are included in the `postgresql.auto.conf` file. The `ALTER SYSTEM` command is used to manage the configuration parameters in the `postgresql.auto.conf` file. -- You can modify parameter settings **in the configuration file while the database server is running**. If the configuration file is then reloaded (meaning a SIGHUP signal is issued), for certain parameter types, the changed parameters settings immediately take effect. For some of these parameter types, the new settings are available in a currently running session immediately after the reload. For other of these parameter types, you must start a new session to use the new settings. And yet for other parameter types, modified settings don't take effect until the database server is stopped and restarted. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/config-setting.html) for information on how to reload the configuration file: +- You can modify parameter settings in the configuration file while the database server is running. If the configuration file is then reloaded (meaning a SIGHUP signal is issued), for certain parameter types, the changed parameters settings immediately take effect. For some of these parameter types, the new settings are available in a currently running session immediately after the reload. For others, you must start a new session to use the new settings. And for some others, modified settings don't take effect until the database server is stopped and restarted. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/config-setting.html) for information on how to reload the configuration file. -- You can **use the SQL commands** `ALTER DATABASE`, `ALTER ROLE`, or `ALTER ROLE IN DATABASE` to modify certain parameter settings. The modified parameter settings take effect for new sessions after you execute the command. `ALTER DATABASE` affects new sessions connecting to the specified database. `ALTER ROLE` affects new sessions started by the specified role. `ALTER ROLE IN DATABASE` affects new sessions started by the specified role connecting to the specified database. Parameter settings established by these SQL commands remain in effect indefinitely, across database server restarts, overriding settings established by the other methods. Parameter settings established using the `ALTER DATABASE`, `ALTER ROLE`, or `ALTER ROLE IN DATABASE` commands can be changed only by either: +- You can use the SQL commands `ALTER DATABASE`, `ALTER ROLE`, or `ALTER ROLE IN DATABASE` to modify certain parameter settings. The modified parameter settings take effect for new sessions after you execute the command. `ALTER DATABASE` affects new sessions connecting to the specified database. `ALTER ROLE` affects new sessions started by the specified role. `ALTER ROLE IN DATABASE` affects new sessions started by the specified role connecting to the specified database. Parameter settings established by these SQL commands remain in effect indefinitely, across database server restarts, overriding settings established by the other methods. You can change parameter settings established using the `ALTER DATABASE`, `ALTER ROLE`, or `ALTER ROLE IN DATABASE` commands by either: - Reissuing these commands with a different parameter value. - - Issuing these commands using either of the `SET parameter TO DEFAULT` clause or the `RESET parameter` clause. These clauses change the parameter back to using the setting set by the other methods. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/sql-commands.html) for the exact syntax of these SQL commands. + - Issuing these commands using the `SET parameter TO DEFAULT` clause or the `RESET parameter` clause. These clauses change the parameter back to using the setting set by the other methods. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/sql-commands.html) for the exact syntax of these SQL commands. -- You can make changes for certain parameter settings for the duration of individual sessions **using the `PGOPTIONS` environment variable** or by **using the `SET` command in the EDB-PSQL or PSQL command-line programs**. Parameter settings made this way override settings established using any of the methods descussed earlier, but only during that session. +- You can make changes for certain parameter settings for the duration of individual sessions using the `PGOPTIONS` environment variable or by using the `SET` command in the EDB-PSQL or PSQL command-line programs. Parameter settings made this way override settings established using any of the methods descussed earlier, but only during that session. ## Modifying the postgresql.conf file @@ -88,7 +88,7 @@ SELECT name FROM pg_settings WHERE context = 'postmaster'; Appropriate authentication methods provide protection and security. Entries in the `pg_hba.conf` file specify the authentication methods that the server uses with connecting clients. Before connecting to the server, you might need to modify the authentication properties specified in the `pg_hba.conf` file. -When you invoke the `initdb` utility to create a cluster, the utility creates a `pg_hba.conf` file for that cluster that specifies the type of authentication required from connecting clients. You can modify this file. After modifying the authentication settings in the `pg_hba.conf` file, restart the server and apply the changes. For more information about authentication and modifying the `pg_hba.conf` file, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html). +When you invoke the initdb utility to create a cluster, the utility creates a `pg_hba.conf` file for that cluster that specifies the type of authentication required from connecting clients. You can modify this file. After modifying the authentication settings in the `pg_hba.conf` file, restart the server and apply the changes. For more information about authentication and modifying the `pg_hba.conf` file, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html). When the server receives a connection request, it verifies the credentials provided against the authentication settings in the `pg_hba.conf` file before allowing a connection to a database. To log the `pg_hba.conf` file entry to authenticate a connection to the server, set the `log_connections` parameter to `ON` in the `postgresql.conf` file. diff --git a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/index.mdx b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/index.mdx index 2b48a5f7eeb..fecb50262fa 100644 --- a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/index.mdx +++ b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/index.mdx @@ -14,7 +14,7 @@ redirects: The EDB Postgres Advanced Server configuration parameters control various aspects of the database server’s behavior and environment such as data file and log file locations, connection, authentication and security settings, resource allocation and consumption, archiving and replication settings, error logging and statistics gathering, optimization and performance tuning, and locale and formatting settings -Configuration parameters that apply only to EDB Postgres Advanced Server are noted in the [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/) topic, which lists all EDB Postgres Advanced Server configuration parameters along with a number of key attributes of the parameters. +Configuration parameters that apply only to EDB Postgres Advanced Server are noted in [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/), which lists all EDB Postgres Advanced Server configuration parameters along with a number of key attributes of the parameters. You can find more information about configuration parameters in the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/runtime-config.html). diff --git a/product_docs/docs/epas/15/database_administration/02_edb_loader/data_loading_methods.mdx b/product_docs/docs/epas/15/database_administration/02_edb_loader/data_loading_methods.mdx index d75c1ccd3ea..5bde3714902 100644 --- a/product_docs/docs/epas/15/database_administration/02_edb_loader/data_loading_methods.mdx +++ b/product_docs/docs/epas/15/database_administration/02_edb_loader/data_loading_methods.mdx @@ -6,11 +6,11 @@ description: "Description of the data loading methods supported by EDB*Loader" As with Oracle SQL\*Loader, EDB\*Loader supports three data loading methods: -- *Conventional path load* — Conventional path load is the default method used by EDB\*Loader. Use basic insert processing to add rows to the table. The advantage of a conventional path load is that table constraints and database objects defined on the table are enforced during a conventional path load. Table constraints and database objects include primary keys, not null constraints, check constraints, unique indexes, foreign key constraints, triggers, and so on. One exception is that the EDB Postgres Advanced Server rules defined on the table aren't enforced. EDB\*Loader can load tables on which rules are defined. However, the rules aren't executed. As a consequence, you can't load partitioned tables implemented using rules with EDB\*Loader. See [Conventional path load](invoking_edb_loader/conventional_path_load.mdx) +- **Conventional path load** — Conventional path load is the default method used by EDB\*Loader. Use basic insert processing to add rows to the table. The advantage of a conventional path load is that table constraints and database objects defined on the table are enforced during a conventional path load. Table constraints and database objects include primary keys, not null constraints, check constraints, unique indexes, foreign key constraints, triggers, and so on. One exception is that the EDB Postgres Advanced Server rules defined on the table aren't enforced. EDB\*Loader can load tables on which rules are defined. However, the rules aren't executed. As a consequence, you can't load partitioned tables implemented using rules with EDB\*Loader. See [Conventional path load](invoking_edb_loader/conventional_path_load.mdx). -- *Direct path load* — A direct path load is faster than a conventional path load but requires removing most types of constraints and triggers from the table. See [Direct path load](invoking_edb_loader/direct_path_load.mdx). +- **Direct path load** — A direct path load is faster than a conventional path load but requires removing most types of constraints and triggers from the table. See [Direct path load](invoking_edb_loader/direct_path_load.mdx). -- *Parallel direct path load* — A parallel direct path load provides even greater performance improvement by permitting multiple EDB\*Loader sessions to run simultaneously to load a single table. See [Parallel direct path load](invoking_edb_loader/parallel_direct_path_load.mdx). +- **Parallel direct path load** — A parallel direct path load provides even greater performance improvement by permitting multiple EDB\*Loader sessions to run simultaneously to load a single table. See [Parallel direct path load](invoking_edb_loader/parallel_direct_path_load.mdx). !!! Note Create EDB Postgres Advanced Server rules using the `CREATE RULE` command. EDB Postgres Advanced Server rules aren't the same database objects as rules and rule sets used in Oracle. diff --git a/product_docs/docs/epas/15/database_administration/02_edb_loader/edb_loader_overview_and_restrictions.mdx b/product_docs/docs/epas/15/database_administration/02_edb_loader/edb_loader_overview_and_restrictions.mdx index 9e87a46566c..bbd6d241e79 100644 --- a/product_docs/docs/epas/15/database_administration/02_edb_loader/edb_loader_overview_and_restrictions.mdx +++ b/product_docs/docs/epas/15/database_administration/02_edb_loader/edb_loader_overview_and_restrictions.mdx @@ -21,9 +21,9 @@ EDB\*Loader features include: The important version compatibility restrictions between the EDB\*Loader client and the database server are: -- When you invoke the EDB\*Loader program (called `edbldr`), you pass in parameters and directive information to the database server. We strongly recommend that you use the version 14 EDB\*Loader client (the edbldr program supplied with EDB Postgres Advanced Server 14) to load data only into version 14 of the database server. In general, use the same version for the EDB\*Loader client and database server. +- When you invoke the EDB\*Loader program (called `edbldr`), you pass in parameters and directive information to the database server. We strongly recommend that you use the version 14 EDB\*Loader client (the `edbldr` program supplied with EDB Postgres Advanced Server 14) to load data only into version 14 of the database server. In general, use the same version for the EDB\*Loader client and database server. -- Using EDB\*Loader with connection poolers such as PgPool-II and PgBouncer isn't supported. EDB\*Loader must connect directly to EDB Postgres Advanced Server version 14. Alternatively, there are commands you can use for loading data through connection poolers: +- Using EDB\*Loader with connection poolers such as PgPool-II and PgBouncer isn't supported. EDB\*Loader must connect directly to EDB Postgres Advanced Server version 14. Alternatively, you can use these commands for loading data through connection poolers: ```shell psql \copy diff --git a/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx b/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx index ab018dcd42a..49a929473f1 100644 --- a/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx +++ b/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx @@ -33,13 +33,20 @@ You can specify parameters listed in the syntax diagram in a *parameter file*. E You can include the full directory path or a relative directory path to the file name when specifying `control_file`, `data_file`, `bad_file`, `discard_file`, `log_file`, and `param_file`. If you specify the file name alone or with a relative directory path, the file is assumed to exist in the case of `control_file`, `data_file`, or `param_file` relative to the current working directory from which `edbldr` is invoked. In the case of `bad_file`, `discard_file`, or `log_file`, the file is created. -If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults for the database, port, and host are determined by the same rules as other EDB Postgres Advanced Server (EPAS) utility programs, such as `edb-psql`. +If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults for the database, port, and host are determined by the same rules as other EDB Postgres Advanced Server utility programs, such as edb-psql. ## Requirements - The control file must exist in the character set encoding of the client where `edbldr` is invoked. If the client is in an encoding different from the database encoding, then you must set the `PGCLIENTENCODING` environment variable on the client to the client’s encoding prior to invoking `edbldr`. This technique ensures character set conversion between the client and the database server is done correctly. -- The file names for `control_file`, `data_file`, `bad_file`, `discard_file`, and `log_file` must include the extensions `.ctl`, `.dat`, `.bad`, `.dsc`, and `.log`, respectively. If the provided file name doesn't contain an extension, EDB\*Loader assumes the actual file name includes the appropriate extension. +- The file names must include these extensions: + - `control_file` must use the `.ctl` extension. + - `data_file` must use the `.dat` extension. + - `bad_file` must use the `.bad` extension + - `discard_file` must use the `.dsc` extension + - `log_file` must include the `.log` extension + + If the provided file name doesn't have an extension, EDB\*Loader assumes the actual file name includes the appropriate extension. - The operating system account used to invoke `edbldr` must have read permission on the directories and files specified by `control_file`, `data_file`, and `param_file`. @@ -59,18 +66,18 @@ If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults f IP address of the host on which the database server is running. -`USERID={ username/password | username/ | username | / }` +`USERID={ | | | / }` - EDB\*Loader connects to the database with `username`. `username` must be a superuser or a username with the required privileges. `password` is the password for `username`. + EDB\*Loader connects to the database with ``. `` must be a superuser or a username with the required privileges. `` is the password for ``. If you omit the `USERID` parameter, EDB\*Loader prompts for `username` and `password`. If you specify `USERID=username/`, then EDB\*Loader either: - - Uses the password file specified by environment variable `PGPASSFILE` if `PGPASSFILE` is set + - Uses the password file specified by the environment variable `PGPASSFILE` if `PGPASSFILE` is set - Uses the `.pgpass` password file (`pgpass.conf` on Windows systems) if `PGPASSFILE` isn't set If you specify `USERID=username`, then EDB\*Loader prompts for `password`. If you specify `USERID=/`, the connection is attempted using the operating system account as the user name. !!! Note - EDB\*Loader ignores the EPAS connection environment variables `PGUSER` and `PGPASSWORD`. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/libpq-pgpass.html) for information on the `PGPASSFILE` environment variable and the password file. + EDB\*Loader ignores the EDB Postgres Advanced Server connection environment variables `PGUSER` and `PGPASSWORD`. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/libpq-pgpass.html) for information on the `PGPASSFILE` environment variable and the password file. `-c CONNECTION_STRING` @@ -92,13 +99,13 @@ If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults f `BAD=bad_file` - `bad_file` specifies the name of a file that receives input data records that can't be loaded due to errors. Specifying a `bad_file` on the command line overrides any `BADFILE` clause specified in the control file. + `bad_file` specifies the name of a file that receives input data records that can't be loaded due to errors. Specifying `bad_file` on the command line overrides any `BADFILE` clause specified in the control file. For more information about `bad_file`, see [Building the EDB\*Loader control file](../building_the_control_file/). `DISCARD=discard_file` - `discard_file` is the name of the file that receives input data records that don't meet any table’s selection criteria. Specifying a `discard_file` on the command line overrides the `DISCARDFILE` clause in the control file. + `discard_file` is the name of the file that receives input data records that don't meet any table’s selection criteria. Specifying `discard_file` on the command line overrides the `DISCARDFILE` clause in the control file. For more information about `discard_file`, see [Building the EDB\*Loader control file](../building_the_control_file/). @@ -131,7 +138,7 @@ If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults f `DIRECT= { FALSE | TRUE }` - If `DIRECT` is set to `TRUE` EDB\*Loader performs a direct path load instead of a conventional path load. The default value of `DIRECT` is `FALSE`. + If `DIRECT` is set to `TRUE`, EDB\*Loader performs a direct path load instead of a conventional path load. The default value of `DIRECT` is `FALSE`. Don't set `DIRECT=true` when loading the data into a replicated table. If you're using EDB\*Loader to load data into a replicated table and set `DIRECT=true`, indexes might omit rows that are in a table or might contain references to rows that were deleted. EnterpriseDB doesn't support direct inserts to load data into replicated tables. @@ -139,7 +146,7 @@ If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults f `FREEZE= { FALSE | TRUE }` - Set `FREEZE` to `TRUE` to copy the data with the rows `frozen`. A tuple guaranteed to be visible to all current and future transactions is marked as frozen to prevent transaction ID wraparound. For more information about frozen tuples, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/routine-vacuuming.html). + Set `FREEZE` to `TRUE` to copy the data with the rows *frozen*. A tuple guaranteed to be visible to all current and future transactions is marked as frozen to prevent transaction ID wraparound. For more information about frozen tuples, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/routine-vacuuming.html). You must specify a data-loading type of `TRUNCATE` in the control file when using the `FREEZE` option. `FREEZE` isn't supported for direct loading. @@ -191,7 +198,7 @@ EDB*Loader: Copyright (c) 2007-2021, EnterpriseDB Corporation. Successfully loaded (4) records ``` -In this example, EDB\*Loader prompts for the user name and password since they are omitted from the command line. In addition, the files for the bad file and log file are specified with the `BAD` and `LOG` command line parameters. +In this example, EDB\*Loader prompts for the user name and password since they're omitted from the command line. In addition, the files for the bad file and log file are specified with the `BAD` and `LOG` command line parameters. ```shell $ /usr/edb/as14/bin/edbldr -d edb CONTROL=emp.ctl BAD=/tmp/emp.bad @@ -234,7 +241,7 @@ EDB*Loader: Copyright (c) 2007-2021, EnterpriseDB Corporation. Successfully loaded (4) records ``` -This example invokes EDB\*Loader using a normal user. For this example, one empty table `bar` is created and a normal user `bob` is created. The `bob` user is granted all privileges on the table `bar`. The CREATE TABLE command creates the empty table. The CREATE USER command creates the user and the GRANT command gives required privileges to the user `bob` on the `bar` table: +This example invokes EDB\*Loader using a normal user. For this example, one empty table `bar` is created and a normal user `bob` is created. The `bob` user is granted all privileges on the table `bar`. The CREATE TABLE command creates the empty table. The CREATE USER command creates the user, and the GRANT command gives required privileges to the user `bob` on the `bar` table: ```sql CREATE TABLE bar(i int); @@ -278,8 +285,8 @@ When EDB\*Loader exits, it returns one of the following codes: | Exit code | Description | | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `0` | Indicates that all rows loaded successfully. | -| `1` | Indicates that EDB\*Loader encountered command line or syntax errors or aborted the load operation due to an unrecoverable error. | -| `2` | Indicates that the load completed, but some (or all) rows were rejected or discarded. | -| `3` | Indicates that EDB\*Loader encountered fatal errors (such as OS errors). This class of errors is equivalent to the `FATAL` or `PANIC` severity levels of PostgreSQL errors. | +| `0` | All rows loaded successfully. | +| `1` | EDB\*Loader encountered command line or syntax errors or aborted the load operation due to an unrecoverable error. | +| `2` | The load completed, but some (or all) rows were rejected or discarded. | +| `3` | EDB\*Loader encountered fatal errors (such as OS errors). This class of errors is equivalent to the `FATAL` or `PANIC` severity levels of PostgreSQL errors. | diff --git a/product_docs/docs/epas/15/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx b/product_docs/docs/epas/15/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx index b76c12a008a..401da0a3db5 100644 --- a/product_docs/docs/epas/15/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx +++ b/product_docs/docs/epas/15/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx @@ -107,7 +107,7 @@ edb=# INSERT INTO t1 VALUES (generate_series (1,10000), 'aaa'); INSERT 0 10000 ``` -The following example shows the results from the `INSERT` command: +This example shows the results from the `INSERT` command: ```sql edb=# SELECT query, rows, total_time, shared_blks_dirtied FROM @@ -152,7 +152,7 @@ edb=# INSERT INTO t1 VALUES (generate_series (1,10000), 'aaa'); INSERT 0 10000 ``` -The following example shows the results from the `INSERT` command without the use of a resource group: +This example shows the results from the `INSERT` command without the use of a resource group: ```sql edb=# SELECT query, rows, total_time, shared_blks_dirtied FROM diff --git a/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx b/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx index 80ee0ea6a19..0ada4c31486 100644 --- a/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx +++ b/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx @@ -110,7 +110,7 @@ __OUTPUT__ (1 row) ``` -The following example displays the status from the log file during various points in the cloning process: +This example displays the status from the log file during various points in the cloning process: ```sql tgtdb=# SELECT edb_util.process_status_from_log('clone_rmt_src_tgt'); diff --git a/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/setting_up_edb_clone_schema.mdx b/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/setting_up_edb_clone_schema.mdx index adaf5809c41..fcaf094944f 100644 --- a/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/setting_up_edb_clone_schema.mdx +++ b/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/setting_up_edb_clone_schema.mdx @@ -150,7 +150,7 @@ CREATE USER MAPPING FOR enterprisedb SERVER local_server For more information about using the `CREATE USER MAPPING` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/sql-createusermapping.html). -These `psql` commands show the foreign server and user mapping: +These psql commands show the foreign server and user mapping: ```sql edb=# \des+ @@ -235,7 +235,7 @@ CREATE USER MAPPING FOR enterprisedb SERVER src_server ``` ## Displaying foreign servers and user mappings -These `psql` commands show the foreign servers and user mappings: +These psql commands show the foreign servers and user mappings: ```sql tgtdb=# \des+ From 356ebc9b9f02fa05c25aee78a6cb6be9f7423366 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 15 Aug 2023 11:08:28 -0400 Subject: [PATCH 002/223] more edits --- .../01_setting_new_parameters.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx index 4a30417ed58..46cb2bbb96d 100644 --- a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx +++ b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx @@ -56,9 +56,9 @@ The multiplier for memory units is 1024. A number of parameter settings are set when the EDB Postgres Advanced Server database product is built. These are read-only parameters, and you can't change their values. A couple of parameters are also permanently set for each database when the database is created. These parameters are read-only and you can't later change them for the database. However, there are a number of ways to specify the configuration parameter settings: -- The initial settings for almost all configurable parameters across the entire database cluster are listed in the `postgresql.conf` configuration file. These settings are put into effect upon database server start or restart. You can override some of these initial parameter settings. All configuration parameters have built-in default settings that are in effect unless they're explicitly overridden. +- The initial settings for almost all configurable parameters across the entire database cluster are listed in the `postgresql.conf` configuration file. These settings are put into effect upon database server start or restart. You can override some of these initial parameter settings. All configuration parameters have built-in default settings that are in effect unless you explicitly override them. -- Configuration parameters in the `postgresql.conf` file are overridden when the same parameters are included in the `postgresql.auto.conf` file. The `ALTER SYSTEM` command is used to manage the configuration parameters in the `postgresql.auto.conf` file. +- Configuration parameters in the `postgresql.conf` file are overridden when the same parameters are included in the `postgresql.auto.conf` file. Use the `ALTER SYSTEM` command to manage the configuration parameters in the `postgresql.auto.conf` file. - You can modify parameter settings in the configuration file while the database server is running. If the configuration file is then reloaded (meaning a SIGHUP signal is issued), for certain parameter types, the changed parameters settings immediately take effect. For some of these parameter types, the new settings are available in a currently running session immediately after the reload. For others, you must start a new session to use the new settings. And for some others, modified settings don't take effect until the database server is stopped and restarted. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/config-setting.html) for information on how to reload the configuration file. @@ -66,7 +66,7 @@ A number of parameter settings are set when the EDB Postgres Advanced Server dat - Reissuing these commands with a different parameter value. - - Issuing these commands using the `SET parameter TO DEFAULT` clause or the `RESET parameter` clause. These clauses change the parameter back to using the setting set by the other methods. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/sql-commands.html) for the exact syntax of these SQL commands. + - Issuing these commands using the `SET parameter TO DEFAULT` clause or the `RESET parameter` clause. These clauses change the parameter back to using the setting set by the other methods. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/sql-commands.html) for the syntax of these SQL commands. - You can make changes for certain parameter settings for the duration of individual sessions using the `PGOPTIONS` environment variable or by using the `SET` command in the EDB-PSQL or PSQL command-line programs. Parameter settings made this way override settings established using any of the methods descussed earlier, but only during that session. @@ -76,7 +76,7 @@ The configuration parameters in the `postgresql.conf` file specify server behavi Parameters that are preceded by a pound sign (#) are set to their default value. To change a parameter value, remove the pound sign and enter a new value. After setting or changing a parameter, you must either `reload` or `restart` the server for the new parameter value to take effect. -In the `postgresql.conf` file, some parameters contain comments that indicate `change requires restart`. To view a list of the parameters that require a server restart, execute the following query at the psql command line: +In the `postgresql.conf` file, some parameters contain comments that indicate `change requires restart`. To view a list of the parameters that require a server restart, use the following query at the psql command line: ```sql SELECT name FROM pg_settings WHERE context = 'postmaster'; From e3e479cb05c63a272ab08c10e47f48cdc642bc5b Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 15 Aug 2023 13:22:46 -0400 Subject: [PATCH 003/223] revisions to database administration --- .../01_setting_new_parameters.mdx | 9 ++-- .../invoking_edb_loader/direct_path_load.mdx | 2 +- .../performing_remote_loading.mdx | 2 +- .../running_edb_loader.mdx | 26 +++++----- .../dirty_buffer_throttling.mdx | 52 +++++++++---------- .../copying_a_remote_schema.mdx | 2 +- 6 files changed, 45 insertions(+), 48 deletions(-) diff --git a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx index 46cb2bbb96d..9fa0068603b 100644 --- a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx +++ b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx @@ -106,9 +106,9 @@ application_name=psql ## Obfuscating the LDAP password -When using [LDAP](https://www.postgresql.org/docs/15/auth-ldap.html) for authentication, the LDAP password used to connect to the LDAP server, (the ldapbindpasswd password) is stored in the pg_hba.conf file. You can store the password there in an obfuscated form, which can then be de-obfuscated by a loadable module which you supply. The loadable module supplies a hook function that performs the de-obfuscation. +When using [LDAP](https://www.postgresql.org/docs/15/auth-ldap.html) for authentication, the LDAP password used to connect to the LDAP server (the ldapbindpasswd password) is stored in the `pg_hba.conf` file. You can store the password there in an obfuscated form, which can then be de-obfuscated by a loadable module that you supply. The loadable module supplies a hook function that performs the de-obfuscation. -For example, here is a C loadable module which uses `rot13_passphrase` as the hook function to de-obfuscate the password from the pg_hba.conf file: +For example, this C-loadable module uses `rot13_passphrase` as the hook function to de-obfuscate the password from the `pg_hba.conf` file: ```c #include "postgres.h" @@ -165,13 +165,10 @@ For example, here is a C loadable module which uses `rot13_passphrase` as the ho } ``` -Add your module to the `shared_preload_libraries` parameter in the postgresql.conf file. For example: +Add your module to the `shared_preload_libraries` parameter in the `postgresql.conf` file. For example: ```ini shared_preload_libraries = '$libdir/ldap_password_func' ``` Restart your server to load the changes in this parameter. - - - diff --git a/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx b/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx index 6a392190530..cd888b3589b 100644 --- a/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx +++ b/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx @@ -6,7 +6,7 @@ description: "Describes how to use EDB*Loader to write data directly to the data -During a direct path load, EDB\*Loader writes the data directly to the database pages, which is then synchronized to disk. The insert processing associated with a conventional path load is bypassed, resulting in a performance improvement. Bypassing insert processing reduces the types of constraints on the target table. The types of constraints permitted on the target table of a direct path load are: +During a direct path load, EDB\*Loader writes the data directly to the database pages, which is then synchronized to disk. The insert processing associated with a conventional path load is bypassed, resulting in performance improvement. Bypassing insert processing reduces the types of constraints on the target table. The types of constraints permitted on the target table of a direct path load are: - Primary key - Not null constraints diff --git a/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/performing_remote_loading.mdx b/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/performing_remote_loading.mdx index 6ed2b29ae07..0f11e8f7dfb 100644 --- a/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/performing_remote_loading.mdx +++ b/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/performing_remote_loading.mdx @@ -14,7 +14,7 @@ In addition, you can use the standard input feature to pipe the data from the da ## Requirements -Performing remote loading along with using standard input requires: +Performing remote loading using standard input requires: - The `edbldr` program must be installed on the client host on which to invoke it with the data source for the EDB\*Loader session. - The control file must contain the clause `INFILE 'stdin'` so you can pipe the data directly into EDB\*Loader’s standard input. For information on the `INFILE` clause and the EDB\*Loader control file, see [Building the EDB\*Loader control file](../building_the_control_file/). diff --git a/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx b/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx index 49a929473f1..cf95ea94d92 100644 --- a/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx +++ b/product_docs/docs/epas/15/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx @@ -29,15 +29,15 @@ edbldr [ -d ] [ -p ] [ -h ] ## Description -You can specify parameters listed in the syntax diagram in a *parameter file*. Exeptions include the `-d` option, `-p` option, `-h` option, and the `PARFILE` parameter. Specify the parameter file on the command line when you invoke `edbldr` using `PARFILE=param_file`. You can specify some parameters in the `OPTIONS` clause in the control file. For more information on the control file, see [Building the EDB\*Loader control file](../building_the_control_file/). +You can specify parameters listed in the syntax diagram in a *parameter file*. Exeptions include the `-d` option, `-p` option, `-h` option, and the `PARFILE` parameter. Specify the parameter file on the command line when you invoke edbldr using `PARFILE=param_file`. You can specify some parameters in the `OPTIONS` clause in the control file. For more information on the control file, see [Building the EDB\*Loader control file](../building_the_control_file/). -You can include the full directory path or a relative directory path to the file name when specifying `control_file`, `data_file`, `bad_file`, `discard_file`, `log_file`, and `param_file`. If you specify the file name alone or with a relative directory path, the file is assumed to exist in the case of `control_file`, `data_file`, or `param_file` relative to the current working directory from which `edbldr` is invoked. In the case of `bad_file`, `discard_file`, or `log_file`, the file is created. +You can include the full directory path or a relative directory path to the file name when specifying `control_file`, `data_file`, `bad_file`, `discard_file`, `log_file`, and `param_file`. If you specify the file name alone or with a relative directory path, the file is assumed to exist in the case of `control_file`, `data_file`, or `param_file` relative to the current working directory from which edbldr is invoked. In the case of `bad_file`, `discard_file`, or `log_file`, the file is created. If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults for the database, port, and host are determined by the same rules as other EDB Postgres Advanced Server utility programs, such as edb-psql. ## Requirements -- The control file must exist in the character set encoding of the client where `edbldr` is invoked. If the client is in an encoding different from the database encoding, then you must set the `PGCLIENTENCODING` environment variable on the client to the client’s encoding prior to invoking `edbldr`. This technique ensures character set conversion between the client and the database server is done correctly. +- The control file must exist in the character set encoding of the client where edbldr is invoked. If the client is in an encoding different from the database encoding, then you must set the `PGCLIENTENCODING` environment variable on the client to the client’s encoding prior to invoking edbldr. This technique ensures character set conversion between the client and the database server is done correctly. - The file names must include these extensions: - `control_file` must use the `.ctl` extension. @@ -48,9 +48,9 @@ If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults f If the provided file name doesn't have an extension, EDB\*Loader assumes the actual file name includes the appropriate extension. -- The operating system account used to invoke `edbldr` must have read permission on the directories and files specified by `control_file`, `data_file`, and `param_file`. +- The operating system account used to invoke edbldr must have read permission on the directories and files specified by `control_file`, `data_file`, and `param_file`. -- The operating system account `enterprisedb` must have write permission on the directories where `bad_file`, `discard_file`, and `log_file` are written. +- The operating system account enterprisedb must have write permission on the directories where `bad_file`, `discard_file`, and `log_file` are written. ## Parameters @@ -83,7 +83,7 @@ If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults f `connstr=CONNECTION_STRING` - The `-c` or `connstr=` option allows you to specify all the connection parameters supported by libpq. With this option, you can also specify SSL connection parameters or other connection parameters supported by libpq. If you provide connection options such as `-d`, `-h`, `-p` or `userid=dbuser/dbpass` separately, they might override the values provided by the `-c` or `connstr=` option. + The `-c` or `connstr=` option allows you to specify all the connection parameters supported by libpq. With this option, you can also specify SSL connection parameters or other connection parameters supported by libpq. If you provide connection options such as `-d`, `-h`, `-p`, or `userid=dbuser/dbpass` separately, they might override the values provided by the `-c` or `connstr=` option. `CONTROL=control_file` @@ -125,7 +125,7 @@ If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults f `log_file` specifies the name of the file in which EDB\*Loader records the results of the EDB\*Loader session. - If you omit the `LOG` parameter, EDB\*Loader creates a log file with the name `control_file_base.log` in the directory from which `edbldr` is invoked. `control_file_base` is the base name of the control file used in the EDB\*Loader session. The operating system account `enterprisedb` must have write permission on the directory where the log file is written. + If you omit the `LOG` parameter, EDB\*Loader creates a log file with the name `control_file_base.log` in the directory from which edbldr is invoked. `control_file_base` is the base name of the control file used in the EDB\*Loader session. The operating system account `enterprisedb` must have write permission on the directory where the log file is written. `PARFILE=param_file` @@ -134,7 +134,7 @@ If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults f Any parameter given in `param_file` overrides the same parameter supplied on the command line before the `PARFILE` option. Any parameter given on the command line that appears after the `PARFILE` option overrides the same parameter given in `param_file`. !!! Note - Unlike other EDB\*Loader files, there's no default file name or extension assumed for `param_file`. However, by Oracle SQL\*Loader convention, `.par` is typically used as an extension. It isn't required. + Unlike other EDB\*Loader files, there's no default file name or extension assumed for `param_file`. However, by Oracle SQL\*Loader convention, `.par` is typically used as an extension. It isn't required. `DIRECT= { FALSE | TRUE }` @@ -176,7 +176,7 @@ If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults f If set to `TRUE`, index maintenance isn't performed as part of a direct path load, and indexes on the loaded table are marked as invalid. The default value of `SKIP_INDEX_MAINTENANCE` is `FALSE`. - During a parallel direct path load, target table indexes aren't updated. They are marked as invalid after the load is complete. + During a parallel direct path load, target table indexes aren't updated. They're marked as invalid after the load is complete. You can use the `REINDEX` command to rebuild an index. For more information about the `REINDEX` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-reindex.htm). @@ -184,7 +184,7 @@ If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults f `group_name` specifies the name of an EDB Resource Manager resource group to which to assign the EDB\*Loader session. - Any default resource group that was assigned to the session is overridden by the resource group given by the `edb_resource_group` parameter specified on the `edbldr` command line. An example of such a group is a database user running the EDB\*Loader session who was assigned a default resource group with the `ALTER ROLE ... SET` `edb_resource_group` command. + Any default resource group that was assigned to the session is overridden by the resource group given by the `edb_resource_group` parameter specified on the edbldr command line. An example of such a group is a database user running the EDB\*Loader session who was assigned a default resource group with the `ALTER ROLE ... SET` `edb_resource_group` command. ## Examples @@ -268,7 +268,7 @@ EDBAS/ - (master) $ cat /tmp/edbldr.dat 5 ``` -Invoke EDB*Loader: +Invoke EDB\*Loader: ```shell EDBAS/ - (master) $ /usr/edb/as15/bin/edbldr -d edb userid=bob/123 control=/tmp/edbldr.ctl @@ -287,6 +287,6 @@ When EDB\*Loader exits, it returns one of the following codes: | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `0` | All rows loaded successfully. | | `1` | EDB\*Loader encountered command line or syntax errors or aborted the load operation due to an unrecoverable error. | -| `2` | The load completed, but some (or all) rows were rejected or discarded. | -| `3` | EDB\*Loader encountered fatal errors (such as OS errors). This class of errors is equivalent to the `FATAL` or `PANIC` severity levels of PostgreSQL errors. | +| `2` | The load completed, but some or all rows were rejected or discarded. | +| `3` | EDB\*Loader encountered fatal errors, such as OS errors. This class of errors is equivalent to the `FATAL` or `PANIC` severity levels of PostgreSQL errors. | diff --git a/product_docs/docs/epas/15/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx b/product_docs/docs/epas/15/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx index 401da0a3db5..5f6ad2cf0ee 100644 --- a/product_docs/docs/epas/15/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx +++ b/product_docs/docs/epas/15/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx @@ -122,9 +122,9 @@ __OUTPUT__ The actual dirty rate is calculated as follows: -- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 13496.184 ms, which yields *0.74117247 blocks per millisecond*. -- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields *741.17247 blocks per second*. -- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately *6072 kilobytes per second*. +- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 13496.184 ms, which yields 0.74117247 blocks per millisecond. +- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 741.17247 blocks per second. +- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 6072 kilobytes per second. The actual dirty rate of 6072 kilobytes per second is close to the dirty rate limit for the resource group, which is 6144 kilobytes per second. @@ -169,9 +169,9 @@ The total time was only 2432.165 milliseconds, compared to 13496.184 millisecond The actual dirty rate without the use of a resource group is calculated as follows: -- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 2432.165 ms, which yields *4.112797 blocks per millisecond*. -- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields *4112.797 blocks per second*. -- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately *33692 kilobytes per second*. +- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 2432.165 ms, which yields 4.112797 blocks per millisecond. +- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 4112.797 blocks per second. +- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 33692 kilobytes per second. The actual dirty rate of 33692 kilobytes per second is much higher than when the resource group with a dirty rate limit of 6144 kilobytes per second was used. @@ -229,7 +229,7 @@ INSERT 0 10000 !!! Note The `INSERT` commands in session 1 and session 2 started after the `SELECT pg_stat_statements_reset()` command in session 2 ran. -The following example shows the results from the `INSERT` commands in the two sessions. `RECORD 3` shows the results from session 1. `RECORD 2` shows the results from session 2. +This example shows the results from the `INSERT` commands in the two sessions. `RECORD 3` shows the results from session 1. `RECORD 2` shows the results from session 2. ```sql edb=# SELECT query, rows, total_time, shared_blks_dirtied FROM @@ -256,15 +256,15 @@ The total time was 33215.334 milliseconds for session 1 and 30591.551 millisecon The actual dirty rate for session 1 is calculated as follows: -- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 33215.334 ms, which yields *0.30115609 blocks per millisecond*. -- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields *301.15609 blocks per second*. -- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately *2467 kilobytes per second*. +- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 33215.334 ms, which yields 0.30115609 blocks per millisecond. +- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 301.15609 blocks per second. +- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 2467 kilobytes per second. The actual dirty rate for session 2 is calculated as follows: -- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 30591.551 ms, which yields *0.32698571 blocks per millisecond*. -- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields *326.98571 blocks per second*. -- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately *2679 kilobytes per second*. +- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 30591.551 ms, which yields 0.32698571 blocks per millisecond. +- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 326.98571 blocks per second. +- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 2679 kilobytes per second. The combined dirty rate from session 1 (2467 kilobytes per second) and from session 2 (2679 kilobytes per second) yields 5146 kilobytes per second, which is below the set dirty rate limit of the resource group (6144 kilobytes per seconds). @@ -325,7 +325,7 @@ INSERT 0 10000 !!! Note The `INSERT` commands in all four sessions started after the `SELECT pg_stat_statements_reset()` command in session 4 ran. -The following example shows the results from the `INSERT` commands in the four sessions: +This example shows the results from the `INSERT` commands in the four sessions: - `RECORD 3` shows the results from session 1. `RECORD 2` shows the results from session 2. @@ -366,29 +366,29 @@ The times of session 1 (28407.435) and session 2 (31343.458) are close to each o The actual dirty rate for session 1 is calculated as follows: -- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 28407.435 ms, which yields *0.35212612 blocks per millisecond*. -- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields *352.12612 blocks per second*. -- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately *2885 kilobytes per second*. +- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 28407.435 ms, which yields 0.35212612 blocks per millisecond. +- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 352.12612 blocks per second. +- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 2885 kilobytes per second. The actual dirty rate for session 2 is calculated as follows: -- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 31343.458 ms, which yields *0.31914156 blocks per millisecond*. -- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields *319.14156 blocks per second*. -- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately *2614 kilobytes per second*. +- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 31343.458 ms, which yields 0.31914156 blocks per millisecond. +- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 319.14156 blocks per second. +- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 2614 kilobytes per second. The combined dirty rate from session 1 (2885 kilobytes per second) and from session 2 (2614 kilobytes per second) yields 5499 kilobytes per second, which is near the set dirty rate limit of the resource group (6144 kilobytes per seconds). The actual dirty rate for session 3 is calculated as follows: -- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 52727.846 ms, which yields *0.18971001 blocks per millisecond*. -- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields *189.71001 blocks per second*. -- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately *1554 kilobytes per second*. +- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 52727.846 ms, which yields 0.18971001 blocks per millisecond. +- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 189.71001 blocks per second. +- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 1554 kilobytes per second. The actual dirty rate for session 4 is calculated as follows: -- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 56063.697 ms, which yields *0.17842205 blocks per millisecond*. -- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields *178.42205 blocks per second*. -- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately *1462 kilobytes per second*. +- The number of blocks dirtied per millisecond (ms) is 10003 blocks / 56063.697 ms, which yields 0.17842205 blocks per millisecond. +- Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 178.42205 blocks per second. +- Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 1462 kilobytes per second. The combined dirty rate from session 3 (1554 kilobytes per second) and from session 4 (1462 kilobytes per second) yields 3016 kilobytes per second, which is near the set dirty rate limit of the resource group (3072 kilobytes per seconds). diff --git a/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx b/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx index 0ada4c31486..36110b453dd 100644 --- a/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx +++ b/product_docs/docs/epas/15/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx @@ -283,7 +283,7 @@ Number of background workers to perform the clone in parallel. The default value The same cloning operation is performed as the example in [`remotecopyschema`](#remotecopyschema) but using the non-blocking function `remotecopyschema_nb`. -The following command starts pgAgent on the target database `tgtdb`. The `pgagent` program file is located in the `bin` subdirectory of the EDB Postgres Advanced Server installation directory. +This command starts pgAgent on the target database `tgtdb`. The `pgagent` program file is located in the `bin` subdirectory of the EDB Postgres Advanced Server installation directory. ```shell [root@localhost bin]# ./pgagent -l 1 -s /tmp/pgagent_tgtdb_log hostaddr=127.0.0.1 port=5444 From 7da104cd292f008cd1374d0951701912f181c132 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 17 Aug 2023 12:03:02 +0530 Subject: [PATCH 004/223] EPAS 15 - Log file fix as per DB-2428 Removed Log rotation file and Sudo configuration file and updated Logs and Lock files as per [DB-2428](https://enterprisedb.atlassian.net/browse/DB-2428) --- .../linux_install_details/component_locations.mdx | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx index 2619fc2125c..f675e154572 100644 --- a/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx @@ -22,10 +22,8 @@ The RPM installers place EDB Postgres Advanced Server components in the director | Documentation | `/usr/edb/as15/share/doc` | | Contrib | `/usr/edb/as15/share/contrib` | | Data | `/var/lib/edb/as15/data` | -| Logs | `/var/log/as15` | -| Lock files | `/var/lock/as15` | -| Log rotation file | `/etc/logrotate.d/as15` | -| Sudo configuration file | `/etc/sudoers.d/as15` | +| Logs | `/var/log/edb/as15` | +| Lock files | `/var/lock/edb/as15` | | Binary to access VIP without sudo | `/usr/edb/as15/bin/secure` | | Backup area | `/var/lib/edb/as15/backups` | | Templates | `/usr/edb/as15/share` | From ef38a8614863f29c2ef54aa8aa5961c4f8a7c635 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 17 Aug 2023 13:33:22 +0530 Subject: [PATCH 005/223] removed and update components as per feedback from Tushar --- .../installing/linux_install_details/component_locations.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx index f675e154572..bcdd65f4541 100644 --- a/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx @@ -18,13 +18,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director | --------------------------------- | ------------------------------------------ | | Executables | `/usr/edb/as15/bin` | | Libraries | `/usr/edb/as15/lib` | -| Cluster configuration files | `/etc/edb/as15` | +| Cluster configuration files | `/var/lib/edb/as15` | | Documentation | `/usr/edb/as15/share/doc` | | Contrib | `/usr/edb/as15/share/contrib` | | Data | `/var/lib/edb/as15/data` | | Logs | `/var/log/edb/as15` | | Lock files | `/var/lock/edb/as15` | -| Binary to access VIP without sudo | `/usr/edb/as15/bin/secure` | | Backup area | `/var/lib/edb/as15/backups` | | Templates | `/usr/edb/as15/share` | | Procedural Languages | `/usr/edb/as15/lib or /usr/edb/as15/lib64` | From 5748ce2e518ab2c4f1b6b35577431a7333778aa0 Mon Sep 17 00:00:00 2001 From: Maxim Burgerhout Date: Thu, 17 Aug 2023 10:07:03 +0200 Subject: [PATCH 006/223] Explicitly call out psql -U for OpenShift Update docs so it is clear users need to call the `kubectl cnp psql` command explicitly with a user on OpenShift due to the fact that OpenShift randomly assigns UID to users in containers. --- .../docs/postgres_for_kubernetes/1/kubectl-plugin.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx b/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx index 2f1cace2e97..96f0a74dfa2 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx @@ -889,6 +889,12 @@ postgres=# \q This command will start `kubectl exec`, and the `kubectl` executable must be reachable in your `PATH` variable to correctly work. +!!! Note + Mind that when connecting to instances running on OpenShift, one has to explicitly + pass a username to the `psql` command, because of a [security measure built into + OpenShift](https://cloud.redhat.com/blog/a-guide-to-openshift-and-uids): + `kubectl cnp psql cluster-example -- -U postgres`. + ### Snapshotting a Postgres cluster The `kubectl cnp snapshot` creates consistent snapshots of a Postgres From a5d8faa2cdb42cb680aa83ff9dac31dca39899cf Mon Sep 17 00:00:00 2001 From: maxim-edb <135828782+maxim-edb@users.noreply.github.com> Date: Thu, 17 Aug 2023 10:17:19 +0200 Subject: [PATCH 007/223] Removing references to clusters running on Debian. Don't know if this is easy to do, as this would make these docs diverge from the upstream ones, but referencing Debian here (`psql` output showing the cluster is running on Debian images), is quite confusing, and should probably be avoided. --- .../docs/postgres_for_kubernetes/1/kubectl-plugin.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx b/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx index 2f1cace2e97..308c067fc78 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx @@ -862,7 +862,7 @@ it from the actual pod. This means that you will be using the `postgres` user. ```shell kubectl cnp psql cluster-example -psql (15.3 (Debian 15.3-1.pgdg110+1)) +psql (15.3) Type "help" for help. postgres=# @@ -873,7 +873,7 @@ select to work against a replica by using the `--replica` option: ```shell kubectl cnp psql --replica cluster-example -psql (15.3 (Debian 15.3-1.pgdg110+1)) +psql (15.3) Type "help" for help. @@ -931,4 +931,4 @@ A specific `VolumeSnapshotClass` can be requested via the `-c` option: ```shell kubectl cnp snapshot cluster-example -c longhorn -``` \ No newline at end of file +``` From ddbc60fd927e6badcf8e25ecdc115a4a31ca1308 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 21 Aug 2023 11:59:10 +0530 Subject: [PATCH 008/223] Updated v14 to v11 with same edits --- .../linux_install_details/component_locations.mdx | 9 +++------ .../linux_install_details/component_locations.mdx | 9 +++------ .../linux_install_details/component_locations.mdx | 9 +++------ .../linux_install_details/component_locations.mdx | 9 +++------ 4 files changed, 12 insertions(+), 24 deletions(-) diff --git a/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx index ab97cfda841..7a657f60ef5 100644 --- a/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx @@ -18,15 +18,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director | --------------------------------- | ------------------------------------------ | | Executables | `/usr/edb/as11/bin` | | Libraries | `/usr/edb/as11/lib` | -| Cluster configuration files | `/etc/edb/as11` | +| Cluster configuration files | `/var/lib/edb/as11` | | Documentation | `/usr/edb/as11/share/doc` | | Contrib | `/usr/edb/as11/share/contrib` | | Data | `/var/lib/edb/as11/data` | -| Logs | `/var/log/as11` | -| Lock files | `/var/lock/as11` | -| Log rotation file | `/etc/logrotate.d/as11` | -| Sudo configuration file | `/etc/sudoers.d/as11` | -| Binary to access VIP without sudo | `/usr/edb/as11/bin/secure` | +| Logs | `/var/log/edb/as11` | +| Lock files | `/var/lock/edb/as11` | | Backup area | `/var/lib/edb/as11/backups` | | Templates | `/usr/edb/as11/share` | | Procedural Languages | `/usr/edb/as11/lib or /usr/edb/as11/lib64` | diff --git a/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx index 7f5a8778d12..83777c8ccc9 100644 --- a/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx @@ -18,15 +18,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director | --------------------------------- | ------------------------------------------ | | Executables | `/usr/edb/as12/bin` | | Libraries | `/usr/edb/as12/lib` | -| Cluster configuration files | `/etc/edb/as12` | +| Cluster configuration files | `/var/lib/edb/as12` | | Documentation | `/usr/edb/as12/share/doc` | | Contrib | `/usr/edb/as12/share/contrib` | | Data | `/var/lib/edb/as12/data` | -| Logs | `/var/log/as12` | -| Lock files | `/var/lock/as12` | -| Log rotation file | `/etc/logrotate.d/as12` | -| Sudo configuration file | `/etc/sudoers.d/as12` | -| Binary to access VIP without sudo | `/usr/edb/as12/bin/secure` | +| Logs | `/var/log/edb/as12` | +| Lock files | `/var/lock/edb/as12` | | Backup area | `/var/lib/edb/as12/backups` | | Templates | `/usr/edb/as12/share` | | Procedural Languages | `/usr/edb/as12/lib or /usr/edb/as12/lib64` | diff --git a/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx index 9f1b374a8eb..1954eaade0c 100644 --- a/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx @@ -17,15 +17,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director | --------------------------------- | ------------------------------------------ | | Executables | `/usr/edb/as13/bin` | | Libraries | `/usr/edb/as13/lib` | -| Cluster configuration files | `/etc/edb/as13` | +| Cluster configuration files | `/var/lib/edb/as13` | | Documentation | `/usr/edb/as13/share/doc` | | Contrib | `/usr/edb/as13/share/contrib` | | Data | `/var/lib/edb/as13/data` | -| Logs | `/var/log/as13` | -| Lock files | `/var/lock/as13` | -| Log rotation file | `/etc/logrotate.d/as13` | -| Sudo configuration file | `/etc/sudoers.d/as13` | -| Binary to access VIP without sudo | `/usr/edb/as13/bin/secure` | +| Logs | `/var/log/edb/as13` | +| Lock files | `/var/lock/edb/as13` | | Backup area | `/var/lib/edb/as13/backups` | | Templates | `/usr/edb/as13/share` | | Procedural Languages | `/usr/edb/as13/lib or /usr/edb/as13/lib64` | diff --git a/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx index 7010acb2381..7d84735bec9 100644 --- a/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx @@ -17,15 +17,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director | --------------------------------- | ------------------------------------------ | | Executables | `/usr/edb/as14/bin` | | Libraries | `/usr/edb/as14/lib` | -| Cluster configuration files | `/etc/edb/as14` | +| Cluster configuration files | `/var/lib/edb/as14` | | Documentation | `/usr/edb/as14/share/doc` | | Contrib | `/usr/edb/as14/share/contrib` | | Data | `/var/lib/edb/as14/data` | -| Logs | `/var/log/as14` | -| Lock files | `/var/lock/as14` | -| Log rotation file | `/etc/logrotate.d/as14` | -| Sudo configuration file | `/etc/sudoers.d/as14` | -| Binary to access VIP without sudo | `/usr/edb/as14/bin/secure` | +| Logs | `/var/log/edb/as14` | +| Lock files | `/var/lock/edb/as14` | | Backup area | `/var/lib/edb/as14/backups` | | Templates | `/usr/edb/as14/share` | | Procedural Languages | `/usr/edb/as14/lib or /usr/edb/as14/lib64` | From ad8ddc06aab333735e17b54e893ffd1939f49eb5 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Mon, 21 Aug 2023 16:56:19 -0400 Subject: [PATCH 009/223] Tech Partner Commvault v15 Testing --- .../05-UsingCommvaultBackupandRecovery.mdx | 49 ++++++++++++++++++- .../Images/FSBasedBackupJob.png | 3 ++ .../Images/FSBasedBackupJobDetails.png | 3 ++ .../Images/SelectFSBasedBackupType.png | 3 ++ 4 files changed, 57 insertions(+), 1 deletion(-) create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJob.png create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJobDetails.png create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/SelectFSBasedBackupType.png diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index 74c233627f2..cc4ab852227 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -17,7 +17,7 @@ Commvault provides two methods of taking the backup from an EDB database and res !!! Note At this time there is a known issue with FSBased Restore that does not allow for proper restoration of the database. See the known issues section of the guide for more information. -### DumpBasedBackupSet Backup and Restore +## DumpBasedBackupSet Backup and Restore Dump based backup uses the `pg_dump` Utility to take the backup. @@ -159,5 +159,52 @@ epas13_test=# ``` +## FSBasedBackupSet Backup and Restore +A file system backup backs up data that resides on a Windows or UNIX computer. + +### Taking FSBasedBackupSet Backup +1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to `Protect > Databases`. + +2. Click on the required instance. + +3. In the `Backup sets` section, click on `FSBasedBackupSet` backup set. + +4. In the `Database groups` section, click the database group that you want to back up. In this case it is `default`. + +5. In the `Backup` section, click `Back up`. + +6. Choose between a Full or Incremental backup in the `Select Backup Level` screen, this example chose an incremental backup. + + ![Select FSBased Backup Type](Images/SelectFSBasedBackupType.png) + +7. A job will be created to take the backup, which you can view by clicking on the `Job ID` for that backup. + + ![FSBased Backup Job](Images/FSBasedBackupJob.png) + +8. When the job is complete, the information about the job can be found on the job's page. + + ![FSBased Backup Job Details](Images/FSBasedBackupJobDetails.png) + +#### Restoring FSBasedBackupSet Full Backup +Backed up data can be restored for a subclient or an entire backup set with either an in-place restore, out-of-place restore or for a Linux file server to a standalone file server. + +1. From the navigation pane, go to `Protect > Databases`. + +2. Click the instance you want to restore. + +3. In the `Recovery Points` calender, select `FSBasedBackupSet`. + +4. Select a date where a full FSBasedBackupSet was taken and click `Restore`. + +5. The `Backup Content` screen will display the databases to be restored, select the required database to restore or select all of them to restore all. + +6. Click `Restore`. + +7. From the `Restore Options` screen, select where you want the restore to take go, in-place, out-of-place or restore to disk for a Linux server. + +8. Select the `Destination Server` and `Destination Instance` and click on submit. + +9. + ## Known Issues FSBaseBackupSet Restore has an issue if the default edb directory (for example, `*:\Program files\edb`) has been lost or deleted. If this occurs then after a restore is performed, the permissions on the restored directories are not recovered. Instead the directory inherits the permissions from the parent directory which does not allow EDB Postgres Advanced Server services to start on the restored directory. We are working with Commvault to resolve the issue. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJob.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJob.png new file mode 100644 index 00000000000..e4995df8065 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJob.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d43db9e5db0f0b0421541273f52d87736ae12e6879aee84bc8700a568d105691 +size 129298 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJobDetails.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJobDetails.png new file mode 100644 index 00000000000..2676007aa44 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJobDetails.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5da67b5742886735b8f41fc1c46f4d67483a70f405eb4f80c2e5b0740a6e7c9a +size 140432 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/SelectFSBasedBackupType.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/SelectFSBasedBackupType.png new file mode 100644 index 00000000000..5f3f1924352 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/SelectFSBasedBackupType.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68bc5a3f22590ee1e7068157679cb258506d757aa1f8cf6c14a1431925c2593c +size 117372 From 94e1b541dc5a12f91905f4e4d3e2a329da87d6b7 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Tue, 22 Aug 2023 09:40:56 -0400 Subject: [PATCH 010/223] Backup Info and Guide Updates --- ...-ConfiguringCommvaultBackupandRecovery.mdx | 2 +- .../05-UsingCommvaultBackupandRecovery.mdx | 40 ++++++++++++++----- .../06-CertificationEnvironment.mdx | 6 +-- 3 files changed, 33 insertions(+), 15 deletions(-) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx index 527b8acd113..2e9d2515c99 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx @@ -1,5 +1,5 @@ --- -title: 'Configuring Commvault Backup & Recovery' +title: 'Configuring' description: 'Walkthrough on configuring Commvault Backup & Recovery' redirects: - /partner_docs/CommVaultGuide/04-ConfiguringCommvaultBackupandRecovery/ diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index cc4ab852227..cd04922e8e6 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -1,5 +1,5 @@ --- -title: 'Using Commvault Backup & Recovery' +title: 'Using' description: 'Walkthroughs of multiple Commvault Backup & Recovery usage scenarios' redirects: - /partner_docs/CommVaultGuide/05-UsingCommvaultBackupandRecovery/ @@ -188,23 +188,41 @@ A file system backup backs up data that resides on a Windows or UNIX computer. #### Restoring FSBasedBackupSet Full Backup Backed up data can be restored for a subclient or an entire backup set with either an in-place restore, out-of-place restore or for a Linux file server to a standalone file server. -1. From the navigation pane, go to `Protect > Databases`. +1. Ensure that your EDB Postgres Advanced Server instance is stopped -2. Click the instance you want to restore. +2. Delete or rename the WAL directory and data directory. -3. In the `Recovery Points` calender, select `FSBasedBackupSet`. +3. From the navigation pane, go to `Protect > Databases`. -4. Select a date where a full FSBasedBackupSet was taken and click `Restore`. +4. Click the instance you want to restore. -5. The `Backup Content` screen will display the databases to be restored, select the required database to restore or select all of them to restore all. +5. In the `Recovery Points` calender, select `FSBasedBackupSet`. -6. Click `Restore`. +6. Select a date where a full FSBasedBackupSet was taken and click `Restore`. + +7. The `Backup Content` screen will display the databases to be restored, select the required database to restore or select all of them to restore all. + +8. Click `Restore`. + +9. From the `Restore Options` screen, select where you want the restore to complete, in-place, out-of-place or restore to disk for a Linux server. -7. From the `Restore Options` screen, select where you want the restore to take go, in-place, out-of-place or restore to disk for a Linux server. +10. Select the `Destination Server` and `Destination Instance` and click on submit. + +11. A Job will be created to restore the backup. + +12. When the Restore has completed successfully Commvault will automatically start the server using the pg_ctl utility. + +13. You can check that the server was started successfully with a command like, `"C:\Program Files\edb\as15\bin\pg_ctl" -U enterprisedb status -D "C:\Program Files\edb\as15\data"` and it should return a message that the server is running. + +```bash +C:\Program Files\edb\as15>"C:\Program Files\edb\as15\bin\pg_ctl" -U enterprisedb status -D "C:\Program Files\edb\as15\data" +pg_ctl: server is running (PID: 20896) +C:/Program Files/edb/as15/bin/edb-postgres.exe "-D" "C:\Program Files\edb\as15\data" +``` -8. Select the `Destination Server` and `Destination Instance` and click on submit. +14. If you would like the server to be controlled by a Services utility you will need to stop it with the pg_ctl utility and start it again in your Services utility, for example Services(Local) in Windows or systemctl in UNIX. -9. +15. After you have started the service with whichever utility you choose, login to your EDB database and check that the restore operation recovered the data. ## Known Issues -FSBaseBackupSet Restore has an issue if the default edb directory (for example, `*:\Program files\edb`) has been lost or deleted. If this occurs then after a restore is performed, the permissions on the restored directories are not recovered. Instead the directory inherits the permissions from the parent directory which does not allow EDB Postgres Advanced Server services to start on the restored directory. We are working with Commvault to resolve the issue. +FSBaseBackupSet Incremental or Point-In-Time(PITR) Restore has issues with Postgres and EDB Postgres Advanced Server versions 13 and onward. The behavior is due to a change that was made in Postgres version 13. From the release notes, `Generate an error if recovery does not reach the specified recovery target`. While Commvault does provide a time target for the recovery, the recovery is performed entirely by Postgres and Postgres does not know how to reach that time target, therefore it fails. This can happen where there are no transactions between backup jobs. A workaround for this solution is to always introduce a transaction scenario, such as a create and drop database, before doing a log backup. Another workaround is to use `recovery_target_lsn` in the postgresql.conf file instead of uisng `recovery_target_time`. Commvault is aware of this error on their side and is working on how to mitigate from their end. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx index c5558f699a7..83a81f8d6e1 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx @@ -5,7 +5,7 @@ description: 'Overview of the certification environment used in the certificatio |   |   | | ----------- | ----------- | -| **Certification Test Date** | June 16, 2022 | -| **EDB Postgres Advanced Server** | 11, 12, 13, 14 | +| **Certification Test Date** | August 22, 2023 | +| **EDB Postgres Advanced Server** | 12, 13, 14, 15 | | **EDB Postgres Extended Server** | 11, 12, 13 | -| **Commvault Backup & Recovery** | 11.24 | +| **Commvault Backup & Recovery** | 11.32 | From ad0c2e68528a0494ec78a95ecab3510e5e94cd2a Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:57:26 -0400 Subject: [PATCH 011/223] Edited Configuring PGD CLI topic Includes changes made in PR4627 --- .../docs/pgd/5/cli/configuring_cli.mdx | 22 +++++++++---------- 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/pgd/5/cli/configuring_cli.mdx b/product_docs/docs/pgd/5/cli/configuring_cli.mdx index 51bf554338e..b1bc7a1f88a 100644 --- a/product_docs/docs/pgd/5/cli/configuring_cli.mdx +++ b/product_docs/docs/pgd/5/cli/configuring_cli.mdx @@ -3,25 +3,25 @@ title: "Configuring PGD CLI" navTitle: "Configuring PGD CLI" --- -PGD CLI can be installed on any system which is able to connect to the PGD cluster. You will require a user with PGD superuser privileges - the [bdr_superuser role](../security) - or equivalent (for example, edb_admin on BigAnimal distributed high-availability) to use PGD CLI. +PGD CLI can be installed on any system that can connect to the PGD cluster. To use PGD CLI, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is edb_admin on a BigAnimal distributed high-availability cluster. ## PGD CLI and database connection strings -You may not need a database connection string. For example, when Trusted Postgres Architect installs the PGD CLI on a system, it also configures the connection to the PGD cluster. This means that PGD CLI will automatically connect when run. +You might not need a database connection string. For example, when Trusted Postgres Architect installs the PGD CLI on a system, it also configures the connection to the PGD cluster, which means that the PGD CLI connects when run. -If you are installing PGD CLI manually, you must give PGD CLI a database connection string so it knows which PGD cluster to connect to. +If you're installing PGD CLI manually, you must give PGD CLI a database connection string so it knows which PGD cluster to connect to. !!! Important Setting passwords -PGD CLI does not interactively prompt for your user's password. You must pass your password using one of the following methods: +PGD CLI doesn't interactively prompt for your password. You must pass your password using one of the following methods: - 1. Adding an entry to your [`.pgpass` password file](https://www.postgresql.org/docs/current/libpq-pgpass.html) which includes the host, port, database name, user name, and password. - 1. Setting the password in the `PGPASSWORD` environment variable. - 1. Including the password in the connection string. + - Adding an entry to your [`.pgpass` password file](https://www.postgresql.org/docs/current/libpq-pgpass.html), which includes the host, port, database name, user name, and password. + - Setting the password in the `PGPASSWORD` environment variable. + - Including the password in the connection string. -We recommend the first option, as the other options don't scale well with multiple databases or compromise password confidentiality. +We recommend the first option, as the other options don't scale well with multiple databases, or they compromise password confidentiality. !!! -If you don't know the database connection strings for your PGD-powered deployment, see [discovering connection strings](discover_connections). It is a guide to finding the right connection strings for your cluster. +If you don't know the database connection strings for your PGD-powered deployment, see [discovering connection strings](discover_connections), which helps you to find the right connection strings for your cluster. Once you have that information, you can continue. @@ -29,7 +29,6 @@ Once you have that information, you can continue. PGD CLI takes its database connection information from either the PGD CLI configuration file or the command line. - ### Using database connection strings in the command line You can pass the connection string directly to `pgd` using the `--dsn` option. For details, see the [sample use case](using_cli/#passing-a-database-connection-string). For example: @@ -58,5 +57,4 @@ By default, `pgd-cli-config.yml` is located in the `/etc/edb/pgd-cli` directory. 1. `/etc/edb/pgd-cli` (default) 2. `$HOME/.edb/pgd-cli` -If your configuration file is not in either of these directories, you can use the optional `-f` or `--config-file` flag on a `pgd` command to set which file should be read as configuration. See the [sample use case](using_cli/#passing-a-database-connection-string). - +If your configuration file isn't in either of these directories, you can use the optional `-f` or `--config-file` flag on a `pgd` command to set the file to read as configuration. See the [sample use case](using_cli/#passing-a-database-connection-string). From 2462d8103c6474d7b3d6d06a766181e41b2d479f Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Tue, 22 Aug 2023 16:49:15 -0400 Subject: [PATCH 012/223] More Restore and Guide Updates --- .../05-UsingCommvaultBackupandRecovery.mdx | 8 +++- .../07-SupportandLogging.mdx | 42 +++++++++++++++++++ .../Images/CommvaultViewLogsForJob.png | 3 ++ .../Images/FSBasedFullRestoreDatabases.png | 3 ++ .../Images/FSBasedFullRestoreOptions.png | 3 ++ .../CommvaultBackupandRecovery/index.mdx | 2 + 6 files changed, 59 insertions(+), 2 deletions(-) create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/CommvaultViewLogsForJob.png create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreDatabases.png create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreOptions.png diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index cd04922e8e6..db902949db6 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -15,7 +15,7 @@ Commvault provides two methods of taking the backup from an EDB database and res 2. FSBasedBackupSet Backup and Restore !!! Note - At this time there is a known issue with FSBased Restore that does not allow for proper restoration of the database. See the known issues section of the guide for more information. + At this time there is a known issue with FSBased Incremental/PITR Restore that does not allow for proper restoration of the database. See the known issues section of the guide for more information. ## DumpBasedBackupSet Backup and Restore @@ -202,10 +202,14 @@ Backed up data can be restored for a subclient or an entire backup set with eith 7. The `Backup Content` screen will display the databases to be restored, select the required database to restore or select all of them to restore all. + ![FSBased Backup Restore Databases](Images/FSBasedFullRestoreDatabases.png) + 8. Click `Restore`. 9. From the `Restore Options` screen, select where you want the restore to complete, in-place, out-of-place or restore to disk for a Linux server. + ![FSBased Backup Restore Details](Images/FSBasedFullRestoreOptions.png) + 10. Select the `Destination Server` and `Destination Instance` and click on submit. 11. A Job will be created to restore the backup. @@ -222,7 +226,7 @@ C:/Program Files/edb/as15/bin/edb-postgres.exe "-D" "C:\Program Files\edb\as15\d 14. If you would like the server to be controlled by a Services utility you will need to stop it with the pg_ctl utility and start it again in your Services utility, for example Services(Local) in Windows or systemctl in UNIX. -15. After you have started the service with whichever utility you choose, login to your EDB database and check that the restore operation recovered the data. +15. After you have started the service with your utility of choice, login to your EDB database and check that the restore operation recovered the data. ## Known Issues FSBaseBackupSet Incremental or Point-In-Time(PITR) Restore has issues with Postgres and EDB Postgres Advanced Server versions 13 and onward. The behavior is due to a change that was made in Postgres version 13. From the release notes, `Generate an error if recovery does not reach the specified recovery target`. While Commvault does provide a time target for the recovery, the recovery is performed entirely by Postgres and Postgres does not know how to reach that time target, therefore it fails. This can happen where there are no transactions between backup jobs. A workaround for this solution is to always introduce a transaction scenario, such as a create and drop database, before doing a log backup. Another workaround is to use `recovery_target_lsn` in the postgresql.conf file instead of uisng `recovery_target_time`. Commvault is aware of this error on their side and is working on how to mitigate from their end. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx new file mode 100644 index 00000000000..303d6c2bb43 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx @@ -0,0 +1,42 @@ +--- +title: 'Support and Logging Details' +description: 'Details of the support process and logging information' +--- + +## Support + +Technical support for the use of these products is provided by both EDB and Commvault. A proper support contract is required to be in place at both EDB and Commvault. A support ticket can be opened on either side to start the process. If it is determined through the support ticket that resources from the other vendor is required, the customer should open a support ticket with that vendor through normal support channels. This will allow both companies to work together to help the customer as needed. + +## Logging + +**EDB Postgres Advanced Server Logs:** + +Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance and from here you can navigate to `log`, `current_logfiles` or you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs. + +**EDB Postgres Extended Server Logs** + +Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance and from here you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options. An example of the full path to view EDB Postgres Extended logs: `/var/lib/edb-pge/15/data/log`. + +**PostgreSQL Server Logs** + +The default log directories for PostgreSQL logs vary depending on the operating system: + +- Debian-based system: `/var/log/postgresql/postgresql-x.x.main.log. X.x.` + +- Red Hat-based system: `/var/lib/pgsql/data/pg_log` + +- Windows: `C:\Program Files\PostgreSQL\9.3\data\pg_log` + +** Commvault Logs** + +Commvault logs can be found a few ways. A first way is within the Content Store directory/folder in the Commvault folder on your system. For example if on a Windows system the Log File path would be `C:\Program Files\Commvault\ContentStore\LogFiles` where you can then see all of the differnt types of logs Commvault collects. + +You can also gather some job specific logs within the Commvault interface. + +1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to `Jobs > Job History`. + +2. Find the specific job you would like to view logs for and click on the `...` beside that job. + +3. Select `View Logs`. + + ![View Job Logs](Images/CommvaultViewLogsForJob.png) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/CommvaultViewLogsForJob.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/CommvaultViewLogsForJob.png new file mode 100644 index 00000000000..ed1093daafa --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/CommvaultViewLogsForJob.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db6a73932cd532dad2bef06a09ba99f4e7c8184ae74ce204e2fab6747e270333 +size 1146108 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreDatabases.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreDatabases.png new file mode 100644 index 00000000000..e537f6ca6af --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreDatabases.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:913d3eb2f127a84517ddab7039323da6ff2ac3eb67ec05a84a94cb993c40f6bf +size 87505 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreOptions.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreOptions.png new file mode 100644 index 00000000000..ae4a2a7023d --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreOptions.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2827c237d4db8cb80a94b996c367c34e26df54a0d9447b1334055bf9ca04791 +size 755537 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx index 41e76ace9cb..4b0ef0800c6 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx @@ -10,3 +10,5 @@ directoryDefaults:

EDB GlobalConnect Technology Partner Implementation Guide

Commvault Backup & Recovery

+ +

This document is intended to augment each vendor’s product documentation to guide you in getting the products working together. It isn't intended to show the optimal configuration for the certified integration.

\ No newline at end of file From 3712681cdb944cc51ad6f256df8e2f3834fd92f4 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Tue, 22 Aug 2023 16:55:52 -0400 Subject: [PATCH 013/223] Error Edits --- .../04-ConfiguringCommvaultBackupandRecovery.mdx | 2 -- .../05-UsingCommvaultBackupandRecovery.mdx | 4 +--- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx index 2e9d2515c99..776bcb89d8a 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx @@ -1,8 +1,6 @@ --- title: 'Configuring' description: 'Walkthrough on configuring Commvault Backup & Recovery' -redirects: - - /partner_docs/CommVaultGuide/04-ConfiguringCommvaultBackupandRecovery/ --- Implementing Commvault Backup & Recovery with an EDB database requires the following components: diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index db902949db6..27dc9e2ded4 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -1,8 +1,6 @@ --- title: 'Using' -description: 'Walkthroughs of multiple Commvault Backup & Recovery usage scenarios' -redirects: - - /partner_docs/CommVaultGuide/05-UsingCommvaultBackupandRecovery/ +description: 'Walkthrough of example usage scenarios' --- How to backup and restore an EDB Database using Commvault Backup & Recovery. From f83d40f41eda29431e853b29bd52f5a5a82ddcce Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Wed, 23 Aug 2023 13:19:45 +0530 Subject: [PATCH 014/223] PEM 9.3 - Release branch Added content as per [PEM-4853](https://enterprisedb.atlassian.net/browse/PEM-4853), [PEM-4906](https://enterprisedb.atlassian.net/browse/PEM-4906), and [PEM-4907]https://enterprisedb.atlassian.net/browse/PEM-4907). --- product_docs/docs/pem/9/images/alert_copy.png | 4 +-- .../9/images/alert_history_report_general.png | 3 ++ .../pem/9/images/alerting_manage_alerts.png | 4 +-- .../pem/9/images/default_email_template.png | 3 ++ .../docs/pem/9/images/email_template_edit.png | 3 ++ .../pem/9/images/email_template_restore.png | 3 ++ .../docs/pem/9/images/pem_management_menu.png | 4 +-- .../pem/9/monitoring_performance/alerts.mdx | 7 ++++- .../monitoring_performance/notifications.mdx | 30 +++++++++++++++++++ product_docs/docs/pem/9/pem_web_interface.mdx | 2 +- product_docs/docs/pem/9/reports.mdx | 15 ++++++++++ 11 files changed, 70 insertions(+), 8 deletions(-) mode change 100755 => 100644 product_docs/docs/pem/9/images/alert_copy.png create mode 100644 product_docs/docs/pem/9/images/alert_history_report_general.png create mode 100644 product_docs/docs/pem/9/images/default_email_template.png create mode 100644 product_docs/docs/pem/9/images/email_template_edit.png create mode 100644 product_docs/docs/pem/9/images/email_template_restore.png diff --git a/product_docs/docs/pem/9/images/alert_copy.png b/product_docs/docs/pem/9/images/alert_copy.png old mode 100755 new mode 100644 index 02f990ef970..b3fea692ae8 --- a/product_docs/docs/pem/9/images/alert_copy.png +++ b/product_docs/docs/pem/9/images/alert_copy.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:72b715546e266575e40f4c4b85fdf883f3f4126345a48bdca981a2a93cc22d36 -size 62210 +oid sha256:da3c35c608983fc063285d304923bb05eb1dc4119270eafeeb910f8fe7659f19 +size 71544 diff --git a/product_docs/docs/pem/9/images/alert_history_report_general.png b/product_docs/docs/pem/9/images/alert_history_report_general.png new file mode 100644 index 00000000000..173690a76d0 --- /dev/null +++ b/product_docs/docs/pem/9/images/alert_history_report_general.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:063b3e8aab631ae507765aac68f7b0c60cf0b12eb8c5fdbf90138a1f4d9e92f4 +size 56260 diff --git a/product_docs/docs/pem/9/images/alerting_manage_alerts.png b/product_docs/docs/pem/9/images/alerting_manage_alerts.png index 8571dbe614d..3c65cb44852 100644 --- a/product_docs/docs/pem/9/images/alerting_manage_alerts.png +++ b/product_docs/docs/pem/9/images/alerting_manage_alerts.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5f65c79ea86b8355493a226ef6ae144ab1ced63ece1a1f12965e829ad5bd83b6 -size 227680 +oid sha256:94c7cb1020cd098f3a31c31da60f9f66990ea091aea34ebcef8235e28922c2b0 +size 197737 diff --git a/product_docs/docs/pem/9/images/default_email_template.png b/product_docs/docs/pem/9/images/default_email_template.png new file mode 100644 index 00000000000..8290d5ce8fe --- /dev/null +++ b/product_docs/docs/pem/9/images/default_email_template.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79c0add8779b0b871605bc038df4e01545309fc135a694ce253f11f0c49fce2c +size 162139 diff --git a/product_docs/docs/pem/9/images/email_template_edit.png b/product_docs/docs/pem/9/images/email_template_edit.png new file mode 100644 index 00000000000..21cab62c1ae --- /dev/null +++ b/product_docs/docs/pem/9/images/email_template_edit.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:606f6ac861a890c127c5a802358ca0715e5ee51fd9d6157abbda2c8a19e7e5ed +size 205416 diff --git a/product_docs/docs/pem/9/images/email_template_restore.png b/product_docs/docs/pem/9/images/email_template_restore.png new file mode 100644 index 00000000000..b8accf8e661 --- /dev/null +++ b/product_docs/docs/pem/9/images/email_template_restore.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26887be4bb2bb27c5f2b55ad33b5ce1326f0d41ab2ba0596700112ce4bde3458 +size 155889 diff --git a/product_docs/docs/pem/9/images/pem_management_menu.png b/product_docs/docs/pem/9/images/pem_management_menu.png index 87f65dadd79..d1cd49508d5 100644 --- a/product_docs/docs/pem/9/images/pem_management_menu.png +++ b/product_docs/docs/pem/9/images/pem_management_menu.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e22937a7945d6e32f306794c2fb11b016f92e1b3ed56059c6f9982993fb59224 -size 145437 +oid sha256:2fd691019a28583b02c0a378e239bf7a5d967485b4f062814e06c90a2f664083 +size 213670 diff --git a/product_docs/docs/pem/9/monitoring_performance/alerts.mdx b/product_docs/docs/pem/9/monitoring_performance/alerts.mdx index 0c8ca924e5a..b61ffe029d7 100644 --- a/product_docs/docs/pem/9/monitoring_performance/alerts.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/alerts.mdx @@ -62,6 +62,7 @@ Use the Quick Links toolbar to open dialog boxes and tabs for managing alerts: - Select **Copy Alerts** to open the Copy Alert Configuration dialog box and copy an alert definition. - Select **Alert Templates** to open the **Alert Template** tab and modify or create an alert template. +- Select **Email Templates** to open the **Email Template** dialog, and modify the default email template to customize an email notification. - Select **Email Groups** to open the **Email Groups** tab and modify or create an email group. - Select **Webhooks** to open the **Webhooks** tab and create or manage the webhooks endpoints. - Select **Server Configurations** to open the Server Configuration dialog box and review or modify server configuration settings. @@ -628,7 +629,11 @@ The Copy Alert Configuration dialog box copies all alerts from the object select To copy alerts to multiple objects at once, select a parent node of the targets. For example, to copy the alerts from one table to all tables in a schema, select the check box next to the schema. PEM copies alerts only to targets that are the same type as the source object. -Select **Ignore duplicates** to prevent PEM from updating any existing alerts on the target objects with the same name as those being copied. Select **Replace duplicates** to replace existing alerts with alerts of the same name from the source object. +Select **Ignore duplicates** to prevent PEM from updating any existing alerts on the target objects with the same name as those being copied. + +Select **Replace duplicates** to replace existing alerts with alerts of the same name from the source object. + +Select **Delete Existing Alerts** to delete all the alerts from the target object and copy all the alerts from the source object to the target object. Select **Configure Alerts** to copy the alerts from the source object to all objects of the same type in or under those objects selected on the Copy Alert Configuration dialog box. diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index eb0d1ba755c..04ebaeec7a5 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -265,3 +265,33 @@ You can use the following command to confirm that Nagios is properly configured: After confirming that Nagios is configured correctly, restart the Nagios service: `/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg` + +## Customizing email templates + +Postgres Enterprise Manager monitors your system for conditions that require user attention and sends email notifications. Use the `Email Templates` to customize the email subject and the payload that the server sends if the current values deviate from the threshold values specified by an alert. + +These are the default email templates that are customizable: + +- Alert detected +- Alert level increased +- Alert level decreased +- Alert cleared +- Alert reminder +- Job success +- Job failure +- Job cancellation +- Job step +- Job step (Database server) + +If any of the default alert template is customized then a green tick mark is displayed against that template in the `Custom Template?` column. + +Select the edit button to customize the email template: + +![Email Template Edit](../images/email_template_edit.png) + +Edit the `Subject` and `Payload` fields, as needed, from the available list of placeholders. + +Select the custom template and select the undo button at the top, to restore it as default template: + +![Email Template Restore](../images/email_template_restore.png) + diff --git a/product_docs/docs/pem/9/pem_web_interface.mdx b/product_docs/docs/pem/9/pem_web_interface.mdx index a9acc238663..d824e58d78e 100644 --- a/product_docs/docs/pem/9/pem_web_interface.mdx +++ b/product_docs/docs/pem/9/pem_web_interface.mdx @@ -306,7 +306,7 @@ Use the **Management** menu to access the following PEM features. | **Postgres Log Analysis Expert** | Open the Postgres Log Analysis Expert dialog box to analyze log file contents for usage trends. | | **Scheduled Tasks** | Open the **Scheduled Tasks** tab and review tasks that are pending or recently completed. | | **Tuning Wizard** | Open the Tuning Wizard dialog box to generate a set of tuning recommendations for your server. | -| **Reports** | Open the Reports dialog box to generate the system configuration report and core usage report for your server. | +| **Reports** | Open the Reports dialog box to generate the alert history report, system configuration report, or core usage report for your server. | | **Schedule Alert Blackout** | Open the Schedule Alert Blackout dialog box and schedule the alerts blackout for your servers and agents. | ### Dashboards menu diff --git a/product_docs/docs/pem/9/reports.mdx b/product_docs/docs/pem/9/reports.mdx index 2d51069dd4d..0d2c3ef1c79 100644 --- a/product_docs/docs/pem/9/reports.mdx +++ b/product_docs/docs/pem/9/reports.mdx @@ -13,6 +13,7 @@ You can generate the System Configuration report and Core Usage report for all l Reports has following options: +- Alert History Report (JSON) - System Configuration Report (JSON) - System Configuration Report (HTML) - Core Usage Report (JSON) @@ -22,6 +23,20 @@ Only superusers or the users with the pem_admin role can download the System Con Information in these reports shows the latest probe run time. +## Alert History Report + +The Alert History Report provides detailed information about the alerts history at the agent or server level in JSON format. + +Go to `Management` menu, select `Reports` then select `Alert History Report`. A new dialogue box opens: + +![Alert History Report](../images/alert_history_report_general.png) + +- **Agent/Server Name**— Select the agents and servers from the drop-down list. `Overall System Report` option is also available to generate a report for all the registered and active agents and servers. + +- **Timeframe**— Select the required timeframe from the drop-down list. + +- **Alert Types**— Select the alert types you wish to generate the alert history report for. + ## System Configuration Report The System Configuration Report provides detailed information about the PEM Agents group, PEM Server Directory group, and custom groups listed under the browser tree. These groups can contain Postgres Enterprise Manager, PEM agent, and database servers. You can download this report in HTML and JSON formats. From c9e168903eae9de8efc5a0ad803459b1451c157b Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Mon, 21 Aug 2023 16:56:19 -0400 Subject: [PATCH 015/223] Tech Partner Commvault v15 Testing --- .../05-UsingCommvaultBackupandRecovery.mdx | 53 +++++++++++++++++-- .../Images/FSBasedBackupJob.png | 3 ++ .../Images/FSBasedBackupJobDetails.png | 3 ++ .../Images/SelectFSBasedBackupType.png | 3 ++ 4 files changed, 59 insertions(+), 3 deletions(-) create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJob.png create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJobDetails.png create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/SelectFSBasedBackupType.png diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index e24f6da2ed0..e579e7acf27 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -17,7 +17,7 @@ Commvault provides two methods of taking the backup from an EDB database and res !!! Note At this time there's a known issue with FSBased Restore that doesn't allow for proper restoration of the database. See [Known issues](#known-issues) for more information. -### DumpBasedBackupSet backup and restore +## DumpBasedBackupSet Backup and Restore Dump-based backup uses the pg_dump utility to take the backup. @@ -160,5 +160,52 @@ epas13_test=# ``` -## Known issues -FSBaseBackupSet restore has an issue if the default edb directory, for example, `*:\Program files\edb`, was lost or deleted. If this occurs, then after a restore is performed, the permissions on the restored directories aren't recovered. Instead, the directory inherits the permissions from the parent directory, which doesn't allow EDB Postgres Advanced Server services to start on the restored directory. We're working with Commvault to resolve the issue. +## FSBasedBackupSet Backup and Restore +A file system backup backs up data that resides on a Windows or UNIX computer. + +### Taking FSBasedBackupSet Backup +1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to `Protect > Databases`. + +2. Click on the required instance. + +3. In the `Backup sets` section, click on `FSBasedBackupSet` backup set. + +4. In the `Database groups` section, click the database group that you want to back up. In this case it is `default`. + +5. In the `Backup` section, click `Back up`. + +6. Choose between a Full or Incremental backup in the `Select Backup Level` screen, this example chose an incremental backup. + + ![Select FSBased Backup Type](Images/SelectFSBasedBackupType.png) + +7. A job will be created to take the backup, which you can view by clicking on the `Job ID` for that backup. + + ![FSBased Backup Job](Images/FSBasedBackupJob.png) + +8. When the job is complete, the information about the job can be found on the job's page. + + ![FSBased Backup Job Details](Images/FSBasedBackupJobDetails.png) + +#### Restoring FSBasedBackupSet Full Backup +Backed up data can be restored for a subclient or an entire backup set with either an in-place restore, out-of-place restore or for a Linux file server to a standalone file server. + +1. From the navigation pane, go to `Protect > Databases`. + +2. Click the instance you want to restore. + +3. In the `Recovery Points` calender, select `FSBasedBackupSet`. + +4. Select a date where a full FSBasedBackupSet was taken and click `Restore`. + +5. The `Backup Content` screen will display the databases to be restored, select the required database to restore or select all of them to restore all. + +6. Click `Restore`. + +7. From the `Restore Options` screen, select where you want the restore to take go, in-place, out-of-place or restore to disk for a Linux server. + +8. Select the `Destination Server` and `Destination Instance` and click on submit. + +9. + +## Known Issues +FSBaseBackupSet Restore has an issue if the default edb directory (for example, `*:\Program files\edb`) has been lost or deleted. If this occurs then after a restore is performed, the permissions on the restored directories are not recovered. Instead the directory inherits the permissions from the parent directory which does not allow EDB Postgres Advanced Server services to start on the restored directory. We are working with Commvault to resolve the issue. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJob.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJob.png new file mode 100644 index 00000000000..e4995df8065 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJob.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d43db9e5db0f0b0421541273f52d87736ae12e6879aee84bc8700a568d105691 +size 129298 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJobDetails.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJobDetails.png new file mode 100644 index 00000000000..2676007aa44 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJobDetails.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5da67b5742886735b8f41fc1c46f4d67483a70f405eb4f80c2e5b0740a6e7c9a +size 140432 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/SelectFSBasedBackupType.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/SelectFSBasedBackupType.png new file mode 100644 index 00000000000..5f3f1924352 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/SelectFSBasedBackupType.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68bc5a3f22590ee1e7068157679cb258506d757aa1f8cf6c14a1431925c2593c +size 117372 From ac6ec309a0270eb9461f24ddd5307fd244806ab4 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Tue, 22 Aug 2023 09:40:56 -0400 Subject: [PATCH 016/223] Backup Info and Guide Updates --- .../05-UsingCommvaultBackupandRecovery.mdx | 38 ++++++++++++++----- .../06-CertificationEnvironment.mdx | 8 ++-- 2 files changed, 32 insertions(+), 14 deletions(-) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index e579e7acf27..f69dca4fb49 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -189,23 +189,41 @@ A file system backup backs up data that resides on a Windows or UNIX computer. #### Restoring FSBasedBackupSet Full Backup Backed up data can be restored for a subclient or an entire backup set with either an in-place restore, out-of-place restore or for a Linux file server to a standalone file server. -1. From the navigation pane, go to `Protect > Databases`. +1. Ensure that your EDB Postgres Advanced Server instance is stopped -2. Click the instance you want to restore. +2. Delete or rename the WAL directory and data directory. -3. In the `Recovery Points` calender, select `FSBasedBackupSet`. +3. From the navigation pane, go to `Protect > Databases`. -4. Select a date where a full FSBasedBackupSet was taken and click `Restore`. +4. Click the instance you want to restore. -5. The `Backup Content` screen will display the databases to be restored, select the required database to restore or select all of them to restore all. +5. In the `Recovery Points` calender, select `FSBasedBackupSet`. -6. Click `Restore`. +6. Select a date where a full FSBasedBackupSet was taken and click `Restore`. -7. From the `Restore Options` screen, select where you want the restore to take go, in-place, out-of-place or restore to disk for a Linux server. +7. The `Backup Content` screen will display the databases to be restored, select the required database to restore or select all of them to restore all. -8. Select the `Destination Server` and `Destination Instance` and click on submit. +8. Click `Restore`. -9. +9. From the `Restore Options` screen, select where you want the restore to complete, in-place, out-of-place or restore to disk for a Linux server. + +10. Select the `Destination Server` and `Destination Instance` and click on submit. + +11. A Job will be created to restore the backup. + +12. When the Restore has completed successfully Commvault will automatically start the server using the pg_ctl utility. + +13. You can check that the server was started successfully with a command like, `"C:\Program Files\edb\as15\bin\pg_ctl" -U enterprisedb status -D "C:\Program Files\edb\as15\data"` and it should return a message that the server is running. + +```bash +C:\Program Files\edb\as15>"C:\Program Files\edb\as15\bin\pg_ctl" -U enterprisedb status -D "C:\Program Files\edb\as15\data" +pg_ctl: server is running (PID: 20896) +C:/Program Files/edb/as15/bin/edb-postgres.exe "-D" "C:\Program Files\edb\as15\data" +``` + +14. If you would like the server to be controlled by a Services utility you will need to stop it with the pg_ctl utility and start it again in your Services utility, for example Services(Local) in Windows or systemctl in UNIX. + +15. After you have started the service with whichever utility you choose, login to your EDB database and check that the restore operation recovered the data. ## Known Issues -FSBaseBackupSet Restore has an issue if the default edb directory (for example, `*:\Program files\edb`) has been lost or deleted. If this occurs then after a restore is performed, the permissions on the restored directories are not recovered. Instead the directory inherits the permissions from the parent directory which does not allow EDB Postgres Advanced Server services to start on the restored directory. We are working with Commvault to resolve the issue. +FSBaseBackupSet Incremental or Point-In-Time(PITR) Restore has issues with Postgres and EDB Postgres Advanced Server versions 13 and onward. The behavior is due to a change that was made in Postgres version 13. From the release notes, `Generate an error if recovery does not reach the specified recovery target`. While Commvault does provide a time target for the recovery, the recovery is performed entirely by Postgres and Postgres does not know how to reach that time target, therefore it fails. This can happen where there are no transactions between backup jobs. A workaround for this solution is to always introduce a transaction scenario, such as a create and drop database, before doing a log backup. Another workaround is to use `recovery_target_lsn` in the postgresql.conf file instead of uisng `recovery_target_time`. Commvault is aware of this error on their side and is working on how to mitigate from their end. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx index 5624b0b1107..a0f30af3cd0 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx @@ -5,7 +5,7 @@ description: 'Overview of the certification environment used in the certificatio |   |   | | ----------- | ----------- | -| **Certification test date** | June 16, 2022 | -| **EDB Postgres Advanced Server** | 11, 12, 13, 14 | -| **EDB Postgres Extended Server** | 11, 12, 13 | -| **Commvault Backup & Recovery** | 11.24 | +| **Certification Test Date** | August 22, 2023 | +| **EDB Postgres Advanced Server** | 12, 13, 14, 15 | +| **EDB Postgres Extended Server** | 12, 13 | +| **Commvault Backup & Recovery** | 11.32 | From 455ef8cabc18508de942dc27930101ee94df63f4 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Tue, 22 Aug 2023 16:49:15 -0400 Subject: [PATCH 017/223] More Restore and Guide Updates --- .../05-UsingCommvaultBackupandRecovery.mdx | 8 +++- .../07-SupportandLogging.mdx | 42 +++++++++++++++++++ .../Images/CommvaultViewLogsForJob.png | 3 ++ .../Images/FSBasedFullRestoreDatabases.png | 3 ++ .../Images/FSBasedFullRestoreOptions.png | 3 ++ .../CommvaultBackupandRecovery/index.mdx | 2 + 6 files changed, 59 insertions(+), 2 deletions(-) create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/CommvaultViewLogsForJob.png create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreDatabases.png create mode 100644 advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreOptions.png diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index f69dca4fb49..250f31681f8 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -15,7 +15,7 @@ Commvault provides two methods of taking the backup from an EDB database and res - FSBasedBackupSet backup and restore !!! Note - At this time there's a known issue with FSBased Restore that doesn't allow for proper restoration of the database. See [Known issues](#known-issues) for more information. + At this time there is a known issue with FSBased Incremental/PITR Restore that does not allow for proper restoration of the database. See the known issues section of the guide for more information. ## DumpBasedBackupSet Backup and Restore @@ -203,10 +203,14 @@ Backed up data can be restored for a subclient or an entire backup set with eith 7. The `Backup Content` screen will display the databases to be restored, select the required database to restore or select all of them to restore all. + ![FSBased Backup Restore Databases](Images/FSBasedFullRestoreDatabases.png) + 8. Click `Restore`. 9. From the `Restore Options` screen, select where you want the restore to complete, in-place, out-of-place or restore to disk for a Linux server. + ![FSBased Backup Restore Details](Images/FSBasedFullRestoreOptions.png) + 10. Select the `Destination Server` and `Destination Instance` and click on submit. 11. A Job will be created to restore the backup. @@ -223,7 +227,7 @@ C:/Program Files/edb/as15/bin/edb-postgres.exe "-D" "C:\Program Files\edb\as15\d 14. If you would like the server to be controlled by a Services utility you will need to stop it with the pg_ctl utility and start it again in your Services utility, for example Services(Local) in Windows or systemctl in UNIX. -15. After you have started the service with whichever utility you choose, login to your EDB database and check that the restore operation recovered the data. +15. After you have started the service with your utility of choice, login to your EDB database and check that the restore operation recovered the data. ## Known Issues FSBaseBackupSet Incremental or Point-In-Time(PITR) Restore has issues with Postgres and EDB Postgres Advanced Server versions 13 and onward. The behavior is due to a change that was made in Postgres version 13. From the release notes, `Generate an error if recovery does not reach the specified recovery target`. While Commvault does provide a time target for the recovery, the recovery is performed entirely by Postgres and Postgres does not know how to reach that time target, therefore it fails. This can happen where there are no transactions between backup jobs. A workaround for this solution is to always introduce a transaction scenario, such as a create and drop database, before doing a log backup. Another workaround is to use `recovery_target_lsn` in the postgresql.conf file instead of uisng `recovery_target_time`. Commvault is aware of this error on their side and is working on how to mitigate from their end. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx new file mode 100644 index 00000000000..303d6c2bb43 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx @@ -0,0 +1,42 @@ +--- +title: 'Support and Logging Details' +description: 'Details of the support process and logging information' +--- + +## Support + +Technical support for the use of these products is provided by both EDB and Commvault. A proper support contract is required to be in place at both EDB and Commvault. A support ticket can be opened on either side to start the process. If it is determined through the support ticket that resources from the other vendor is required, the customer should open a support ticket with that vendor through normal support channels. This will allow both companies to work together to help the customer as needed. + +## Logging + +**EDB Postgres Advanced Server Logs:** + +Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance and from here you can navigate to `log`, `current_logfiles` or you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs. + +**EDB Postgres Extended Server Logs** + +Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance and from here you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options. An example of the full path to view EDB Postgres Extended logs: `/var/lib/edb-pge/15/data/log`. + +**PostgreSQL Server Logs** + +The default log directories for PostgreSQL logs vary depending on the operating system: + +- Debian-based system: `/var/log/postgresql/postgresql-x.x.main.log. X.x.` + +- Red Hat-based system: `/var/lib/pgsql/data/pg_log` + +- Windows: `C:\Program Files\PostgreSQL\9.3\data\pg_log` + +** Commvault Logs** + +Commvault logs can be found a few ways. A first way is within the Content Store directory/folder in the Commvault folder on your system. For example if on a Windows system the Log File path would be `C:\Program Files\Commvault\ContentStore\LogFiles` where you can then see all of the differnt types of logs Commvault collects. + +You can also gather some job specific logs within the Commvault interface. + +1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to `Jobs > Job History`. + +2. Find the specific job you would like to view logs for and click on the `...` beside that job. + +3. Select `View Logs`. + + ![View Job Logs](Images/CommvaultViewLogsForJob.png) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/CommvaultViewLogsForJob.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/CommvaultViewLogsForJob.png new file mode 100644 index 00000000000..ed1093daafa --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/CommvaultViewLogsForJob.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db6a73932cd532dad2bef06a09ba99f4e7c8184ae74ce204e2fab6747e270333 +size 1146108 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreDatabases.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreDatabases.png new file mode 100644 index 00000000000..e537f6ca6af --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreDatabases.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:913d3eb2f127a84517ddab7039323da6ff2ac3eb67ec05a84a94cb993c40f6bf +size 87505 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreOptions.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreOptions.png new file mode 100644 index 00000000000..ae4a2a7023d --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreOptions.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2827c237d4db8cb80a94b996c367c34e26df54a0d9447b1334055bf9ca04791 +size 755537 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx index c4c8905d918..87c365f7f4b 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx @@ -9,3 +9,5 @@ directoryDefaults:

EDB GlobalConnect Technology Partner Implementation Guide

Commvault Backup & Recovery

+ +

This document is intended to augment each vendor’s product documentation to guide you in getting the products working together. It isn't intended to show the optimal configuration for the certified integration.

\ No newline at end of file From c8eb29148ce1802b6489bf37768ac19b84d1c5d6 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Tue, 22 Aug 2023 16:55:52 -0400 Subject: [PATCH 018/223] Error Edits --- .../05-UsingCommvaultBackupandRecovery.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index 250f31681f8..16152ba8b46 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -1,8 +1,6 @@ --- title: 'Using' -description: 'Walkthroughs of multiple Commvault Backup & Recovery usage scenarios' -redirects: - - /partner_docs/CommVaultGuide/05-UsingCommvaultBackupandRecovery/ +description: 'Walkthrough of example usage scenarios' --- You can back up and restore an EDB database using Commvault Backup & Recovery. From c6f18cf4a6333c3bd453d422e0022ed848e94e32 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Wed, 23 Aug 2023 09:37:29 -0400 Subject: [PATCH 019/223] More Edits --- .../CommvaultBackupandRecovery/02-PartnerInformation.mdx | 4 ++-- .../CommvaultBackupandRecovery/03-SolutionSummary.mdx | 2 +- .../04-ConfiguringCommvaultBackupandRecovery.mdx | 2 +- .../05-UsingCommvaultBackupandRecovery.mdx | 8 ++++---- .../06-CertificationEnvironment.mdx | 2 +- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx index 9ec0f28b705..abb1dc20c75 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx @@ -1,6 +1,6 @@ --- title: 'Partner information' -description: 'Details for Commvault Backup & Recovery' +description: 'Details of the Partner' --- |   |   | @@ -8,5 +8,5 @@ description: 'Details for Commvault Backup & Recovery' | **Partner Name** | Commvault | | **Partner product** | Commvault Backup & Recovery | | **Website** | https://www.commvault.com/ | -| **Version** | Commvault Backup & Recovery 11.24 | +| **Version** | Commvault Backup & Recovery 11.32 | | **Product description** | Wherever your data resides, ensure availability by way of a single interface with Commvault Backup & Recovery. It offers domprehensive workload coverage, files, apps, and databases, including EDB Postgres Advanced Server and EDB Postgres Extended Server, from a single extensible platform and user interface. Commvault Backup & Recovery provides a comprehensive backup and archiving solution for your trusted recovery, ransomware protection, and security. | diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx index 4c81ede5ab6..0839f8fc321 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx @@ -1,6 +1,6 @@ --- title: 'Solution summary' -description: 'Brief explanation of the solution and its purpose' +description: 'Explanation of the solution and its purpose' --- Commvault enables your business to streamline management of its continuously evolving data environment, whether the data is on premises or in the cloud. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx index 5e629a4d158..a04f7e337ca 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx @@ -1,6 +1,6 @@ --- title: 'Configuring' -description: 'Walkthrough of configuring Commvault Backup & Recovery' +description: 'Walkthrough of configuring the integration' redirects: - /partner_docs/CommVaultGuide/04-ConfiguringCommvaultBackupandRecovery/ --- diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index 16152ba8b46..9fcd267d26c 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -187,11 +187,11 @@ A file system backup backs up data that resides on a Windows or UNIX computer. #### Restoring FSBasedBackupSet Full Backup Backed up data can be restored for a subclient or an entire backup set with either an in-place restore, out-of-place restore or for a Linux file server to a standalone file server. -1. Ensure that your EDB Postgres Advanced Server instance is stopped +1. Ensure that your EDB Postgres Advanced Server instance is stopped. 2. Delete or rename the WAL directory and data directory. -3. From the navigation pane, go to `Protect > Databases`. +3. From the Commvault navigation pane, go to `Protect > Databases`. 4. Click the instance you want to restore. @@ -213,7 +213,7 @@ Backed up data can be restored for a subclient or an entire backup set with eith 11. A Job will be created to restore the backup. -12. When the Restore has completed successfully Commvault will automatically start the server using the pg_ctl utility. +12. When the Restore has completed successfully, Commvault will automatically start the server using the pg_ctl utility. 13. You can check that the server was started successfully with a command like, `"C:\Program Files\edb\as15\bin\pg_ctl" -U enterprisedb status -D "C:\Program Files\edb\as15\data"` and it should return a message that the server is running. @@ -228,4 +228,4 @@ C:/Program Files/edb/as15/bin/edb-postgres.exe "-D" "C:\Program Files\edb\as15\d 15. After you have started the service with your utility of choice, login to your EDB database and check that the restore operation recovered the data. ## Known Issues -FSBaseBackupSet Incremental or Point-In-Time(PITR) Restore has issues with Postgres and EDB Postgres Advanced Server versions 13 and onward. The behavior is due to a change that was made in Postgres version 13. From the release notes, `Generate an error if recovery does not reach the specified recovery target`. While Commvault does provide a time target for the recovery, the recovery is performed entirely by Postgres and Postgres does not know how to reach that time target, therefore it fails. This can happen where there are no transactions between backup jobs. A workaround for this solution is to always introduce a transaction scenario, such as a create and drop database, before doing a log backup. Another workaround is to use `recovery_target_lsn` in the postgresql.conf file instead of uisng `recovery_target_time`. Commvault is aware of this error on their side and is working on how to mitigate from their end. +FSBaseBackupSet Incremental or Point-In-Time(PITR) Restore has issues with Postgres and EDB Postgres Advanced Server versions 13 and onward. The behavior is due to a change that was made in Postgres version 13. From the release notes, `Generate an error if recovery does not reach the specified recovery target`. While Commvault does provide a time target for the recovery, the recovery is performed entirely by Postgres and Postgres does not know how to reach that time target, therefore it fails. This can happen when there are no transactions between backup jobs. A workaround for this solution is to always introduce a transaction scenario, such as a create and drop database, before doing a log backup. Another workaround is to use `recovery_target_lsn` in the postgresql.conf file instead of uisng `recovery_target_time`. Commvault is aware of this error on their side and is working on how to mitigate from their end. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx index a0f30af3cd0..772fe4e5b5c 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx @@ -1,6 +1,6 @@ --- title: 'Certification environment' -description: 'Overview of the certification environment used in the certification of Commvault Backup & Recovery' +description: 'Overview of the certification environment' --- |   |   | From 5a03d531050291498bc5a2c7825b75d03b34a865 Mon Sep 17 00:00:00 2001 From: Lenz Grimmer Date: Wed, 23 Aug 2023 18:15:31 +0200 Subject: [PATCH 020/223] Update README.md, add and fix links in PGD docs Minor improvements to `README.md`. Add link to the OpenTelemetry project in the OpenTelemetry chapter. Fix broken links in the Monitoring through SQL chapter. Signed-off-by: Lenz Grimmer --- README.md | 6 +++--- product_docs/docs/pgd/5/monitoring/otel.mdx | 2 +- product_docs/docs/pgd/5/monitoring/sql.mdx | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 569ae835259..9a659fcd2f6 100644 --- a/README.md +++ b/README.md @@ -45,7 +45,7 @@ At this point you have a couple options. 1. Run `npm run start`. The application will start in the background and take a few minutes to load. -1. You can view logs and monitor the startup process by running `npm run logs`. Once it's finished it can be accessed at `http://localhost:8000/`. +1. You can view logs and monitor the startup process by running `npm run logs`. Once it's finished it can be accessed at [http://localhost:8000/](http://localhost:8000). #### Additional Commands and Options for the Docker Environment @@ -63,7 +63,7 @@ At this point you have a couple options. If you find that the container crashes frequently or see that your container has exited with code 137, increasing the Docker memory should help. Allocating at least 4GB is recommended. -1. open Docker Desktop +1. Open Docker Desktop 1. Go to Preferences (gear icon in the top right corner) @@ -283,7 +283,7 @@ If you need to setup a redirect from Docs 1.0 to Docs 2.0 manually, this is the # MDX Format -Documentation must be formatted as an [MDX file](https://www.gatsbyjs.com/docs/mdx/writing-pages/) with the `.mdx` extension. MDX is a superset of [Markdown](https://www.markdownguide.org/). +Documentation must be formatted as an [MDX file](https://www.gatsbyjs.com/docs/how-to/routing/mdx/) with the `.mdx` extension. MDX is a superset of [Markdown](https://www.markdownguide.org/). See [What is MDX?](https://mdxjs.com/docs/what-is-mdx/) for a detailed explanation of the format. ## Frontmatter diff --git a/product_docs/docs/pgd/5/monitoring/otel.mdx b/product_docs/docs/pgd/5/monitoring/otel.mdx index ca7df3a644d..c33fb9ec965 100644 --- a/product_docs/docs/pgd/5/monitoring/otel.mdx +++ b/product_docs/docs/pgd/5/monitoring/otel.mdx @@ -3,7 +3,7 @@ title: OpenTelemetry integration --- You can configure EDB Postgres Distributed to report monitoring information -as well as traces to the OpenTelemetry collector. +as well as traces to the [OpenTelemetry](https://opentelemetry.io/) collector. EDB Postgres Distributed OTEL collector fills several resource attributes. These are attached to all metrics and traces: diff --git a/product_docs/docs/pgd/5/monitoring/sql.mdx b/product_docs/docs/pgd/5/monitoring/sql.mdx index 0a7f7d64719..36ac35396c8 100644 --- a/product_docs/docs/pgd/5/monitoring/sql.mdx +++ b/product_docs/docs/pgd/5/monitoring/sql.mdx @@ -113,7 +113,7 @@ You can use another view for monitoring of outgoing replication activity: - [`bdr.node_replication_rates`](/pgd/latest/reference/catalogs-visible/#bdrnode_replication_rates) for monitoring outgoing replication -The []`bdr.node_replication_rates`](/pgd/latest/reference/catalogs-visible/#bdrnode_replication_rates) view gives an overall picture of the outgoing +The [`bdr.node_replication_rates`](/pgd/latest/reference/catalogs-visible/#bdrnode_replication_rates) view gives an overall picture of the outgoing replication activity along with the catchup estimates for peer nodes, specifically. @@ -152,7 +152,7 @@ view. !!! Note This catalog is present only when the bdr-enterprise extension is installed. -Administrators can query `[`bdr.node_slots`](/pgd/latest/reference/catalogs-visible/#bdrnode_slots) for outgoing replication from the +Administrators can query [`bdr.node_slots`](/pgd/latest/reference/catalogs-visible/#bdrnode_slots) for outgoing replication from the local node. It shows information about replication status of all other nodes in the group that are known to the current node as well as any additional replication slots created by PGD on the current node. From a6f87fbb2e82627f504e77c4022ec8d96a55e741 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 23 Aug 2023 14:22:34 -0400 Subject: [PATCH 021/223] BigAnimal: clarifying language for listing valid values for properties in config file --- .../docs/biganimal/release/reference/cli/managing_clusters.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index b46c2d00abd..f0065f0c1fa 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -121,7 +121,7 @@ To create the cluster using the sample configuration file `config_file.yaml`: biganimal cluster create --config-file "./config_file.yaml" ``` -To query an enumeration of valid values for the BigAnimal and cloud service provider-related properties, CLI provides a series of subcommands. For example, you can use `cluster show-architectures` to list all cloud architectures available to your current login account: +To view valid values you can use in the configuration file for BigAnimal and cloud service provider-related properties, the CLI provides a series of cluster subcommands. For example, you can use `cluster show-architectures` to list all BigAnimal database architectures available within your cloud service provider account: ```shell biganimal cluster show-architectures From 5dbc5bad1c7cfe566adfd4b69b6cb0b8fdcae01c Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Wed, 23 Aug 2023 15:25:17 -0400 Subject: [PATCH 022/223] Postgres Add --- .../CommvaultBackupandRecovery/02-PartnerInformation.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx index abb1dc20c75..a630a37e94f 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx @@ -9,4 +9,4 @@ description: 'Details of the Partner' | **Partner product** | Commvault Backup & Recovery | | **Website** | https://www.commvault.com/ | | **Version** | Commvault Backup & Recovery 11.32 | -| **Product description** | Wherever your data resides, ensure availability by way of a single interface with Commvault Backup & Recovery. It offers domprehensive workload coverage, files, apps, and databases, including EDB Postgres Advanced Server and EDB Postgres Extended Server, from a single extensible platform and user interface. Commvault Backup & Recovery provides a comprehensive backup and archiving solution for your trusted recovery, ransomware protection, and security. | +| **Product description** | Wherever your data resides, ensure availability by way of a single interface with Commvault Backup & Recovery. It offers domprehensive workload coverage, files, apps, and databases, including EDB Postgres Advanced Server, EDB Postgres Extended Server and PostgreSQL Server, from a single extensible platform and user interface. Commvault Backup & Recovery provides a comprehensive backup and archiving solution for your trusted recovery, ransomware protection, and security. | From 9e08eb987be951de8a66e54b0711ed86af74ee89 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Wed, 23 Aug 2023 15:26:06 -0400 Subject: [PATCH 023/223] PG Edit --- .../CommvaultBackupandRecovery/02-PartnerInformation.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx index a630a37e94f..d6abe7d2c7b 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx @@ -9,4 +9,4 @@ description: 'Details of the Partner' | **Partner product** | Commvault Backup & Recovery | | **Website** | https://www.commvault.com/ | | **Version** | Commvault Backup & Recovery 11.32 | -| **Product description** | Wherever your data resides, ensure availability by way of a single interface with Commvault Backup & Recovery. It offers domprehensive workload coverage, files, apps, and databases, including EDB Postgres Advanced Server, EDB Postgres Extended Server and PostgreSQL Server, from a single extensible platform and user interface. Commvault Backup & Recovery provides a comprehensive backup and archiving solution for your trusted recovery, ransomware protection, and security. | +| **Product description** | Wherever your data resides, ensure availability by way of a single interface with Commvault Backup & Recovery. It offers domprehensive workload coverage, files, apps, and databases, including EDB Postgres Advanced Server, EDB Postgres Extended Server and PostgreSQL, from a single extensible platform and user interface. Commvault Backup & Recovery provides a comprehensive backup and archiving solution for your trusted recovery, ransomware protection, and security. | From 2ea4d89f018fee786c989a8fd1c861108c2839d7 Mon Sep 17 00:00:00 2001 From: kunliuedb <95676424+kunliuedb@users.noreply.github.com> Date: Tue, 4 Jul 2023 16:18:21 +0800 Subject: [PATCH 024/223] Update import_data.mdx --- .../release/free_trial/detail/experiment/import_data.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/free_trial/detail/experiment/import_data.mdx b/product_docs/docs/biganimal/release/free_trial/detail/experiment/import_data.mdx index fbc00dbd960..fea2f96b028 100644 --- a/product_docs/docs/biganimal/release/free_trial/detail/experiment/import_data.mdx +++ b/product_docs/docs/biganimal/release/free_trial/detail/experiment/import_data.mdx @@ -7,7 +7,7 @@ PostgreSQL includes a variety of ways to import data. Here, we'll show how to im For this demonstration, we're going to import batter data from the [Baseball Databank](https://github.com/chadwickbureau/baseballdatabank), which is in CSV form. While it's easy to import the data using [PostgreSQL's COPY command](https://www.postgresql.org/docs/current/sql-copy.html), we'll need to first define a table to put that data into. -We're going to [add a database](/biganimal/latest/using_cluster/01_postgres_access/#one-database-with-one-application) called "baseball," which we'll populate with some Major League Baseball statistics. +We're going to add a database called "baseball," which we'll populate with some Major League Baseball statistics. ```sql create database baseball; From ccb443bf970b0f226f468c6a7f9a81a3a7b01c72 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 23 Aug 2023 17:03:56 -0400 Subject: [PATCH 025/223] BigAnimal: removed duplicated sections --- .../reference/cli/managing_clusters.mdx | 133 ------------------ 1 file changed, 133 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index b46c2d00abd..a866f5b2a69 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -278,139 +278,6 @@ To restore a deleted cluster, use the `--from-deleted` flag in the command. You can restore a cluster in a single cluster to a primary/standby high-availability cluster and vice versa. You can restore a distributed high-availability cluster only to a cluster using the same architecture. !!! -### Get cluster connection information - -To use your BigAnimal cluster, you first need to get your cluster's connection information. To get your cluster's connection information, use the `cluster show-connection` command: - -```shell -biganimal cluster show-connection \ - --name "my-biganimal-cluster" \ - --provider "azure" \ - --region "eastus" -__OUTPUT__ -┌─────────────┬──────────────────────────────────────────────────────────────────────────────────────────┐ -│ Access Type │ Connection String │ -├─────────────┼──────────────────────────────────────────────────────────────────────────────────────────┤ -│ read-write │ postgresql://edb_admin@p-gxhkfww1fe.30glixgayvwhtmn3.enterprisedb.network:5432/edb_admin │ -│ read-only │ Disabled │ -└─────────────┴──────────────────────────────────────────────────────────────────────────────────────────┘ -``` - -!!!tip -You can query the complete connection information with other output formats, like JSON or YAML. For example: - -```shell -biganimal cluster show-connection \ - --name "my-biganimal-cluster" \ - --provider "azure" \ - --region "eastus" \ - --output "json" -``` -!!! - -### Update cluster - -After the cluster is created, you can update attributes of the cluster, including both the cluster’s profile and its deployment architecture. You can update the following attributes: - -- Cluster name -- Password of administrator account -- Cluster architecture -- Number of standby replicas -- Instance type of cluster -- Instance volume properties -- Networking -- Allowed IP list -- Postgres database configuration -- Volume properties, size, IOPS -- Retention period -- Read-only workloads -- IAM authentication - -For example, to set the public allowed IP range list, use the `--cidr-blocks` flag: - -```shell -./biganimal cluster update --name "my-biganimal-cluster" --provider "azure" \ - --region "eastus" \ - --cidr-blocks "9.9.9.9/28=Traffic from App A" -``` - -To check whether the setting took effect, use the `cluster show` command, and view the detailed cluster information output in JSON format. For example: - -```shell -biganimal cluster show --name "my-biganimal-cluster" --provider "azure" \ - --region "eastus" \ - --output "json" \ -| jq '.[0].allowIpRangeMap' -__OUTPUT__ -[ - [ - "9.9.9.9/28", - "Traffic from App A" - ] -] -``` - -### Update the Postgres configuration of a cluster - -To update the Postgres configuration of a BigAnimal cluster directly from the CLI: - -```shell -biganimal cluster update --id "p-gxhkfww1fe" \ - --pg-config "application_name=ba_test_app,array_nulls=false" -__OUTPUT__ -Update Cluster operation is started -Cluster ID is "p-gxhkfww1fe" -``` -To specify multiple configurations, you can use multiple `--pg-config` flags or include multiple configuration settings as a key-value array string separated by commas in one `--pg-config` flag. If a Postgres setting contains a comma, you need to specify it with a separate `--pg-config` flag. - -!!! Note -You can update the cluster architecture with the `--cluster-architecture` flag. The only supported scenario is to update a single-node cluster to a primary/standby high-availability cluster. -!!! - -### Delete a cluster - -To delete a cluster you no longer need, use the `cluster delete` command. For example: - -```shell -biganimal cluster delete \ - --name "my-biganimal-cluster" \ - --provider "azure" \ - --region "eastus" -``` - -You can list all deleted clusters using the `show-deleted-clusters` command and restore them from their history backups as needed. - - -### Restore a cluster -BigAnimal continuously backs up your PostgreSQL clusters. Using the CLI, you can restore a cluster from its backup to any point in time as long as the backups are retained in the backup storage. The restored cluster can be in another region and with different configurations. You can specify new configurations in the `cluster restore` command. For example: - -```shell -biganimal cluster restore\ - --name "my-biganimal-cluster" \ - --provider "azure" \ - --region "eastus" \ - --password "mypassword@123" \ - --new-name "my-biganimal-cluster-restored" \ - --new-region="eastus2" \ - --cluster-architecture "single" \ - --instance-type "azure:Standard_E2s_v3" \ - --volume-type "azurepremiumstorage" \ - --volume-property "P1" \ - --networking "public" \ - --cidr-blocks="10.10.10.10/27=Traffic from App B" \ - --restore-point "2022-01-26T15:04:05+0800" \ - --backup-retention-period "2w" \ - --read-only-workloads: "true" -``` - -The password for the restored cluster is mandatory. The other parameters, if not specified, inherit the source database's settings. - -To restore a deleted cluster, use the `--from-deleted` flag in the command. - -!!! Note -You can restore a cluster in a single cluster to a primary/standby high-availability cluster and vice versa. You can restore a distributed high-availability cluster only to a cluster using the same architecture. -!!! - ## Managing distributed high-availability clusters From cb7682a29d04d99918c07dd4e777a87fb70b56c0 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Wed, 23 Aug 2023 17:54:03 -0400 Subject: [PATCH 026/223] Review Edits --- ...-ConfiguringCommvaultBackupandRecovery.mdx | 33 ++++++++++--------- .../05-UsingCommvaultBackupandRecovery.mdx | 24 +++++++------- 2 files changed, 30 insertions(+), 27 deletions(-) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx index a04f7e337ca..d8d7d27b376 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx @@ -7,18 +7,21 @@ redirects: Implementing Commvault Backup & Recovery with an EDB database requires the following components: -- EDB Postgres Advanced Server or EDB Postgres Extended Server +- EDB Postgres Advanced Server, EDB Postgres Extended Server or PostgreSQL Server - Commvault Backup & Recovery software +!!! Note + We refer to the EDB Postgres Advanced Server, EDB Postgres Extended Server, and PostgreSQL Server products as Postgres distribution. The specific distribution type depends on your needs and preferences. + ## Prerequisites -- A running EDB Postgres Advanced Server or EDB Postgres Extended Server instance +- A running Postgres distribution - Commvault Backup & Recovery installed -- EDB Postgres Advanced Server or EDB Postgres Extended Server application path and library directory path, for example, `c:\Program Files\edb\as13\bin` and `c:\Program Files\edb\as13\lib` -- The login credentials used to access the EDB Postgres Advanced Server or EDB Postgres Extended Server database -- EDB Postgres Advanced Server or EDB Postgres Extended Server archive log directory configured +- Postgres distribution application path and library directory path, for example, `c:\Program Files\edb\as15\bin` and `c:\Program Files\edb\as15\lib` +- The login credentials used to access the Postgres distribution database +- Postgres distribution archive log directory configured -## Configure Commvault Backup & Recovery for EDB Postgres Advanced Server or EDB Postgres Extended Server +## Configure Commvault Backup & Recovery for Postgres distribution ### Set up a disk storage pool @@ -42,11 +45,11 @@ Next, create a server backup plan in Core Setup. To create a server backup plan ![Creating a Server Backup Plan in Core Setup](Images/BackupPlanConf.png) -### Install a client on an EDB database +### Install a client on a Postgres distribution database 1. From the Navigation pane of the Commvault Backup & Recovery's Command Center, select **Protect > Databases**. 2. Select **Add server**. -3. Select the database type for EDB database, which in this case is **PostgreSQL**. +3. Select the database type for the Postgres distribution database, which in this case is **PostgreSQL**. ![Creating a Server Backup Plan in Core Setup](Images/ServerAdd1.png) @@ -66,7 +69,7 @@ Next, create a server backup plan in Core Setup. To create a server backup plan ![Creating a Server Backup Plan in Core Setup](Images/ServerAdd6.png) -### Configure the EDB database instances to back up and protect +### Configure the Postgres distribution instances to backup and protect 1. From the navigation pane, select **Protect > Databases > DB Instances**. 2. Select **Add instance**, and then select **PostgreSQL**. @@ -74,18 +77,18 @@ Next, create a server backup plan in Core Setup. To create a server backup plan ![Creating a Server Backup Plan in Core Setup](Images/CreateInstance1.png) 3. From the **Server name** list, select the server where you want to create the new instance. -4. In the **Instance Name** box, enter the EDB database instance name. -5. From the **Plan** list, select the server plan you set up for use with your EDB database. +4. In the **Instance Name** box, enter the Postgres distribution database instance name. +5. From the **Plan** list, select the server plan you set up for use with your Postgres distribution database. 6. Under **Connection details**, enter the following information. - - In the **Database user** box, enter the user name to access the EDB database instance. - - In the **Password** box, enter the EDB database user account password. - - In the **Port** box, enter the port to open the communication between the EDB database and the clients. + - In the **Database user** box, enter the user name to access the Postgres distribution database instance. + - In the **Password** box, enter the Postgres distribution database user account password. + - In the **Port** box, enter the port to open the communication between the Postgres distribution and the clients. - In the **Maintenance DB** box, enter the name of a system database that's used as a maintenance database. - In the **PostgreSQL** section, enter paths for **Binary Directory**, **Lib Directory**, and **Archive Log Directory**. ![Creating a Server Backup Plan in Core Setup](Images/CreateInstance2.png) - Your database instance to back up is now created. You can view its configuration. + Your Postgres distribution database instance to back up is now created. You can view its configuration. ![Creating a Server Backup Plan in Core Setup](Images/CreateInstance3.png) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index 9fcd267d26c..f2fff4a148b 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -3,23 +3,23 @@ title: 'Using' description: 'Walkthrough of example usage scenarios' --- -You can back up and restore an EDB database using Commvault Backup & Recovery. +You can back up and restore a Postgres distribution database using Commvault Backup & Recovery. ## Using Commvault Backup & Recovery -Commvault provides two methods of taking the backup from an EDB database and restoring it: +Commvault provides two methods of taking the backup from a Postgres distribution database and restoring it: - DumpBasedBackupSet backup and restore - FSBasedBackupSet backup and restore !!! Note - At this time there is a known issue with FSBased Incremental/PITR Restore that does not allow for proper restoration of the database. See the known issues section of the guide for more information. + At this time there is a known issue with FSBased Incremental/PITR Restore that does not allow for proper restoration of the database using the defined process. See the known issues section of the guide for more information and workaround. -## DumpBasedBackupSet Backup and Restore +### DumpBasedBackupSet Backup and Restore Dump-based backup uses the pg_dump utility to take the backup. -#### Taking DumpBasedBackupSet backup +## Taking DumpBasedBackupSet backup 1. Open the Commvault Backup & Recovery's Command Center. From the navigation pane, select **Protect > Databases**. @@ -51,7 +51,7 @@ Dump-based backup uses the pg_dump utility to take the backup. ![Backup Job](Images/Dumpbackup7.png) -#### Restoring DumpBasedBackupSet backup +## Restoring DumpBasedBackupSet backup You can use DumpBasedBackupSet to restore the individual databases. @@ -77,7 +77,7 @@ You can use DumpBasedBackupSet to restore the individual databases. ![Restore Job](Images/Dumprestore5.png) -8. When the Restore has completed successfully, log in to the EDB database and check that the restore operation recovered the data. This example connected to an EDB Postgres Advanced Server instance: +8. When the Restore has completed successfully, log in to the Postgres distribution database and check that the restore operation recovered the data. This example connected to an EDB Postgres Advanced Server instance: ```bash edb=# @@ -158,10 +158,10 @@ epas13_test=# ``` -## FSBasedBackupSet Backup and Restore +### FSBasedBackupSet Backup and Restore A file system backup backs up data that resides on a Windows or UNIX computer. -### Taking FSBasedBackupSet Backup +## Taking FSBasedBackupSet Backup 1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to `Protect > Databases`. 2. Click on the required instance. @@ -184,10 +184,10 @@ A file system backup backs up data that resides on a Windows or UNIX computer. ![FSBased Backup Job Details](Images/FSBasedBackupJobDetails.png) -#### Restoring FSBasedBackupSet Full Backup +## Restoring FSBasedBackupSet Full Backup Backed up data can be restored for a subclient or an entire backup set with either an in-place restore, out-of-place restore or for a Linux file server to a standalone file server. -1. Ensure that your EDB Postgres Advanced Server instance is stopped. +1. Ensure that your Postgres distribution instance is stopped. 2. Delete or rename the WAL directory and data directory. @@ -228,4 +228,4 @@ C:/Program Files/edb/as15/bin/edb-postgres.exe "-D" "C:\Program Files\edb\as15\d 15. After you have started the service with your utility of choice, login to your EDB database and check that the restore operation recovered the data. ## Known Issues -FSBaseBackupSet Incremental or Point-In-Time(PITR) Restore has issues with Postgres and EDB Postgres Advanced Server versions 13 and onward. The behavior is due to a change that was made in Postgres version 13. From the release notes, `Generate an error if recovery does not reach the specified recovery target`. While Commvault does provide a time target for the recovery, the recovery is performed entirely by Postgres and Postgres does not know how to reach that time target, therefore it fails. This can happen when there are no transactions between backup jobs. A workaround for this solution is to always introduce a transaction scenario, such as a create and drop database, before doing a log backup. Another workaround is to use `recovery_target_lsn` in the postgresql.conf file instead of uisng `recovery_target_time`. Commvault is aware of this error on their side and is working on how to mitigate from their end. +FSBaseBackupSet Incremental or Point-In-Time(PITR) Restore has issues with PostgreSQL server, EDB Postgres Advanced Server and EDB Postgres Extended versions 13 and onward. The behavior is due to a change that was made in Postgres version 13. From the release notes, `Generate an error if recovery does not reach the specified recovery target`. While Commvault does provide a time target for the recovery, the recovery is performed entirely by Postgres and Postgres does not know how to reach that time target, therefore it fails. This can happen when there are no transactions between backup jobs. A workaround for this solution is to always introduce a transaction scenario, such as a create and drop database, before doing a log backup. Another workaround is to use `recovery_target_lsn` in the postgresql.conf file instead of uisng `recovery_target_time`. Commvault is aware of this error on their side and is working on a fix. From 1e1ec10b3e257e03907c7b3496d15f693d4e40b8 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 24 Aug 2023 12:08:12 +0530 Subject: [PATCH 027/223] Added the configure options as per PEM-4905 --- .../configuring_the_pem_server_on_linux.mdx | 30 +++++++++++-------- 1 file changed, 18 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/pem/9/installing/configuring_the_pem_server_on_linux.mdx b/product_docs/docs/pem/9/installing/configuring_the_pem_server_on_linux.mdx index 370ef1e2387..1372d7d887e 100644 --- a/product_docs/docs/pem/9/installing/configuring_the_pem_server_on_linux.mdx +++ b/product_docs/docs/pem/9/installing/configuring_the_pem_server_on_linux.mdx @@ -22,18 +22,24 @@ The PEM server package includes a script (`configure-pem-server.sh`) to help aut When invoking the script, you can include command line options to specify configuration properties. The script prompts you for values that you omit on the command line. The accepted options are: -| Option | Description | -| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `-acp` | Defines PEM agent certificate path. The default is `/root/.pem`. | -| `-ci` | CIDR-formatted network address range that agents connect to the server from, to be added to the server's `pg_hba.conf` file, for example, `192.168.1.0/24`. The default is `0.0.0.0/0`. | -| `-dbi` | The directory for the database server installation, for example, `/usr/edb/as12` for EDB Postgres Advanced Server or `/usr/pgsql-12` for PostgreSQL. | -| `-ds` | The unit file name of the PEM database server. For EDB Postgres Advanced Server, the default file name is `edb-as-12`. For PostgreSQL, it's `postgresql-12`. | -| `-ho` | The host address of the PEM database server. | -| `-p` | The port number of the PEM database server. | -| `-ps` | The service name of the pemagent. The default value is `pemagent`. | -| `-sp` | The superuser password of the PEM database server. This value is required. | -| `-su` | The superuser name of the PEM database server. | -| `-t` | The installation type: Specify `1` if the configuration is for web services and backend database, `2` if you're configuring web services, or `3` if you're configuring the backend database. If you specify `3`, the database must reside on the local host. | +| Option | Description | +| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `-acp` or `--pemagent-certificate-path` | Defines PEM agent certificate path. The default is `/root/.pem`. | +| `-ci` or `--cidr-address` | CIDR-formatted network address range that agents connect to the server from, to be added to the server's `pg_hba.conf` file, for example, `192.168.1.0/24`. The default is `0.0.0.0/0`. | +| `-dbi` or `--db-install-path` | The directory for the database server installation, for example, `/usr/edb/as12` for EDB Postgres Advanced Server or `/usr/pgsql-12` for PostgreSQL. | +| `-ds` or `--db-unitfile` | The unit file name of the PEM database server. For EDB Postgres Advanced Server, the default file name is `edb-as-12`. For PostgreSQL, it's `postgresql-12`. | +| `-ho` or `--host` | The host address of the PEM database server. | +| `-p` or `--port` | The port number of the PEM database server. | +| `-ps` or `--pemagent-servicename` | The service name of the pemagent. The default value is `pemagent`. | +| `-sp` or `--superpassword` | The superuser password of the PEM database server. This value is required. | +| `-su` or `--superuser` | The superuser name of the PEM database server. | +| `-au` or `--use-agent-user` | The option to provide the PEM agent user name. | +| `-t` or `--type` | The installation type: Specify `1` if the configuration is for web services and backend database, `2` if you're configuring web services, or `3` if you're configuring the backend database. If you specify `3`, the database must reside on the local host. | +| `-un` or `--uninstall-pem-server` | The option to uninstall the PEM server. | +| `-nhc` or `--no-hba-change` | The option to skip the changes done to `pg_hba.conf` and `pg_config` files. | +| `-uac` or `--use-agent-sslcert` | The option to reuse the existing agent SSL certificates while configuring the PEM server. | +| `-uak` or `--use-agent-sslkey` | The option to reuse the existing agent SSL key while configuring the PEM server. | +| `-h` or `--help` | The option to list all the available options while configuring the PEM server. | If you don't provide configuration properties on the command line, the script prompts you for values. When you invoke the script, choose from: From 09781637de096f0fee52cbbcda677f37b5a3e3f1 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 24 Aug 2023 12:09:20 +0530 Subject: [PATCH 028/223] Added the PEM 9.3.0 release notes --- .../pem/9/pem_rel_notes/930_rel_notes.mdx | 19 +++++++++++++++++++ .../docs/pem/9/pem_rel_notes/index.mdx | 1 + 2 files changed, 20 insertions(+) create mode 100644 product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx diff --git a/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx new file mode 100644 index 00000000000..1e01310c8ab --- /dev/null +++ b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx @@ -0,0 +1,19 @@ +--- +title: "Version 9.3.0" +--- + +New features, enhancements, bug fixes, and other changes in PEM 9.3.0 include: + +| Type | Description | +| ----------- | -------------------------------------------------------------------------------------------------| +| Enhancement | Added the functionality to delete all the existing alert while using the copy alert feature. | +| Enhancement | Added PostgreSQL and EPAS 16 support as a backend database server and monitoring server. | +| Enhancement | Added support to customize the default email templates. | +| Enhancement | Added the support to download the alert history report for agents and servers from the reports tab. | +| Enhancement | Added options to reuse the existing agent SSL certificates and key files while configuring the PEM server. | +| Bug Fix | Added the functionality to add/view ignore mount points in the agent REST API. | +| Bug Fix | Added the `hostaddr` body parameter to the server REST API. | +| Bug Fix | Removed the newline character in the alert details from the payload of Webhook. | +| Bug Fix | Added the support to allow the webhook endpoint registration without providing the client SSL certificates and key files or CA certificates using `allow_insecure_webhooks` parameter in the `agent.cfg` file. Also set `ssl_verifypeer` parameter to `false` while establishing the connection with webhook endpoint. | +| Bug Fix | Improved the error message for better user understanding of put/post server REST API. | +| Bug Fix | Fixed an issue related to the backup sizes displaying on the PEM's Barman dashbaord. | \ No newline at end of file diff --git a/product_docs/docs/pem/9/pem_rel_notes/index.mdx b/product_docs/docs/pem/9/pem_rel_notes/index.mdx index 778ae3c93c2..e7909211984 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/index.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/index.mdx @@ -13,6 +13,7 @@ The Postgres Enterprise Manager (PEM) documentation describes the latest version | Version | Release Date | Upstream Merges | Accessibility Conformance | | ------------------------- | ------------ | --------------------------------------------------------------------------| --------------------------------------------------------------------------------------------------- | +| [9.3.0](930_rel_notes) | 31 Aug 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | | [9.2.2](922_rel_notes) | 14 Jul 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | | [9.2.1](921_rel_notes) | 03 Jul 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | | [9.2.0](920_rel_notes) | 24 May 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | From 04a8919bb8e26a0ca022069105fc10777f8c6642 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 24 Aug 2023 07:46:24 -0400 Subject: [PATCH 029/223] Syntax Edits --- ...-ConfiguringCommvaultBackupandRecovery.mdx | 2 +- .../05-UsingCommvaultBackupandRecovery.mdx | 26 +++++++++---------- 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx index d8d7d27b376..db7372a2446 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx @@ -5,7 +5,7 @@ redirects: - /partner_docs/CommVaultGuide/04-ConfiguringCommvaultBackupandRecovery/ --- -Implementing Commvault Backup & Recovery with an EDB database requires the following components: +Implementing Commvault Backup & Recovery with an EDB Postgres Advanced Server, EDB Postgres Extended Server or PostgreSQL Server database requires the following components: - EDB Postgres Advanced Server, EDB Postgres Extended Server or PostgreSQL Server - Commvault Backup & Recovery software diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index f2fff4a148b..dc1974407d1 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -162,21 +162,21 @@ epas13_test=# A file system backup backs up data that resides on a Windows or UNIX computer. ## Taking FSBasedBackupSet Backup -1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to `Protect > Databases`. +1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to ***Protect > Databases***. 2. Click on the required instance. -3. In the `Backup sets` section, click on `FSBasedBackupSet` backup set. +3. In the ***Backup sets*** section, click on ***FSBasedBackupSet*** backup set. -4. In the `Database groups` section, click the database group that you want to back up. In this case it is `default`. +4. In the ***Database groups*** section, click the database group that you want to back up. In this case it is ***default***. -5. In the `Backup` section, click `Back up`. +5. In the ***Backup*** section, click ***Back up***. -6. Choose between a Full or Incremental backup in the `Select Backup Level` screen, this example chose an incremental backup. +6. Choose between a Full or Incremental backup in the ***Select Backup Level*** screen, this example chose an incremental backup. ![Select FSBased Backup Type](Images/SelectFSBasedBackupType.png) -7. A job will be created to take the backup, which you can view by clicking on the `Job ID` for that backup. +7. A job will be created to take the backup, which you can view by clicking on the ***Job ID*** for that backup. ![FSBased Backup Job](Images/FSBasedBackupJob.png) @@ -191,25 +191,25 @@ Backed up data can be restored for a subclient or an entire backup set with eith 2. Delete or rename the WAL directory and data directory. -3. From the Commvault navigation pane, go to `Protect > Databases`. +3. From the Commvault navigation pane, go to ***Protect > Databases***. 4. Click the instance you want to restore. -5. In the `Recovery Points` calender, select `FSBasedBackupSet`. +5. In the ***Recovery Points*** calender, select ***FSBasedBackupSet***. -6. Select a date where a full FSBasedBackupSet was taken and click `Restore`. +6. Select a date where a full FSBasedBackupSet was taken and click ***Restore***. -7. The `Backup Content` screen will display the databases to be restored, select the required database to restore or select all of them to restore all. +7. The ***Backup Content*** screen will display the databases to be restored, select the required database to restore or select all of them to restore all. ![FSBased Backup Restore Databases](Images/FSBasedFullRestoreDatabases.png) -8. Click `Restore`. +8. Click ***Restore***. -9. From the `Restore Options` screen, select where you want the restore to complete, in-place, out-of-place or restore to disk for a Linux server. +9. From the ***Restore Options*** screen, select where you want the restore to complete, in-place, out-of-place or restore to disk for a Linux server. ![FSBased Backup Restore Details](Images/FSBasedFullRestoreOptions.png) -10. Select the `Destination Server` and `Destination Instance` and click on submit. +10. Select the ***Destination Server*** and ***Destination Instance*** and click on submit. 11. A Job will be created to restore the backup. From af62fadb07b87f59598ecf4a5aca86c619159713 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 24 Aug 2023 08:21:36 -0400 Subject: [PATCH 030/223] Final syntax fix --- .../05-UsingCommvaultBackupandRecovery.mdx | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index dc1974407d1..876a5d237cf 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -162,21 +162,21 @@ epas13_test=# A file system backup backs up data that resides on a Windows or UNIX computer. ## Taking FSBasedBackupSet Backup -1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to ***Protect > Databases***. +1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to **Protect > Databases**. 2. Click on the required instance. -3. In the ***Backup sets*** section, click on ***FSBasedBackupSet*** backup set. +3. In the **Backup sets** section, click on **FSBasedBackupSet** backup set. -4. In the ***Database groups*** section, click the database group that you want to back up. In this case it is ***default***. +4. In the **Database groups** section, click the database group that you want to back up. In this case it is **default**. -5. In the ***Backup*** section, click ***Back up***. +5. In the **Backup** section, click **Back up**. -6. Choose between a Full or Incremental backup in the ***Select Backup Level*** screen, this example chose an incremental backup. +6. Choose between a Full or Incremental backup in the **Select Backup Level** screen, this example chose an incremental backup. ![Select FSBased Backup Type](Images/SelectFSBasedBackupType.png) -7. A job will be created to take the backup, which you can view by clicking on the ***Job ID*** for that backup. +7. A job will be created to take the backup, which you can view by clicking on the **Job ID** for that backup. ![FSBased Backup Job](Images/FSBasedBackupJob.png) @@ -191,25 +191,25 @@ Backed up data can be restored for a subclient or an entire backup set with eith 2. Delete or rename the WAL directory and data directory. -3. From the Commvault navigation pane, go to ***Protect > Databases***. +3. From the Commvault navigation pane, go to **Protect > Databases**. 4. Click the instance you want to restore. -5. In the ***Recovery Points*** calender, select ***FSBasedBackupSet***. +5. In the **Recovery Points** calender, select **FSBasedBackupSet**. -6. Select a date where a full FSBasedBackupSet was taken and click ***Restore***. +6. Select a date where a full FSBasedBackupSet was taken and click **Restore**. -7. The ***Backup Content*** screen will display the databases to be restored, select the required database to restore or select all of them to restore all. +7. The **Backup Content** screen will display the databases to be restored, select the required database to restore or select all of them to restore all. ![FSBased Backup Restore Databases](Images/FSBasedFullRestoreDatabases.png) -8. Click ***Restore***. +8. Click **Restore**. -9. From the ***Restore Options*** screen, select where you want the restore to complete, in-place, out-of-place or restore to disk for a Linux server. +9. From the **Restore Options** screen, select where you want the restore to complete, in-place, out-of-place or restore to disk for a Linux server. ![FSBased Backup Restore Details](Images/FSBasedFullRestoreOptions.png) -10. Select the ***Destination Server*** and ***Destination Instance*** and click on submit. +10. Select the **Destination Server** and **Destination Instance** and click on submit. 11. A Job will be created to restore the backup. From 9a5f74202f0c21ffbde21e0b598e9275aca15938 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Tue, 22 Aug 2023 16:17:57 +0100 Subject: [PATCH 031/223] All renumbered with no code involved Signed-off-by: Dj Walker-Morgan --- .../advanced_storage_pack/rel_notes/index.mdx | 2 +- .../ldap_sync/rel_notes/index.mdx | 2 +- .../pg_failover_slots/rel_notes/index.mdx | 2 +- .../pg_tuner/rel_notes/index.mdx | 4 +- .../query_advisor/rel_notes/index.mdx | 2 +- .../edb_plus/41/02_release_notes/index.mdx | 6 +- .../docs/efm/4/efm_rel_notes/index.mdx | 12 +- .../docs/epas/11/epas_rel_notes/index.mdx | 46 ++++---- .../docs/epas/12/epas_rel_notes/index.mdx | 34 +++--- .../docs/epas/13/epas_rel_notes/index.mdx | 26 ++--- .../docs/epas/14/epas_rel_notes/index.mdx | 18 +-- .../docs/epas/15/epas_rel_notes/index.mdx | 6 +- ...schema_objects_created_for_publication.mdx | 2 +- .../docs/eprs/7/eprs_rel_notes/index.mdx | 18 +-- .../2/hadoop_rel_notes/index.mdx | 16 +-- .../42.5.4.1/01_jdbc_rel_notes/index.mdx | 22 ++-- .../55/mtk_rel_notes/index.mdx | 20 ++-- .../5/mongo_rel_notes/index.mdx | 16 +-- .../2/mysql_rel_notes/index.mdx | 16 +-- .../ocl_connector/15/ocl_rel_notes/index.mdx | 6 +- .../12/01_odbc_rel_notes/index.mdx | 4 +- .../13/01_odbc_rel_notes/index.mdx | 10 +- .../pgbouncer/1/pgbouncer_rel_notes/index.mdx | 10 +- .../pgd/3.7/harp/01_release_notes/index.mdx | 24 ++-- product_docs/docs/pgd/4/rel_notes/index.mdx | 22 ++-- product_docs/docs/pgd/5/rel_notes/index.mdx | 8 +- .../docs/pge/15/release_notes/index.mdx | 4 +- .../docs/pgpool/4/pgpool_rel_notes/index.mdx | 10 +- .../postgis/3.2/01_release_notes/index.mdx | 8 +- .../1/rel_notes/index.mdx | 2 +- .../1/rel_notes/index.mdx | 104 +++++++++--------- 31 files changed, 241 insertions(+), 241 deletions(-) diff --git a/advocacy_docs/pg_extensions/advanced_storage_pack/rel_notes/index.mdx b/advocacy_docs/pg_extensions/advanced_storage_pack/rel_notes/index.mdx index 8dcbf2d9680..1802a3e9ad8 100644 --- a/advocacy_docs/pg_extensions/advanced_storage_pack/rel_notes/index.mdx +++ b/advocacy_docs/pg_extensions/advanced_storage_pack/rel_notes/index.mdx @@ -11,7 +11,7 @@ about the release that introduced the feature. | Version | Release Date | | --------------------------- | ------------ | -| [1.0.0](asp_1.0.0_rel_notes) | 2022 Nov 30 | +| [1.0.0](asp_1.0.0_rel_notes) | 30 Nov 2022 | diff --git a/advocacy_docs/pg_extensions/ldap_sync/rel_notes/index.mdx b/advocacy_docs/pg_extensions/ldap_sync/rel_notes/index.mdx index 8d55874c4a2..363bad1651c 100644 --- a/advocacy_docs/pg_extensions/ldap_sync/rel_notes/index.mdx +++ b/advocacy_docs/pg_extensions/ldap_sync/rel_notes/index.mdx @@ -11,7 +11,7 @@ about the release that introduced the feature. | Version | Release Date | | --------------------------- | ------------ | -| [1.0.0](ldap_sync_1.0.0_rel_notes) | 2022 Nov 30 | +| [1.0.0](ldap_sync_1.0.0_rel_notes) | 30 Nov 2022 | diff --git a/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/index.mdx b/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/index.mdx index 52e15d35198..4d6373b08ca 100644 --- a/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/index.mdx +++ b/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/index.mdx @@ -11,7 +11,7 @@ about the release that introduced the feature. | Version | Release Date | | --------------------------- | ------------ | -| [1.0.0](pg_failover_slots_1.0.0_rel_notes) | 2023 Mar 31 | +| [1.0.0](pg_failover_slots_1.0.0_rel_notes) | 31 Mar 2023 | diff --git a/advocacy_docs/pg_extensions/pg_tuner/rel_notes/index.mdx b/advocacy_docs/pg_extensions/pg_tuner/rel_notes/index.mdx index 0669deef032..1fcdf91696d 100644 --- a/advocacy_docs/pg_extensions/pg_tuner/rel_notes/index.mdx +++ b/advocacy_docs/pg_extensions/pg_tuner/rel_notes/index.mdx @@ -14,8 +14,8 @@ about the release that introduced the feature. | Version | Release Date | | --------------------------- | ------------ | -| [1.1.0](pg_tuner_1.1.0_rel_notes) | 2023 Feb 10 | -| [1.0.0](pg_tuner_1.0.0_rel_notes) | 2022 Nov 30 | +| [1.1.0](pg_tuner_1.1.0_rel_notes) | 10 Feb 2023 | +| [1.0.0](pg_tuner_1.0.0_rel_notes) | 30 Nov 2022 | diff --git a/advocacy_docs/pg_extensions/query_advisor/rel_notes/index.mdx b/advocacy_docs/pg_extensions/query_advisor/rel_notes/index.mdx index 8560ac96b8e..2cb1d75b6c1 100644 --- a/advocacy_docs/pg_extensions/query_advisor/rel_notes/index.mdx +++ b/advocacy_docs/pg_extensions/query_advisor/rel_notes/index.mdx @@ -11,7 +11,7 @@ about the release that introduced the feature. | Version | Release Date | | --------------------------- | ------------ | -| [1.0.0](query_advisor_1.0.0_rel_notes) | 2023 May 10 | +| [1.0.0](query_advisor_1.0.0_rel_notes) | 10 May 2023 | diff --git a/product_docs/docs/edb_plus/41/02_release_notes/index.mdx b/product_docs/docs/edb_plus/41/02_release_notes/index.mdx index dac25ecd895..5269d7c8505 100644 --- a/product_docs/docs/edb_plus/41/02_release_notes/index.mdx +++ b/product_docs/docs/edb_plus/41/02_release_notes/index.mdx @@ -13,6 +13,6 @@ The EDB\*Plus documentation describes the latest version of EDB\*Plus Version 41 | Version | Release Date | | ------------------------------------- | ------------ | -| [41.2.0](edbplus_41.2_rel_notes.mdx) | 2023 Aug 23 | -| [41.1.0](edbplus_41.1_rel_notes.mdx) | 2023 Apr 20 | -| [41.0.0](edbplus_41.0_rel_notes.mdx) | 2023 Feb 14 | +| [41.2.0](edbplus_41.2_rel_notes.mdx) | 23 Aug 2023 | +| [41.1.0](edbplus_41.1_rel_notes.mdx) | 20 Apr 2023 | +| [41.0.0](edbplus_41.0_rel_notes.mdx) | 14 Feb 2023 | diff --git a/product_docs/docs/efm/4/efm_rel_notes/index.mdx b/product_docs/docs/efm/4/efm_rel_notes/index.mdx index f63a2e6ede6..b25f4fe7c17 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/index.mdx +++ b/product_docs/docs/efm/4/efm_rel_notes/index.mdx @@ -9,14 +9,14 @@ about the release that introduced the feature. | Version | Release Date | | ------- | ------------ | -| [4.7](03_efm_47_rel_notes) | 2023 Jun 20 | -| [4.6](04_efm_46_rel_notes) | 2023 Feb 14 | -| [4.5](05_efm_45_rel_notes) | 2022 Aug 30 | -| [4.4](06_efm_44_rel_notes) | 2022 Jan 5 | +| [4.7](03_efm_47_rel_notes) | 20 Jun 2023| +| [4.6](04_efm_46_rel_notes) | 14 Feb 2023| +| [4.5](05_efm_45_rel_notes) | 30 Aug 2022| +| [4.4](06_efm_44_rel_notes) | 5 Jan 2022| | [4.3](07_efm_43_rel_notes) | 2021 Dec 18| | [4.2](08_efm_42_rel_notes) | 2021 Apr 19| -| [4.1](09_efm_41_rel_notes) | 2021 Dec 11 | -| [4.0](10_efm_40_rel_notes) | 2021 Sep 2 | +| [4.1](09_efm_41_rel_notes) | 11 Dec 2021| +| [4.0](10_efm_40_rel_notes) | 2 Sep 2021 | diff --git a/product_docs/docs/epas/11/epas_rel_notes/index.mdx b/product_docs/docs/epas/11/epas_rel_notes/index.mdx index 1cab0645dad..b321278359f 100644 --- a/product_docs/docs/epas/11/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/11/epas_rel_notes/index.mdx @@ -24,26 +24,26 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merge | | ------- | ------------ | -------------- | -| [11.21.32](epas11_21_32_rel_notes.mdx) | 2023 Aug 21 | [11.21](https://www.postgresql.org/docs/11/release-11-21.html) | -| [11.20.31](epas11_20_31_rel_notes.mdx) | 2023 May 11 | [11.20](https://www.postgresql.org/docs/11/release-11-20.html) | -| [11.19.30](epas11_19_30_rel_notes.mdx) | 2023 Feb 10 | [11.19](https://www.postgresql.org/docs/11/release-11-19.html) | -| [11.18.29](epas11_18_29_rel_notes.mdx) | 2022 Nov 10 | [11.18](https://www.postgresql.org/docs/11/release-11-18.html) | -| [11.17.28](epas11_17_28_rel_notes.mdx) | 2022 Aug 11 | [11.17](https://www.postgresql.org/docs/11/release-11-17.html) | -| [11.16.26](epas11_16_26_rel_notes.mdx) | 2022 May 12 | [11.16](https://www.postgresql.org/docs/11/release-11-16.html) | -| [11.15.25](09_epas11.15.25_rel_notes.mdx) | 2022 Feb 10 | [11.15](https://www.postgresql.org/docs/11/release-11-15.html) | -| [11.14.24](10_epas11.14.24_rel_notes.mdx) | 2021 Nov 11 | [11.14](https://www.postgresql.org/docs/11/release-11-14.html) | -| [11.13.23](11_epas11.13.23_rel_notes.mdx) | 2021 Sep 08 | [11.13](https://www.postgresql.org/docs/11/release-11-13.html) | -| [11.12.22](13_epas11.12.22_rel_notes.mdx) | 2021 May 05 | [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | -| [11.12.21](15_epas11.12.21_rel_notes.mdx) | 2021 Apr 15 | [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | -| [11.11.20](17_epas11.11.20_rel_notes.mdx) | 2021 Feb 12 | [11.11](https://www.postgresql.org/docs/11/release-11-11.html) | -| [11.10.19](19_epas11.10.19_rel_notes.mdx) | 2020 Nov 20 | [11.10](https://www.postgresql.org/docs/11/release-11-10.html) | -| [11.9.17](21_epas11.9.17_rel_notes.mdx) | 2020 Aug 18 | [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | -| [11.9.16](23_epas11.9.16_rel_notes.mdx) | 2020 Aug 17 | [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | -| [11.8.15](25_epas11.8.15_rel_notes.mdx) | 2020 May 18 | [11.8](https://www.postgresql.org/docs/11/release-11-8.html) | -| [11.7.14](27_epas11.7.14_rel_notes.mdx) | 2020 Feb 14 | [11.7](https://www.postgresql.org/docs/11/release-11-7.html) | -| [11.6.13](29_epas11.6.13_rel_notes.mdx) | 2019 Nov 19 | [11.6](https://www.postgresql.org/docs/11/release-11-6.html) | -| [11.5.12](31_epas11.5.12_rel_notes.mdx) | 2019 Aug 26 | [11.5](https://www.postgresql.org/docs/11/release-11-5.html) | -| [11.4.11](33_epas11.4.11_rel_notes.mdx) | 2019 Jun 25 | [11.4](https://www.postgresql.org/docs/11/release-11-4.html) | -| [11.3.10](35_epas11.3.10_rel_notes.mdx) | 2019 May 13 | [11.3](https://www.postgresql.org/docs/11/release-11-3.html) | -| [11.2.9](37_epas11.2.9_rel_notes.mdx) | 2019 Feb 22 | [11.2](https://www.postgresql.org/docs/11/release-11-2.html) | -| [11.1.7](39_epas11.1.7_rel_notes.mdx) | 2018 Nov 28 | [11.1](https://www.postgresql.org/docs/11/release-11-1.html) | \ No newline at end of file +| [11.21.32](epas11_21_32_rel_notes.mdx) | 21 Aug 2023 | [11.21](https://www.postgresql.org/docs/11/release-11-21.html) | +| [11.20.31](epas11_20_31_rel_notes.mdx) | 11 May 2023 | [11.20](https://www.postgresql.org/docs/11/release-11-20.html) | +| [11.19.30](epas11_19_30_rel_notes.mdx) | 10 Feb 2023 | [11.19](https://www.postgresql.org/docs/11/release-11-19.html) | +| [11.18.29](epas11_18_29_rel_notes.mdx) | 10 Nov 2022 | [11.18](https://www.postgresql.org/docs/11/release-11-18.html) | +| [11.17.28](epas11_17_28_rel_notes.mdx) | 11 Aug 2022 | [11.17](https://www.postgresql.org/docs/11/release-11-17.html) | +| [11.16.26](epas11_16_26_rel_notes.mdx) | 12 May 2022 | [11.16](https://www.postgresql.org/docs/11/release-11-16.html) | +| [11.15.25](09_epas11.15.25_rel_notes.mdx) | 10 Feb 2022 | [11.15](https://www.postgresql.org/docs/11/release-11-15.html) | +| [11.14.24](10_epas11.14.24_rel_notes.mdx) | 11 Nov 2021| [11.14](https://www.postgresql.org/docs/11/release-11-14.html) | +| [11.13.23](11_epas11.13.23_rel_notes.mdx) | 08 Sep 2021| [11.13](https://www.postgresql.org/docs/11/release-11-13.html) | +| [11.12.22](13_epas11.12.22_rel_notes.mdx) | 05 May 2021| [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | +| [11.12.21](15_epas11.12.21_rel_notes.mdx) | 15 Apr 2021| [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | +| [11.11.20](17_epas11.11.20_rel_notes.mdx) | 12 Feb 2021| [11.11](https://www.postgresql.org/docs/11/release-11-11.html) | +| [11.10.19](19_epas11.10.19_rel_notes.mdx) | 20 Nov 2020| [11.10](https://www.postgresql.org/docs/11/release-11-10.html) | +| [11.9.17](21_epas11.9.17_rel_notes.mdx) | 18 Aug 2020| [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | +| [11.9.16](23_epas11.9.16_rel_notes.mdx) | 17 Aug 2020| [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | +| [11.8.15](25_epas11.8.15_rel_notes.mdx) | 18 May 2020| [11.8](https://www.postgresql.org/docs/11/release-11-8.html) | +| [11.7.14](27_epas11.7.14_rel_notes.mdx) | 14 Feb 2020| [11.7](https://www.postgresql.org/docs/11/release-11-7.html) | +| [11.6.13](29_epas11.6.13_rel_notes.mdx) | 19 Nov 2019| [11.6](https://www.postgresql.org/docs/11/release-11-6.html) | +| [11.5.12](31_epas11.5.12_rel_notes.mdx) | 26 Aug 2019| [11.5](https://www.postgresql.org/docs/11/release-11-5.html) | +| [11.4.11](33_epas11.4.11_rel_notes.mdx) | 25 Jun 2019| [11.4](https://www.postgresql.org/docs/11/release-11-4.html) | +| [11.3.10](35_epas11.3.10_rel_notes.mdx) | 13 May 2019| [11.3](https://www.postgresql.org/docs/11/release-11-3.html) | +| [11.2.9](37_epas11.2.9_rel_notes.mdx) | 22 Feb 2019| [11.2](https://www.postgresql.org/docs/11/release-11-2.html) | +| [11.1.7](39_epas11.1.7_rel_notes.mdx) | 28 Nov 2018| [11.1](https://www.postgresql.org/docs/11/release-11-1.html) | \ No newline at end of file diff --git a/product_docs/docs/epas/12/epas_rel_notes/index.mdx b/product_docs/docs/epas/12/epas_rel_notes/index.mdx index 9261a7af773..2c30ddf4612 100644 --- a/product_docs/docs/epas/12/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/12/epas_rel_notes/index.mdx @@ -27,20 +27,20 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merges | | ------- | ------------ | --------------- | -| [12.16.20](epas12_16_20_rel_notes.mdx) | 2023 Aug 21 | [12.16](https://www.postgresql.org/docs/12/release-12-16.html) -| [12.15.19](epas12_15_19_rel_notes.mdx) | 2023 May 11 | [12.15](https://www.postgresql.org/docs/12/release-12-15.html) | -| [12.14.18](epas12_14_18_rel_notes.mdx) | 2023 Feb 10 | [12.14](https://www.postgresql.org/docs/12/release-12-14.html) | -| [12.13.17](epas12_13_17_rel_notes.mdx) | 2022 Nov 10 | [12.13](https://www.postgresql.org/docs/12/release-12-13.html) | -| [12.12.16](epas12_12_16_rel_notes.mdx) | 2022 Aug 11 | [12.12](https://www.postgresql.org/docs/12/release-12-12.html) | -| [12.11.15](epas12_11_15_rel_notes.mdx) | 2022 May 12 | [12.11](https://www.postgresql.org/docs/12/release-12-11.html) | -| [12.10.14](05_epas12.10.14_rel_notes.mdx) | 2022 Feb 10 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | | [12.10.14](05_epas12.10.14_rel_notes.mdx) | 2022 Feb 10 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | -| [12.9.13](06_epas12.9.13_rel_notes.mdx) | 2021 Nov 11 | [12.9](https://www.postgresql.org/docs/12/release-12-9.html) | -| [12.8.12](07_epas12.8.12_rel_notes.mdx) | 2021 Sep 28 | [12.8](https://www.postgresql.org/docs/12/release-12-8.html) | -| [12.7.10](08_epas12.7.10_rel_notes.mdx) | 2021 May 25 | [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | -| [12.7](09_epas12.7_rel_notes.mdx) | 2021 May 14 | [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | -| [12.6.7](10_epas12.6.7_rel_notes.mdx) | 2021 Feb 12 | [12.6](https://www.postgresql.org/docs/12/release-12-6.html) | -| [12.5.6](11_epas12.5.6_rel_notes.mdx) | 2020 Nov 20 | [12.5](https://www.postgresql.org/docs/12/release-12-5.html) | -| [12.4.5](13_epas12.4.5_rel_notes.mdx) | 2020 Aug 17 | [12.4](https://www.postgresql.org/docs/12/release-12-4.html) | -| [12.3.4](15_epas12.3.4_rel_notes.mdx) | 2020 May 18 | [12.3](https://www.postgresql.org/docs/12/release-12-3.html) | -| [12.2.3](17_epas12.2.3_rel_notes.mdx) | 2020 Feb 14 | [12.2](https://www.postgresql.org/docs/12/release-12-2.html) | -| [12.1.2](19_epas12.1.2_rel_notes.mdx) | 2019 Dec 10 | [12.0](https://www.postgresql.org/docs/12/release-12.html) | \ No newline at end of file +| [12.16.20](epas12_16_20_rel_notes.mdx) | 21 Aug 2023 | [12.16](https://www.postgresql.org/docs/12/release-12-16.html) +| [12.15.19](epas12_15_19_rel_notes.mdx) | 11 May 2023 | [12.15](https://www.postgresql.org/docs/12/release-12-15.html) | +| [12.14.18](epas12_14_18_rel_notes.mdx) | 10 Feb 2023 | [12.14](https://www.postgresql.org/docs/12/release-12-14.html) | +| [12.13.17](epas12_13_17_rel_notes.mdx) | 10 Nov 2022 | [12.13](https://www.postgresql.org/docs/12/release-12-13.html) | +| [12.12.16](epas12_12_16_rel_notes.mdx) | 11 Aug 2022 | [12.12](https://www.postgresql.org/docs/12/release-12-12.html) | +| [12.11.15](epas12_11_15_rel_notes.mdx) | 12 May 2022 | [12.11](https://www.postgresql.org/docs/12/release-12-11.html) | +| [12.10.14](05_epas12.10.14_rel_notes.mdx) | 10 Feb 2022 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | | [12.10.14](05_epas12.10.14_rel_notes.mdx) | 10 Feb 2022 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | +| [12.9.13](06_epas12.9.13_rel_notes.mdx) | 11 Nov 2021| [12.9](https://www.postgresql.org/docs/12/release-12-9.html) | +| [12.8.12](07_epas12.8.12_rel_notes.mdx) | 28 Sep 2021| [12.8](https://www.postgresql.org/docs/12/release-12-8.html) | +| [12.7.10](08_epas12.7.10_rel_notes.mdx) | 25 May 2021| [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | +| [12.7](09_epas12.7_rel_notes.mdx) | 14 May 2021| [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | +| [12.6.7](10_epas12.6.7_rel_notes.mdx) | 12 Feb 2021| [12.6](https://www.postgresql.org/docs/12/release-12-6.html) | +| [12.5.6](11_epas12.5.6_rel_notes.mdx) | 20 Nov 2020| [12.5](https://www.postgresql.org/docs/12/release-12-5.html) | +| [12.4.5](13_epas12.4.5_rel_notes.mdx) | 17 Aug 2020| [12.4](https://www.postgresql.org/docs/12/release-12-4.html) | +| [12.3.4](15_epas12.3.4_rel_notes.mdx) | 18 May 2020| [12.3](https://www.postgresql.org/docs/12/release-12-3.html) | +| [12.2.3](17_epas12.2.3_rel_notes.mdx) | 14 Feb 2020| [12.2](https://www.postgresql.org/docs/12/release-12-2.html) | +| [12.1.2](19_epas12.1.2_rel_notes.mdx) | 10 Dec 2019| [12.0](https://www.postgresql.org/docs/12/release-12.html) | \ No newline at end of file diff --git a/product_docs/docs/epas/13/epas_rel_notes/index.mdx b/product_docs/docs/epas/13/epas_rel_notes/index.mdx index eb487d41638..e0a3eb281bd 100644 --- a/product_docs/docs/epas/13/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/13/epas_rel_notes/index.mdx @@ -20,16 +20,16 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merges | | ------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------- | -| [13.12.17](epas13_12_17_rel_notes) | 2023 Aug 21 | [13.12](https://www.postgresql.org/docs/release/13.12/) | -| [13.11.15](epas13_11_15_rel_notes) | 2023 May 11 | [13.11](https://www.postgresql.org/docs/release/13.11/) | -| [13.10.14](epas13_10_14_rel_notes) | 2023 Feb 10 | [13.10](https://www.postgresql.org/docs/release/13.10/) | -| [13.9.13](epas13_9_13_rel_notes) | 2022 Nov 10 | [13.9](https://www.postgresql.org/docs/release/13.9/) | -| [13.8.12](epas13_8_12_rel_notes) | 2022 Aug 11 | [13.8](https://www.postgresql.org/docs/release/13.8/) | -| [13.7.11](epas13_7_11_rel_notes) | 2022 May 23 | [13.7](https://www.postgresql.org/docs/release/13.7/) -| [13.6.10](13_epas13.6.10_rel_notes) | 2022 Feb 10 | [13.6](https://www.postgresql.org/docs/13/release-13-6.html) | -| [13.5.9](14_epas13.5.9_rel_notes) | 2021 Nov 11 | [13.5](https://www.postgresql.org/docs/13/release-13-5.html) | -| [13.4.8](15_epas13.4.8_rel_notes) | 2021 Sep 28 | [13.4](https://www.postgresql.org/docs/13/release-13-4.html) | -| [13.3.7](16_epas13.3.7_rel_notes) | 2021 May 25 | NA | -| [13.3.6](17_epas13.3.6_rel_notes) | 2021 May 14 | [13.3](https://www.postgresql.org/docs/13/release-13-3.html) | -| [13.2.5](19_epas13.2.5_rel_notes) | 2021 Feb 02 | [13.2](https://www.postgresql.org/docs/13/release-13-2.html) | -| [13.1.4](20_epas13_rel_notes) | 2020 Dec 12 | [13](https://www.postgresql.org/docs/13/release-13.html), [13.1](https://www.postgresql.org/docs/13/release-13-1.html) | \ No newline at end of file +| [13.12.17](epas13_12_17_rel_notes) | 21 Aug 2023 | [13.12](https://www.postgresql.org/docs/release/13.12/) | +| [13.11.15](epas13_11_15_rel_notes) | 11 May 2023 | [13.11](https://www.postgresql.org/docs/release/13.11/) | +| [13.10.14](epas13_10_14_rel_notes) | 10 Feb 2023 | [13.10](https://www.postgresql.org/docs/release/13.10/) | +| [13.9.13](epas13_9_13_rel_notes) | 10 Nov 2022 | [13.9](https://www.postgresql.org/docs/release/13.9/) | +| [13.8.12](epas13_8_12_rel_notes) | 11 Aug 2022 | [13.8](https://www.postgresql.org/docs/release/13.8/) | +| [13.7.11](epas13_7_11_rel_notes) | 23 May 2022 | [13.7](https://www.postgresql.org/docs/release/13.7/) +| [13.6.10](13_epas13.6.10_rel_notes) | 10 Feb 2022 | [13.6](https://www.postgresql.org/docs/13/release-13-6.html) | +| [13.5.9](14_epas13.5.9_rel_notes) | 11 Nov 2021 | [13.5](https://www.postgresql.org/docs/13/release-13-5.html) | +| [13.4.8](15_epas13.4.8_rel_notes) | 28 Sep 2021 | [13.4](https://www.postgresql.org/docs/13/release-13-4.html) | +| [13.3.7](16_epas13.3.7_rel_notes) | 25 May 2021 | NA | +| [13.3.6](17_epas13.3.6_rel_notes) | 14 May 2021 | [13.3](https://www.postgresql.org/docs/13/release-13-3.html) | +| [13.2.5](19_epas13.2.5_rel_notes) | 02 Feb 2021 | [13.2](https://www.postgresql.org/docs/13/release-13-2.html) | +| [13.1.4](20_epas13_rel_notes) | 12 Dec 2020 | [13](https://www.postgresql.org/docs/13/release-13.html), [13.1](https://www.postgresql.org/docs/13/release-13-1.html) | \ No newline at end of file diff --git a/product_docs/docs/epas/14/epas_rel_notes/index.mdx b/product_docs/docs/epas/14/epas_rel_notes/index.mdx index 3fdff1905c9..a11ad85cf6e 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/index.mdx @@ -19,15 +19,15 @@ The EDB Postgres Advanced Server (EDB Postgres Advanced Server) documentation de | Version | Release date | Upstream merges | | ------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------- | -| [14.9.0](epas14_9_0_rel_notes) | 2023 Aug 21 | [14.9](https://www.postgresql.org/docs/14/release-14-9.html) | -| [14.8.0](epas14_8_0_rel_notes) | 2023 May 11 | [14.8](https://www.postgresql.org/docs/14/release-14-8.html) | -| [14.7.0](epas14_7_0_rel_notes) | 2023 Feb 10 | [14.7](https://www.postgresql.org/docs/14/release-14-7.html) | -| [14.6.0](epas14_6_0_rel_notes) | 2022 Nov 10 | [14.6](https://www.postgresql.org/docs/14/release-14-6.html) | -| [14.5.0](epas14_5_0_rel_notes) | 2022 Aug 11 | [14.5](https://www.postgresql.org/docs/14/release-14-5.html) | -| [14.4.0](epas14_4_0_rel_notes) | 2022 Jun 16 | [14.4](https://www.postgresql.org/docs/14/release-14-4.html) | -| [14.3.0](epas14_3_0_rel_notes) | 2022 May 12 | [14.3](https://www.postgresql.org/docs/14/release-14-3.html) | -| [14.2.1](19_epas14.2.1_rel_notes) | 2022 Feb 10 | [14.2](https://www.postgresql.org/docs/14/release-14-2.html) | -| [14.1.0](20_epas14_rel_notes) | 2021 Dec 01 | [14.0](https://www.postgresql.org/docs/14/release-14.html), [14.1](https://www.postgresql.org/docs/14/release-14-1.html) | +| [14.9.0](epas14_9_0_rel_notes) | 21 Aug 2023 | [14.9](https://www.postgresql.org/docs/14/release-14-9.html) | +| [14.8.0](epas14_8_0_rel_notes) | 11 May 2023 | [14.8](https://www.postgresql.org/docs/14/release-14-8.html) | +| [14.7.0](epas14_7_0_rel_notes) | 10 Feb 2023 | [14.7](https://www.postgresql.org/docs/14/release-14-7.html) | +| [14.6.0](epas14_6_0_rel_notes) | 10 Nov 2022 | [14.6](https://www.postgresql.org/docs/14/release-14-6.html) | +| [14.5.0](epas14_5_0_rel_notes) | 11 Aug 2022 | [14.5](https://www.postgresql.org/docs/14/release-14-5.html) | +| [14.4.0](epas14_4_0_rel_notes) | 16 Jun 2022 | [14.4](https://www.postgresql.org/docs/14/release-14-4.html) | +| [14.3.0](epas14_3_0_rel_notes) | 12 May 2022 | [14.3](https://www.postgresql.org/docs/14/release-14-3.html) | +| [14.2.1](19_epas14.2.1_rel_notes) | 10 Feb 2022 | [14.2](https://www.postgresql.org/docs/14/release-14-2.html) | +| [14.1.0](20_epas14_rel_notes) | 01 Dec 2021 | [14.0](https://www.postgresql.org/docs/14/release-14.html), [14.1](https://www.postgresql.org/docs/14/release-14-1.html) | ## Support announcements diff --git a/product_docs/docs/epas/15/epas_rel_notes/index.mdx b/product_docs/docs/epas/15/epas_rel_notes/index.mdx index 039dd690f8c..6739f08a0e5 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/index.mdx @@ -13,9 +13,9 @@ The EDB Postgres Advanced Server documentation describes the latest version of E | Version | Release date | Upstream merges | | ------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [15.4.0](epas15_4_0_rel_notes) | 2023 Aug 21 | [15.4](https://www.postgresql.org/docs/release/15.4/) -| [15.3.0](epas15_3_0_rel_notes) | 2023 May 11 | [15.3](https://www.postgresql.org/docs/release/15.3/) | -| [15.2.0](epas15_2_0_rel_notes) | 2023 Feb 14 | [15.0](https://www.postgresql.org/docs/release/15.0/), [15.1](https://www.postgresql.org/docs/release/15.1/), [15.2](https://www.postgresql.org/docs/release/15.2/) | +| [15.4.0](epas15_4_0_rel_notes) | 21 Aug 2023 | [15.4](https://www.postgresql.org/docs/release/15.4/) +| [15.3.0](epas15_3_0_rel_notes) | 11 May 2023 | [15.3](https://www.postgresql.org/docs/release/15.3/) | +| [15.2.0](epas15_2_0_rel_notes) | 14 Feb 2023 | [15.0](https://www.postgresql.org/docs/release/15.0/), [15.1](https://www.postgresql.org/docs/release/15.1/), [15.2](https://www.postgresql.org/docs/release/15.2/) | ## Component certification diff --git a/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx b/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx index 3e969e562cb..3a205855418 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx @@ -411,7 +411,7 @@ _edb_replicator_pub.sp_dropsequence SQL_STORED_PROCEDURE _edb_replicator_sub.rrep_common_seq USER_TABLE ``` -SQL Server versions 2012 and 2014 support creation of sequence objects that can now perform the functionality previously provided by the preceding list of objects. The following are the sequence objects that are now used when the publication database is SQL Server 2012 or 2014: +SQL Server versions 2014 and 2012support creation of sequence objects that can now perform the functionality previously provided by the preceding list of objects. The following are the sequence objects that are now used when the publication database is SQL Server 2012 or 2014: ```shell 1> USE edb; diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx index 36623d6ebb4..8ba40e8def8 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx @@ -13,15 +13,15 @@ The Replication Server documentation describes the latest version including mino | Version | Release Date | | -------------------------------- | ------------ | -| [7.5.1](eprs_rel_notes_7.5.1) | 2023 May 26 | -| [7.5.0](eprs_rel_notes_7.5.0) | 2023 Feb 14 | -| [7.4.0](eprs_rel_notes_7.4.0) | 2022 Nov 29 | -| [7.3.0](15_eprs_rel_notes_7.3.0) | 2022 Nov 15 | -| [7.2.1](16_eprs_rel_notes_7.2.1) | 2022 Jul 25 | -| [7.2.0](17_eprs_rel_notes_7.2.0) | 2022 Jun 24 | -| [7.1.0](18_eprs_rel_notes_7.1.0) | 2022 Mar 21 | -| [7.0.1](19_eprs_rel_notes_7.0.1) | 2022 Mar 03 | -| [7.0.0](20_eprs_rel_notes_7.0.0) | 2021 Dec 01 | +| [7.5.1](eprs_rel_notes_7.5.1) | 26 May 2023 | +| [7.5.0](eprs_rel_notes_7.5.0) | 14 Feb 2023 | +| [7.4.0](eprs_rel_notes_7.4.0) | 29 Nov 2022 | +| [7.3.0](15_eprs_rel_notes_7.3.0) | 15 Nov 2022 | +| [7.2.1](16_eprs_rel_notes_7.2.1) | 25 Jul 2022 | +| [7.2.0](17_eprs_rel_notes_7.2.0) | 24 Jun 2022 | +| [7.1.0](18_eprs_rel_notes_7.1.0) | 21 Mar 2022 | +| [7.0.1](19_eprs_rel_notes_7.0.1) | 03 Mar 2022 | +| [7.0.0](20_eprs_rel_notes_7.0.0) | 01 Dec 2021 | ## Supported upgrade paths diff --git a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/index.mdx b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/index.mdx index 04658f3c2c7..e435172e198 100644 --- a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/index.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/index.mdx @@ -18,11 +18,11 @@ The Hadoop Foreign Data Wrapper documentation describes the latest version inclu | Version | Release Date | | --------------------------------| ------------ | -| [2.3.1](hadoop_rel_notes_2.3.1) | 2023 Jul 20 | -| [2.3.0](hadoop_rel_notes_2.3.0) | 2023 Jan 06 | -| [2.2.0](hadoop_rel_notes_2.2.0) | 2022 May 26 | -| [2.1.0](hadoop_rel_notes_2.1.0) | 2021 Dec 02 | -| [2.0.8](hadoop_rel_notes_2.0.8) | 2021 Jun 24 | -| [2.0.7](hadoop_rel_notes_2.0.7) | 2020 Nov 23 | -| [2.0.5](hadoop_rel_notes_2.0.5) | 2019 Dec 10 | -| [2.0.4](hadoop_rel_notes_2.0.4) | 2018 Nov 28 | +| [2.3.1](hadoop_rel_notes_2.3.1) | 20 Jul 2023 | +| [2.3.0](hadoop_rel_notes_2.3.0) | 06 Jan 2023 | +| [2.2.0](hadoop_rel_notes_2.2.0) | 26 May 2022 | +| [2.1.0](hadoop_rel_notes_2.1.0) | 02 Dec 2021 | +| [2.0.8](hadoop_rel_notes_2.0.8) | 24 Jun 2021 | +| [2.0.7](hadoop_rel_notes_2.0.7) | 23 Nov 2020 | +| [2.0.5](hadoop_rel_notes_2.0.5) | 10 Dec 2019 | +| [2.0.4](hadoop_rel_notes_2.0.4) | 28 Nov 2018 | diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx index 020b7b15338..7c72652e3e8 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx @@ -13,16 +13,16 @@ These release notes describe what's new in each release. When a minor or patch r | Version | Release Date | | ---------------------------------------- | ------------ | -| [42.5.4.1](jdbc_42.5.4.1_rel_notes) | 2023 Mar 16 | -| [42.5.1.2](jdbc_42.5.1.2_rel_notes) | 2023 Feb 14 | -| [42.5.1.1](jdbc_42.5.1.1_rel_notes) | 2022 Dec 9 | -| [42.5.0.1](jdbc_42.5.0.1_rel_notes) | 2022 Sep 1 | -| [42.3.3.1](08_jdbc_42.3.3.1_rel_notes) | 2022 Apr 20 | -| [42.3.2.1](09_jdbc_42.3.2.1_rel_notes) | 2022 Feb 15 | -| [42.2.24.1](10_jdbc_42.2.24.1_rel_notes) | 2021 Nov 5 | -| [42.2.19.1](12_jdbc_42.2.19.1_rel_notes) | 2021 Apr 15 | -| [42.2.12.3](14_jdbc_42.2.12.3_rel_notes) | 2020 Oct 22 | -| [42.2.9.1](16_jdbc_42.2.9.1_rel_notes) | 2020 May 18 | -| [42.2.8.1](18_jdbc_42.2.8.1_rel_notes) | 2019 Oct 21 | +| [42.5.4.1](jdbc_42.5.4.1_rel_notes) | 16 Mar 2023 | +| [42.5.1.2](jdbc_42.5.1.2_rel_notes) | 14 Feb 2023 | +| [42.5.1.1](jdbc_42.5.1.1_rel_notes) | 9 Dec 2022 | +| [42.5.0.1](jdbc_42.5.0.1_rel_notes) | 1 Sep 2022 | +| [42.3.3.1](08_jdbc_42.3.3.1_rel_notes) | 20 Apr 2022 | +| [42.3.2.1](09_jdbc_42.3.2.1_rel_notes) | 15 Feb 2022 | +| [42.2.24.1](10_jdbc_42.2.24.1_rel_notes) | 5 Nov 2021 | +| [42.2.19.1](12_jdbc_42.2.19.1_rel_notes) | 15 Apr 2021 | +| [42.2.12.3](14_jdbc_42.2.12.3_rel_notes) | 22 Oct 2020 | +| [42.2.9.1](16_jdbc_42.2.9.1_rel_notes) | 18 May 2020 | +| [42.2.8.1](18_jdbc_42.2.8.1_rel_notes) | 21 Oct 2019 | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx index 71b24680f38..aa7cc862c00 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx @@ -19,14 +19,14 @@ The Migration Toolkit documentation describes the latest version of Migration To | Version | Release Date | | ------- | ------------ | -| [55.6.0](mtk_556_rel_notes) | 2023 May 25 | -| [55.5.0](mtk_555_rel_notes) | 2023 Feb 14 | -| [55.4.0](mtk_554_rel_notes) | 2022 Nov 29 | -| [55.3.0](mtk_553_rel_notes) | 2022 Oct 06 | -| [55.2.3](mtk_5523_rel_notes) | 2022 Jun 16 | -| [55.2.2](05_mkt_5522_rel_notes) | 2022 Mar 10 | -| [55.2.1](06_mkt_5521_rel_notes) | 2022 Jan 13 | -| [55.2.0](07_mkt_552_rel_notes) | 2021 Dec 2 | -| [55.1.0](08_mkt_551_rel_notes) | 2021 Sep 20 | -| [55.0.0](09_mkt_55_rel_notes) | 2021 Mar 19 | +| [55.6.0](mtk_556_rel_notes) | 25 May 2023 | +| [55.5.0](mtk_555_rel_notes) | 14 Feb 2023 | +| [55.4.0](mtk_554_rel_notes) | 29 Nov 2022 | +| [55.3.0](mtk_553_rel_notes) | 06 Oct 2022 | +| [55.2.3](mtk_5523_rel_notes) | 16 Jun 2022 | +| [55.2.2](05_mkt_5522_rel_notes) | 10 Mar 2022 | +| [55.2.1](06_mkt_5521_rel_notes) | 13 Jan 2022 | +| [55.2.0](07_mkt_552_rel_notes) | 2 Dec 2021 | +| [55.1.0](08_mkt_551_rel_notes) | 20 Sep 2021 | +| [55.0.0](09_mkt_55_rel_notes) | 19 Mar 2021 | diff --git a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/index.mdx b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/index.mdx index 3e99eee7f41..92d5ea532ba 100644 --- a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/index.mdx +++ b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/index.mdx @@ -17,13 +17,13 @@ The Mongo Foreign Data Wrapper documentation describes the latest version of Mon | Version | Release date | | ----------------------------- | ------------ | -| [5.5.1](mongo5.5.1_rel_notes) | 2023 Jul 20 | -| [5.5.0](mongo5.5.0_rel_notes) | 2023 Jan 06 | -| [5.4.0](mongo5.4.0_rel_notes) | 2022 May 26 | -| [5.3.0](mongo5.3.0_rel_notes) | 2021 Dec 02 | -| [5.2.9](mongo5.2.9_rel_notes) | 2021 Jun 24 | -| [5.2.8](mongo5.2.8_rel_notes) | 2020 Nov 23 | -| [5.2.6](mongo5.2.8_rel_notes) | 2019 Sep 27 | -| [5.2.3](mongo5.2.8_rel_notes) | 2018 Nov 01 | +| [5.5.1](mongo5.5.1_rel_notes) | 20 Jul 2023 | +| [5.5.0](mongo5.5.0_rel_notes) | 06 Jan 2023 | +| [5.4.0](mongo5.4.0_rel_notes) | 26 May 2022 | +| [5.3.0](mongo5.3.0_rel_notes) | 02 Dec 2021 | +| [5.2.9](mongo5.2.9_rel_notes) | 24 Jun 2021 | +| [5.2.8](mongo5.2.8_rel_notes) | 23 Nov 2020 | +| [5.2.6](mongo5.2.8_rel_notes) | 27 Sep 2019 | +| [5.2.3](mongo5.2.8_rel_notes) | 01 Nov 2018 | diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx index ed38e10191e..99debbb99dd 100644 --- a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx @@ -17,11 +17,11 @@ The MySQL Foreign Data Wrapper documentation describes the latest version of MyS | Version | Release Date | | ----------------------------- | ------------ | -| [2.9.1](mysql2.9.1_rel_notes) | 2023 Jul 20 | -| [2.9.0](mysql2.9.0_rel_notes) | 2023 Jan 06 | -| [2.8.0](mysql2.8.0_rel_notes) | 2022 May 26 | -| [2.7.0](mysql2.7.0_rel_notes) | 2021 Dec 02 | -| [2.6.0](mysql2.6.0_rel_notes) | 2021 May 18 | -| [2.5.5](mysql2.5.5_rel_notes) | 2020 Nov 23 | -| [2.5.3](mysql2.5.3_rel_notes) | 2019 Dec 10 | -| [2.5.1](mysql2.5.1_rel_notes) | 2018 Nov 28 | \ No newline at end of file +| [2.9.1](mysql2.9.1_rel_notes) | 20 Jul 2023 | +| [2.9.0](mysql2.9.0_rel_notes) | 06 Jan 2023 | +| [2.8.0](mysql2.8.0_rel_notes) | 26 May 2022 | +| [2.7.0](mysql2.7.0_rel_notes) | 02 Dec 2021 | +| [2.6.0](mysql2.6.0_rel_notes) | 18 May 2021 | +| [2.5.5](mysql2.5.5_rel_notes) | 23 Nov 2020 | +| [2.5.3](mysql2.5.3_rel_notes) | 10 Dec 2019 | +| [2.5.1](mysql2.5.1_rel_notes) | 28 Nov 2018 | \ No newline at end of file diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx index 6312a14c160..a174db2f141 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx @@ -13,7 +13,7 @@ Release notes describe what's new in a release. When a minor or patch release in | Version | Release date | | -------------------------------------- | ------------ | -| [15.2.0.3](15.2.0.3_ocl_release_notes) | 2023 Jun 20 | -| [15.2.0.2](15.2.0.2_ocl_release_notes) | 2023 May 19 | -| [15.2.0.1](01_ocl_release_notes) | 2023 Feb 14 | +| [15.2.0.3](15.2.0.3_ocl_release_notes) | 20 Jun 2023 | +| [15.2.0.2](15.2.0.2_ocl_release_notes) | 19 May 2023 | +| [15.2.0.1](01_ocl_release_notes) | 14 Feb 2023 | diff --git a/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx b/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx index 9e63dbfb4c3..70a8e648c0d 100644 --- a/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx +++ b/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx @@ -8,6 +8,6 @@ Release notes describe what is new in a release. When a minor or patch release i | Version | Release Date | | ------------------------------------------- | ------------ | -| [12.02.0000.02](01_odbc_12.2.0.2_rel_notes) | 2021 Nov 16 | -| [12.00.0000.02](03_odbc_12.0.0.2_rel_notes) | 2020 Aug 9 | +| [12.02.0000.02](01_odbc_12.2.0.2_rel_notes) | 16 Nov 2021 | +| [12.00.0000.02](03_odbc_12.0.0.2_rel_notes) | 9 Aug 2020 | diff --git a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx index f4f7db8dacc..1263f196cd5 100644 --- a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx +++ b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx @@ -10,8 +10,8 @@ Release notes describe what's new in a release. When a minor or patch release in | Version | Release date | | ----------------------------------------- | ------------ | -| [13.02.0000.02](odbc_13.2.0.02_rel_notes) | 2023 Feb 14 | -| [13.02.0000.01](02_odbc_13.2.0.01_rel_notes) | 2022 May 17 | -| [13.01.0000.02](03_odbc_13.1.0.02_rel_notes) | 2021 Dec 12 | -| [13.01.0000.01](04_odbc_13.1.0.01_rel_notes) | 2021 Sep 14 | -| [13.00.0000.01](05_odbc_13.0.0.01_rel_notes) | 2020 Nov 19 | +| [13.02.0000.02](odbc_13.2.0.02_rel_notes) | 14 Feb 2023| +| [13.02.0000.01](02_odbc_13.2.0.01_rel_notes) | 17 May 2022| +| [13.01.0000.02](03_odbc_13.1.0.02_rel_notes) | 12 Dec 2021 | +| [13.01.0000.01](04_odbc_13.1.0.01_rel_notes) | 14 Sep 2021 | +| [13.00.0000.01](05_odbc_13.0.0.01_rel_notes) | 19 Nov 2020 | diff --git a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx index c8c1c6e8829..c2a53ccf12d 100644 --- a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx +++ b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx @@ -8,9 +8,9 @@ The EDB PgBouncer documentation describes the latest version of EDB PgBouncer 1, | Version | Release date | Upstream merges | | ------------------------------ | ------------ | --------------------------------------------------------------------------------- | -| [1.19.0.0](06_11900_rel_notes) | 2023 Jun 07 | Upstream [1.19.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-119x) -| [1.18.0.0](07_11800_rel_notes) | 2023 Feb 14 | Upstream [1.18.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-118x) -| [1.17.0.0](08_11700_rel_notes) | 2022 Aug 04 | Upstream [1.17.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-117x) -| [1.16.1.0](09_11610_rel_notes) | 2021 Dec 11 | Upstream [1.16.1.0](https://www.pgbouncer.org/changelog.html#pgbouncer-116x) | -| [1.16.0.1](10_11601_rel_notes) | 2021 Jun 10 | Upstream [1.16.0.1](https://www.pgbouncer.org/changelog.html#pgbouncer-116x) | +| [1.19.0.0](06_11900_rel_notes) | 07 Jun 2023 | Upstream [1.19.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-119x) +| [1.18.0.0](07_11800_rel_notes) | 14 Feb 2023 | Upstream [1.18.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-118x) +| [1.17.0.0](08_11700_rel_notes) | 04 Aug 2022 | Upstream [1.17.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-117x) +| [1.16.1.0](09_11610_rel_notes) | 11 Dec 2021 | Upstream [1.16.1.0](https://www.pgbouncer.org/changelog.html#pgbouncer-116x) | +| [1.16.0.1](10_11601_rel_notes) | 10 Jun 2021 | Upstream [1.16.0.1](https://www.pgbouncer.org/changelog.html#pgbouncer-116x) | diff --git a/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx b/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx index 722e81914b4..190f1efe85f 100644 --- a/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx +++ b/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx @@ -25,15 +25,15 @@ The release notes in this section provide information on what was new in each re | Version | Release Date | | ----------------------- | ------------ | -| [2.3.1](harp2.3.1_rel_notes) | 2023 Jul 27 | -| [2.3.0](harp2.3.0_rel_notes) | 2023 Jul 12 | -| [2.2.3](harp2.2.3_rel_notes) | 2023 May 16 | -| [2.2.2](harp2.2.2_rel_notes) | 2023 Mar 30 | -| [2.2.1](harp2.2.1_rel_notes) | 2022 Nov 16 | -| [2.2.0](harp2.2.0_rel_notes) | 2022 Aug 22 | -| [2.1.1](harp2.1.1_rel_notes) | 2022 Jun 21 | -| [2.1.0](harp2.1.0_rel_notes) | 2022 May 17 | -| [2.0.3](harp2.0.3_rel_notes) | 2022 Mar 31 | -| [2.0.2](harp2.0.2_rel_notes) | 2022 Feb 24 | -| [2.0.1](harp2.0.1_rel_notes) | 2021 Jan 31 | -| [2.0.0](harp2_rel_notes) | 2021 Dec 01 | +| [2.3.1](harp2.3.1_rel_notes) | 27 Jul 2023 | +| [2.3.0](harp2.3.0_rel_notes) | 12 Jul 2023 | +| [2.2.3](harp2.2.3_rel_notes) | 16 May 2023 | +| [2.2.2](harp2.2.2_rel_notes) | 30 Mar 2023 | +| [2.2.1](harp2.2.1_rel_notes) | 16 Nov 2022 | +| [2.2.0](harp2.2.0_rel_notes) | 22 Aug 2022 | +| [2.1.1](harp2.1.1_rel_notes) | 21 Jun 2022 | +| [2.1.0](harp2.1.0_rel_notes) | 17 May 2022 | +| [2.0.3](harp2.0.3_rel_notes) | 31 Mar 2022 | +| [2.0.2](harp2.0.2_rel_notes) | 24 Feb 2022 | +| [2.0.1](harp2.0.1_rel_notes) | 31 Jan 2021 | +| [2.0.0](harp2_rel_notes) | 01 Dec 2021 | diff --git a/product_docs/docs/pgd/4/rel_notes/index.mdx b/product_docs/docs/pgd/4/rel_notes/index.mdx index 75e5ab566bc..9ea08a1e8fd 100644 --- a/product_docs/docs/pgd/4/rel_notes/index.mdx +++ b/product_docs/docs/pgd/4/rel_notes/index.mdx @@ -27,17 +27,17 @@ The EDB Postgres Distributed documentation describes the latest version of EDB P | ------------ | ---------------------------- | ----- | ----- | ----- | -------------------------------------------------------------------------------- | | 2023 July 27 | [4.3.1-2 ](pgd_4.3.1-2_rel_notes)| 4.3.1 | 2.3.1 | 1.1.1 | [23.19](/tpa/latest/rel_notes/tpa_23.19_rel_notes) | | 2023 July 12 | [4.3.1-1 ](pgd_4.3.1-1_rel_notes)| 4.3.1 | 2.3.0 | 1.1.1 | [23.19](/tpa/latest/rel_notes/tpa_23.19_rel_notes) | -| 2023 May 17 | [4.3.1](pgd_4.3.1_rel_notes) | 4.3.1 | 2.2.3 | 1.1.1 | [23.17](/tpa/latest/rel_notes/tpa_23.17_rel_notes) | -| 2023 Mar 30 | [4.3.0-1](pgd_4.3.0-1_rel_notes) | 4.3.0 | 2.2.2 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | -| 2023 Feb 14 | [4.3.0](pgd_4.3.0_rel_notes) | 4.3.0 | 2.2.1 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | -| 2022 Dec 14 | [4.2.2](pgd_4.2.2_rel_notes) | 4.2.2 | 2.2.1 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | -| 2022 Nov 16 | [4.2.1](pgd_4.2.1_rel_notes) | 4.2.1 | 2.2.1 | 1.1.0 | [23.7](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-237) | -| 2022 Aug 22 | [4.2.0](pgd_4.2.0_rel_notes) | 4.2.0 | 2.2.0 | 1.1.0 | [23.5](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-235) | +| 17 May 2023 | [4.3.1](pgd_4.3.1_rel_notes) | 4.3.1 | 2.2.3 | 1.1.1 | [23.17](/tpa/latest/rel_notes/tpa_23.17_rel_notes) | +| 30 Mar 2023 | [4.3.0-1](pgd_4.3.0-1_rel_notes) | 4.3.0 | 2.2.2 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | +| 14 Feb 2023 | [4.3.0](pgd_4.3.0_rel_notes) | 4.3.0 | 2.2.1 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | +| 14 Dec 2022 | [4.2.2](pgd_4.2.2_rel_notes) | 4.2.2 | 2.2.1 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | +| 16 Nov 2022 | [4.2.1](pgd_4.2.1_rel_notes) | 4.2.1 | 2.2.1 | 1.1.0 | [23.7](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-237) | +| 22 Aug 2022 | [4.2.0](pgd_4.2.0_rel_notes) | 4.2.0 | 2.2.0 | 1.1.0 | [23.5](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-235) | | 2022 June 21 | [4.1.1](pgd_4.1.1_rel_notes) | 4.1.1 | 2.1.1 | 1.0.0 | [23.2](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-232) | -| 2022 May 17 | [4.1.0](pgd_4.1.0_rel_notes) | 4.1.0 | 2.1.0 | 1.0.0 | [23.1](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-231) | -| 2022 Mar 31 | [4.0.3](pgd_4.0.3_rel_notes) | - | 2.0.3 | - | 22.10 | -| 2022 Feb 24 | [4.0.2](pgd_4.0.2_rel_notes) | 4.0.2 | 2.0.2 | - | 22.9 | -| 2022 Jan 31 | [4.0.1](pgd_4.0.1_rel_notes) | 4.0.1 | 2.0.1 | - | 22.6 | -| 2021 Dec 01 | [4.0.0](pgd_4.0.0_rel_notes) | 4.0.0 | 2.0.0 | - | 21.9 | +| 17 May 2022 | [4.1.0](pgd_4.1.0_rel_notes) | 4.1.0 | 2.1.0 | 1.0.0 | [23.1](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-231) | +| 31 Mar 2022 | [4.0.3](pgd_4.0.3_rel_notes) | - | 2.0.3 | - | 22.10 | +| 24 Feb 2022 | [4.0.2](pgd_4.0.2_rel_notes) | 4.0.2 | 2.0.2 | - | 22.9 | +| 31 Jan 2022 | [4.0.1](pgd_4.0.1_rel_notes) | 4.0.1 | 2.0.1 | - | 22.6 | +| 01 Dec 2021 | [4.0.0](pgd_4.0.0_rel_notes) | 4.0.0 | 2.0.0 | - | 21.9 | diff --git a/product_docs/docs/pgd/5/rel_notes/index.mdx b/product_docs/docs/pgd/5/rel_notes/index.mdx index 8ca36d6563f..c5eb7e32160 100644 --- a/product_docs/docs/pgd/5/rel_notes/index.mdx +++ b/product_docs/docs/pgd/5/rel_notes/index.mdx @@ -20,7 +20,7 @@ that introduced the feature. | Release Date | EDB Postgres Distributed | BDR extension | PGD CLI | PGD Proxy | | ------------- | ---------------------------- | ------------- | ------- | --------- | -| 2023 Aug 4 | [5.2.0](pgd_5.2.0_rel_notes) | 5.2.0 | 5.2.0 | 5.2.0 | -| 2023 May 16 | [5.1.0](pgd_5.1.0_rel_notes) | 5.1.0 | 5.1.0 | 5.1.0 | -| 2023 Mar 21 | [5.0.1](pgd_5.0.1_rel_notes) | 5.0.0 | 5.0.1 | 5.0.1 | -| 2023 Feb 21 | [5.0.0](pgd_5.0.0_rel_notes) | 5.0.0 | 5.0.0 | 5.0.0 | +| 4 Aug 2023 | [5.2.0](pgd_5.2.0_rel_notes) | 5.2.0 | 5.2.0 | 5.2.0 | +| 16 May 2023 | [5.1.0](pgd_5.1.0_rel_notes) | 5.1.0 | 5.1.0 | 5.1.0 | +| 21 Mar 2023 | [5.0.1](pgd_5.0.1_rel_notes) | 5.0.0 | 5.0.1 | 5.0.1 | +| 21 Feb 2023 | [5.0.0](pgd_5.0.0_rel_notes) | 5.0.0 | 5.0.0 | 5.0.0 | diff --git a/product_docs/docs/pge/15/release_notes/index.mdx b/product_docs/docs/pge/15/release_notes/index.mdx index bd99b69f9b0..0d513be5602 100644 --- a/product_docs/docs/pge/15/release_notes/index.mdx +++ b/product_docs/docs/pge/15/release_notes/index.mdx @@ -10,8 +10,8 @@ cover what was new in each release. | Version | Release date | | ------------------------ | ------------ | -| [15.3](rel_notes15.3) | 2023 May 11 | -| [15.2](rel_notes15.2) | 2023 Feb 14 | +| [15.3](rel_notes15.3) | 11 May 2023 | +| [15.2](rel_notes15.2) | 14 Feb 2023 | diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx index 24731fc47b7..1b0236f8d2f 100644 --- a/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx +++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx @@ -18,8 +18,8 @@ The EDB Pgpool-II documentation describes the latest version of EDB Pgpool-II, i | Version | Release Date | Upstream merges | | | ------------------------------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | -| [4.4.2](442_rel_notes) | 2023 Feb 14 | Upstream [4.4.2](https://www.pgpool.net/docs/44/en/html/release-4-4-2.html) | | -| [4.3.2](07_432_rel_notes), [4.2.9](429_rel_notes), [4.1.12](4112_rel_notes), [4.0.19](4019_rel_notes), [3.7.24](3724_rel_notes) | 2022 Jul 05 | Upstream [4.3.2](https://www.pgpool.net/docs/43/en/html/release-4-3-2.html#bug-fixes), [4.2.9](https://www.pgpool.net/docs/43/en/html/release-4-2-9.html#bug-fixes), [4.1.12](https://www.pgpool.net/docs/43/en/html/release-4-1-12.html#bug-fixes), [4.0.19](https://www.pgpool.net/docs/43/en/html/release-4-0-19.html#bug-fixes), [3.7.24](https://www.pgpool.net/docs/43/en/html/release-3-7-24.html#bug-fixes) | | -| [4.3.0](08_430_rel_notes) | 2022 Feb 01 | Upstream [4.3.0](https://www.pgpool.net/docs/43/en/html/release-4-3-0.html#bug-fixes) | | -| [4.2.6](09_426_rel_notes) | 2021 Dec 01 | Upstream [4.2.6](https://www.pgpool.net/docs/42/en/html/release-4-2-6.html#bug-fixes) | | -| [4.2.5](10_425_rel_notes) | 2021 Jun 10 | Upstream [4.2.5](https://www.pgpool.net/docs/42/en/html/release-4-2-5.html) and [4.2.4](https://www.pgpool.net/docs/42/en/html/release-4-2-4.html) | | \ No newline at end of file +| [4.4.2](442_rel_notes) | 14 Feb 2023 | Upstream [4.4.2](https://www.pgpool.net/docs/44/en/html/release-4-4-2.html) | | +| [4.3.2](07_432_rel_notes), [4.2.9](429_rel_notes), [4.1.12](4112_rel_notes), [4.0.19](4019_rel_notes), [3.7.24](3724_rel_notes) | 05 Jul 2022 | Upstream [4.3.2](https://www.pgpool.net/docs/43/en/html/release-4-3-2.html#bug-fixes), [4.2.9](https://www.pgpool.net/docs/43/en/html/release-4-2-9.html#bug-fixes), [4.1.12](https://www.pgpool.net/docs/43/en/html/release-4-1-12.html#bug-fixes), [4.0.19](https://www.pgpool.net/docs/43/en/html/release-4-0-19.html#bug-fixes), [3.7.24](https://www.pgpool.net/docs/43/en/html/release-3-7-24.html#bug-fixes) | | +| [4.3.0](08_430_rel_notes) | 01 Feb 2022 | Upstream [4.3.0](https://www.pgpool.net/docs/43/en/html/release-4-3-0.html#bug-fixes) | | +| [4.2.6](09_426_rel_notes) | 01 Dec 2021 | Upstream [4.2.6](https://www.pgpool.net/docs/42/en/html/release-4-2-6.html#bug-fixes) | | +| [4.2.5](10_425_rel_notes) | 10 Jun 2021 | Upstream [4.2.5](https://www.pgpool.net/docs/42/en/html/release-4-2-5.html) and [4.2.4](https://www.pgpool.net/docs/42/en/html/release-4-2-4.html) | | \ No newline at end of file diff --git a/product_docs/docs/postgis/3.2/01_release_notes/index.mdx b/product_docs/docs/postgis/3.2/01_release_notes/index.mdx index ba879151a01..5a8edc43541 100644 --- a/product_docs/docs/postgis/3.2/01_release_notes/index.mdx +++ b/product_docs/docs/postgis/3.2/01_release_notes/index.mdx @@ -13,10 +13,10 @@ cover what was new in each release. | Version | Release date | | ------------------------ | ------------ | -| [3.2.1](rel_notes321) | 2022 Aug 04 | -| [3.2.0](rel_notes32) | 2022 Dec 01 | -| [3.1.5](rel_notes315) | 2022 Aug 03 | -| [3.1.4](rel_notes314) | 2021 Dec 01 | +| [3.2.1](rel_notes321) | 04 Aug 2022 | +| [3.2.0](rel_notes32) | 01 Dec 2022 | +| [3.1.5](rel_notes315) | 03 Aug 2022| +| [3.1.4](rel_notes314) | 01 Dec 2021| | [3.1.2](rel_notes312) | 2021 Jun 24| diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/rel_notes/index.mdx index a847b4e6165..cf3533088ad 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/rel_notes/index.mdx @@ -11,7 +11,7 @@ The EDB Postgres Distributed for Kubernetes documentation describes the major ve | Version | Release date | | -------------------------- | ------------ | -| [0.6.0](0_6_rel_notes) | 2023 May 15 | +| [0.6.0](0_6_rel_notes) | 15 May 2023 | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx index 335c160cdfa..a761c22c20c 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx @@ -63,58 +63,58 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | Version | Release date | Upstream merges | | -------------------------- | ------------ | ------------------------------------------------------------------------------------------- | -| [1.20.2](1_20_2_rel_notes) | 2023 Jul 27 | Upstream [1.20.2](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | -| [1.20.1](1_20_1_rel_notes) | 2023 Jun 13 | Upstream [1.20.1](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | -| [1.20.0](1_20_0_rel_notes) | 2023 Apr 27 | Upstream [1.20.0](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | -| [1.19.4](1_19_4_rel_notes) | 2023 Jul 27 | Upstream [1.19.4](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | -| [1.19.3](1_19_3_rel_notes) | 2023 Jun 13 | Upstream [1.19.3](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | -| [1.19.2](1_19_2_rel_notes) | 2023 Apr 27 | Upstream [1.19.2](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | -| [1.19.1](1_19_1_rel_notes) | 2023 Mar 20 | Upstream [1.19.1](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | -| [1.19.0](1_19_0_rel_notes) | 2023 Feb 14 | Upstream [1.19.0](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | -| [1.18.6](1_18_6_rel_notes) | 2023 Jul 27 | None | -| [1.18.5](1_18_5_rel_notes) | 2023 Jun 13 | Upstream [1.18.5](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.18.4](1_18_4_rel_notes) | 2023 Apr 27 | Upstream [1.18.4](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.18.3](1_18_3_rel_notes) | 2023 Mar 20 | Upstream [1.18.3](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.18.2](1_18_2_rel_notes) | 2023 Feb 14 | Upstream [1.18.2](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.18.1](1_18_1_rel_notes) | 2022 Dec 21 | Upstream [1.18.1](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.18.0](1_18_0_rel_notes) | 2022 Nov 14 | Upstream [1.18.0](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.17.5](1_17_5_rel_notes) | 2023 Mar 20 | Upstream [1.17.5](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.4](1_17_4_rel_notes) | 2023 Feb 14 | Upstream [1.17.4](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.3](1_17_3_rel_notes) | 2022 Dec 21 | Upstream [1.17.3](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.2](1_17_2_rel_notes) | 2022 Nov 14 | Upstream [1.17.2](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.1](1_17_1_rel_notes) | 2022 Oct 7 | Upstream [1.17.1](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.0](1_17_rel_notes) | 2022 Sep 6 | Upstream [1.17.0](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.16.4](1_16_4_rel_notes) | 2022 Nov 14 | Upstream [1.16.4](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | -| [1.16.3](1_16_3_rel_notes) | 2022 Oct 7 | Upstream [1.16.3](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | -| [1.16.2](1_16_2_rel_notes) | 2022 Sep 6 | Upstream [1.16.2](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | -| [1.16.1](1_16_1_rel_notes) | 2022 Aug 12 | Upstream [1.16.1](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | -| [1.16.0](1_16_rel_notes) | 2022 Jul 07 | Upstream [1.16.0](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16) | -| [1.15.5](1_15_5_rel_notes) | 2022 Oct 7 | Upstream [1.15.5](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.15.4](1_15_4_rel_notes) | 2022 Sep 6 | Upstream [1.15.4](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.15.3](1_15_3_rel_notes) | 2022 Aug 12 | Upstream [1.15.3](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.15.2](1_15_2_rel_notes) | 2022 Jul 07 | Upstream [1.15.2](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.15.1](1_15_1_rel_notes) | 2022 May 27 | Upstream [1.15.1](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.15.0](1_15_rel_notes) | 2022 Apr 21 | Upstream [1.15.0](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.14.0](1_14_rel_notes) | 2022 Mar 25 | NA | -| [1.13.0](1_13_rel_notes) | 2022 Feb 17 | NA | -| [1.12.0](1_12_rel_notes) | 2022 Jan 11 | NA | -| [1.11.0](1_11_rel_notes) | 2021 Dec 15 | NA | -| [1.10.0](1_10_rel_notes) | 2021 Nov 11 | NA | -| [1.9.2](1_9_2_rel_notes) | 2021 Oct 15 | NA | -| [1.9.1](1_9_1_rel_notes) | 2021 Sep 30 | NA | -| [1.9.0](1_9_rel_notes) | 2021 Sep 28 | NA | -| [1.8.0](1_8_rel_notes) | 2021 Sep 13 | NA | -| [1.7.1](1_7_1_rel_notes) | 2021 Aug 11 | NA | -| [1.7.0](1_7_rel_notes) | 2021 Jul 28 | NA | -| [1.6.0](1_6_rel_notes) | 2021 Jul 12 | NA | -| [1.5.1](1_5_1_rel_notes) | 2021 Jun 11 | NA | -| [1.5.0](1_5_rel_notes) | 2021 Jun 17 | NA | -| [1.4.0](1_4_rel_notes) | 2021 May 18 | NA | -| [1.3.0](1_3_rel_notes) | 2021 Apr 23 | NA | -| [1.2.1](1_2_1_rel_notes) | 2021 Apr 06 | NA | -| [1.2.0](1_2_rel_notes) | 2021 Mar 31 | NA | -| [1.1.0](1_1_rel_notes) | 2021 Mar 03 | NA | -| [1.0.0](1_0_rel_notes) | 2021 Feb 04 | NA | +| [1.20.2](1_20_2_rel_notes) | 27 Jul 2023 | Upstream [1.20.2](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | +| [1.20.1](1_20_1_rel_notes) | 13 Jun 2023 | Upstream [1.20.1](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | +| [1.20.0](1_20_0_rel_notes) | 27 Apr 2023 | Upstream [1.20.0](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | +| [1.19.4](1_19_4_rel_notes) | 27 Jul 2023 | Upstream [1.19.4](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | +| [1.19.3](1_19_3_rel_notes) | 13 Jun 2023 | Upstream [1.19.3](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | +| [1.19.2](1_19_2_rel_notes) | 27 Apr 2023 | Upstream [1.19.2](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | +| [1.19.1](1_19_1_rel_notes) | 20 Mar 2023 | Upstream [1.19.1](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | +| [1.19.0](1_19_0_rel_notes) | 14 Feb 2023 | Upstream [1.19.0](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | +| [1.18.6](1_18_6_rel_notes) | 27 Jul 2023 | None | +| [1.18.5](1_18_5_rel_notes) | 13 Jun 2023 | Upstream [1.18.5](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.18.4](1_18_4_rel_notes) | 27 Apr 2023 | Upstream [1.18.4](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.18.3](1_18_3_rel_notes) | 20 Mar 2023 | Upstream [1.18.3](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.18.2](1_18_2_rel_notes) | 14 Feb 2023 | Upstream [1.18.2](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.18.1](1_18_1_rel_notes) | 21 Dec 2022 | Upstream [1.18.1](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.18.0](1_18_0_rel_notes) | 14 Nov 2022 | Upstream [1.18.0](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.17.5](1_17_5_rel_notes) | 20 Mar 2023 | Upstream [1.17.5](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.4](1_17_4_rel_notes) | 14 Feb 2023 | Upstream [1.17.4](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.3](1_17_3_rel_notes) | 21 Dec 2022 | Upstream [1.17.3](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.2](1_17_2_rel_notes) | 14 Nov 2022 | Upstream [1.17.2](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.1](1_17_1_rel_notes) | 7 Oct 2022 | Upstream [1.17.1](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.0](1_17_rel_notes) | 6 Sep 2022 | Upstream [1.17.0](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.16.4](1_16_4_rel_notes) | 14 Nov 2022 | Upstream [1.16.4](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | +| [1.16.3](1_16_3_rel_notes) | 7 Oct 2022 | Upstream [1.16.3](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | +| [1.16.2](1_16_2_rel_notes) | 6 Sep 2022 | Upstream [1.16.2](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | +| [1.16.1](1_16_1_rel_notes) | 12 Aug 2022 | Upstream [1.16.1](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | +| [1.16.0](1_16_rel_notes) | 07 Jul 2022 | Upstream [1.16.0](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16) | +| [1.15.5](1_15_5_rel_notes) | 7 Oct 2022 | Upstream [1.15.5](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.4](1_15_4_rel_notes) | 6 Sep 2022 | Upstream [1.15.4](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.3](1_15_3_rel_notes) | 12 Aug 2022 | Upstream [1.15.3](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.2](1_15_2_rel_notes) | 07 Jul 2022 | Upstream [1.15.2](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.1](1_15_1_rel_notes) | 27 May 2022 | Upstream [1.15.1](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.0](1_15_rel_notes) | 21 Apr 2022 | Upstream [1.15.0](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.14.0](1_14_rel_notes) | 25 Mar 2022 | NA | +| [1.13.0](1_13_rel_notes) | 17 Feb 2022 | NA | +| [1.12.0](1_12_rel_notes) | 11 Jan 2022 | NA | +| [1.11.0](1_11_rel_notes) | 15 Dec 2021 | NA | +| [1.10.0](1_10_rel_notes) | 11 Nov 2021 | NA | +| [1.9.2](1_9_2_rel_notes) | 15 Oct 2021 | NA | +| [1.9.1](1_9_1_rel_notes) | 30 Sep 2021 | NA | +| [1.9.0](1_9_rel_notes) | 28 Sep 2021 | NA | +| [1.8.0](1_8_rel_notes) | 13 Sep 2021 | NA | +| [1.7.1](1_7_1_rel_notes) | 11 Aug 2021 | NA | +| [1.7.0](1_7_rel_notes) | 28 Jul 2021 | NA | +| [1.6.0](1_6_rel_notes) | 12 Jul 2021 | NA | +| [1.5.1](1_5_1_rel_notes) | 11 Jun 2021 | NA | +| [1.5.0](1_5_rel_notes) | 17 Jun 2021 | NA | +| [1.4.0](1_4_rel_notes) | 18 May 2021 | NA | +| [1.3.0](1_3_rel_notes) | 23 Apr 2021 | NA | +| [1.2.1](1_2_1_rel_notes) | 06 Apr 2021 | NA | +| [1.2.0](1_2_rel_notes) | 31 Mar 2021 | NA | +| [1.1.0](1_1_rel_notes) | 03 Mar 2021 | NA | +| [1.0.0](1_0_rel_notes) | 04 Feb 2021 | NA | From 29aaf6b64571e62839e395bec6b3b309512a0e2f Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:35:06 -0400 Subject: [PATCH 032/223] added digit to day and fixed two rows that got missed --- product_docs/docs/efm/4/efm_rel_notes/index.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/efm/4/efm_rel_notes/index.mdx b/product_docs/docs/efm/4/efm_rel_notes/index.mdx index b25f4fe7c17..6eb796f3255 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/index.mdx +++ b/product_docs/docs/efm/4/efm_rel_notes/index.mdx @@ -12,11 +12,11 @@ about the release that introduced the feature. | [4.7](03_efm_47_rel_notes) | 20 Jun 2023| | [4.6](04_efm_46_rel_notes) | 14 Feb 2023| | [4.5](05_efm_45_rel_notes) | 30 Aug 2022| -| [4.4](06_efm_44_rel_notes) | 5 Jan 2022| -| [4.3](07_efm_43_rel_notes) | 2021 Dec 18| -| [4.2](08_efm_42_rel_notes) | 2021 Apr 19| +| [4.4](06_efm_44_rel_notes) | 05 Jan 2022| +| [4.3](07_efm_43_rel_notes) | 18 Dec 2021| +| [4.2](08_efm_42_rel_notes) | 19 Apr 2021 | | [4.1](09_efm_41_rel_notes) | 11 Dec 2021| -| [4.0](10_efm_40_rel_notes) | 2 Sep 2021 | +| [4.0](10_efm_40_rel_notes) | 02 Sep 2021 | From d16b54fe4f01d9dad50cbcbfd16e6a48d8246995 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:40:14 -0400 Subject: [PATCH 033/223] fixed inadvertent change --- .../04_control_schema_objects_created_for_publication.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx b/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx index 3a205855418..a9e46eded50 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx @@ -411,7 +411,7 @@ _edb_replicator_pub.sp_dropsequence SQL_STORED_PROCEDURE _edb_replicator_sub.rrep_common_seq USER_TABLE ``` -SQL Server versions 2014 and 2012support creation of sequence objects that can now perform the functionality previously provided by the preceding list of objects. The following are the sequence objects that are now used when the publication database is SQL Server 2012 or 2014: +SQL Server versions 2014 and 2012 support creation of sequence objects that can now perform the functionality previously provided by the preceding list of objects. The following are the sequence objects that are now used when the publication database is SQL Server 2012 or 2014: ```shell 1> USE edb; From 168dbf950439b16b8076353efdbf430a597f7a0c Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:45:17 -0400 Subject: [PATCH 034/223] made day two digits --- .../docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx index 7c72652e3e8..95b0f91177f 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx @@ -15,7 +15,7 @@ These release notes describe what's new in each release. When a minor or patch r | ---------------------------------------- | ------------ | | [42.5.4.1](jdbc_42.5.4.1_rel_notes) | 16 Mar 2023 | | [42.5.1.2](jdbc_42.5.1.2_rel_notes) | 14 Feb 2023 | -| [42.5.1.1](jdbc_42.5.1.1_rel_notes) | 9 Dec 2022 | +| [42.5.1.1](jdbc_42.5.1.1_rel_notes) | 09 Dec 2022 | | [42.5.0.1](jdbc_42.5.0.1_rel_notes) | 1 Sep 2022 | | [42.3.3.1](08_jdbc_42.3.3.1_rel_notes) | 20 Apr 2022 | | [42.3.2.1](09_jdbc_42.3.2.1_rel_notes) | 15 Feb 2022 | From 2fd8210bce0e31793cd836b7c54fd7a4047fde53 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:45:56 -0400 Subject: [PATCH 035/223] made day two digits --- .../docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx index 95b0f91177f..0f26c6d3125 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx @@ -16,7 +16,7 @@ These release notes describe what's new in each release. When a minor or patch r | [42.5.4.1](jdbc_42.5.4.1_rel_notes) | 16 Mar 2023 | | [42.5.1.2](jdbc_42.5.1.2_rel_notes) | 14 Feb 2023 | | [42.5.1.1](jdbc_42.5.1.1_rel_notes) | 09 Dec 2022 | -| [42.5.0.1](jdbc_42.5.0.1_rel_notes) | 1 Sep 2022 | +| [42.5.0.1](jdbc_42.5.0.1_rel_notes) | 01 Sep 2022 | | [42.3.3.1](08_jdbc_42.3.3.1_rel_notes) | 20 Apr 2022 | | [42.3.2.1](09_jdbc_42.3.2.1_rel_notes) | 15 Feb 2022 | | [42.2.24.1](10_jdbc_42.2.24.1_rel_notes) | 5 Nov 2021 | From e2d4e1065abe70b851dd14b1c59cf3c5f82cf252 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:46:07 -0400 Subject: [PATCH 036/223] made day two digits --- product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx b/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx index 70a8e648c0d..63ce06b4210 100644 --- a/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx +++ b/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx @@ -9,5 +9,5 @@ Release notes describe what is new in a release. When a minor or patch release i | Version | Release Date | | ------------------------------------------- | ------------ | | [12.02.0000.02](01_odbc_12.2.0.2_rel_notes) | 16 Nov 2021 | -| [12.00.0000.02](03_odbc_12.0.0.2_rel_notes) | 9 Aug 2020 | +| [12.00.0000.02](03_odbc_12.0.0.2_rel_notes) | 09 Aug 2020 | From 5274fd2569b71dad7838adde87b7fe713c46b9b0 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:46:34 -0400 Subject: [PATCH 037/223] Fixed missed row --- product_docs/docs/postgis/3.2/01_release_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/postgis/3.2/01_release_notes/index.mdx b/product_docs/docs/postgis/3.2/01_release_notes/index.mdx index 5a8edc43541..769dc9c3e12 100644 --- a/product_docs/docs/postgis/3.2/01_release_notes/index.mdx +++ b/product_docs/docs/postgis/3.2/01_release_notes/index.mdx @@ -17,7 +17,7 @@ cover what was new in each release. | [3.2.0](rel_notes32) | 01 Dec 2022 | | [3.1.5](rel_notes315) | 03 Aug 2022| | [3.1.4](rel_notes314) | 01 Dec 2021| -| [3.1.2](rel_notes312) | 2021 Jun 24| +| [3.1.2](rel_notes312) | 24 Jun 2021 | From b1dff672246039604b3a293cf26b3900fc69091e Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:48:38 -0400 Subject: [PATCH 038/223] made day two digits --- product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx index a761c22c20c..c2aa5e5f555 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx @@ -82,7 +82,7 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | [1.17.4](1_17_4_rel_notes) | 14 Feb 2023 | Upstream [1.17.4](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.17.3](1_17_3_rel_notes) | 21 Dec 2022 | Upstream [1.17.3](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.17.2](1_17_2_rel_notes) | 14 Nov 2022 | Upstream [1.17.2](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.1](1_17_1_rel_notes) | 7 Oct 2022 | Upstream [1.17.1](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.1](1_17_1_rel_notes) | 07 Oct 2022 | Upstream [1.17.1](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.17.0](1_17_rel_notes) | 6 Sep 2022 | Upstream [1.17.0](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.16.4](1_16_4_rel_notes) | 14 Nov 2022 | Upstream [1.16.4](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.3](1_16_3_rel_notes) | 7 Oct 2022 | Upstream [1.16.3](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | From 883e90d6ba04a7baa32d8392bbd46965d11e0171 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:48:49 -0400 Subject: [PATCH 039/223] made day two digits --- product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx index c2aa5e5f555..1b887972507 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx @@ -83,7 +83,7 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | [1.17.3](1_17_3_rel_notes) | 21 Dec 2022 | Upstream [1.17.3](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.17.2](1_17_2_rel_notes) | 14 Nov 2022 | Upstream [1.17.2](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.17.1](1_17_1_rel_notes) | 07 Oct 2022 | Upstream [1.17.1](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.0](1_17_rel_notes) | 6 Sep 2022 | Upstream [1.17.0](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.0](1_17_rel_notes) | 06 Sep 2022 | Upstream [1.17.0](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.16.4](1_16_4_rel_notes) | 14 Nov 2022 | Upstream [1.16.4](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.3](1_16_3_rel_notes) | 7 Oct 2022 | Upstream [1.16.3](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.2](1_16_2_rel_notes) | 6 Sep 2022 | Upstream [1.16.2](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | From 6d8a7397dfd876ab08ffe0aaa4cdd353c9332c2f Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:48:59 -0400 Subject: [PATCH 040/223] made day two digits --- product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx index 1b887972507..f6d2ab9413c 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx @@ -85,7 +85,7 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | [1.17.1](1_17_1_rel_notes) | 07 Oct 2022 | Upstream [1.17.1](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.17.0](1_17_rel_notes) | 06 Sep 2022 | Upstream [1.17.0](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.16.4](1_16_4_rel_notes) | 14 Nov 2022 | Upstream [1.16.4](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | -| [1.16.3](1_16_3_rel_notes) | 7 Oct 2022 | Upstream [1.16.3](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | +| [1.16.3](1_16_3_rel_notes) | 07 Oct 2022 | Upstream [1.16.3](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.2](1_16_2_rel_notes) | 6 Sep 2022 | Upstream [1.16.2](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.1](1_16_1_rel_notes) | 12 Aug 2022 | Upstream [1.16.1](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.0](1_16_rel_notes) | 07 Jul 2022 | Upstream [1.16.0](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16) | From cf18eeb9c71ecc42dbdc956d727cc77d05e6706b Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:49:12 -0400 Subject: [PATCH 041/223] made day two digits --- product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx index f6d2ab9413c..c511b176546 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx @@ -86,7 +86,7 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | [1.17.0](1_17_rel_notes) | 06 Sep 2022 | Upstream [1.17.0](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.16.4](1_16_4_rel_notes) | 14 Nov 2022 | Upstream [1.16.4](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.3](1_16_3_rel_notes) | 07 Oct 2022 | Upstream [1.16.3](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | -| [1.16.2](1_16_2_rel_notes) | 6 Sep 2022 | Upstream [1.16.2](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | +| [1.16.2](1_16_2_rel_notes) | 06 Sep 2022 | Upstream [1.16.2](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.1](1_16_1_rel_notes) | 12 Aug 2022 | Upstream [1.16.1](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.0](1_16_rel_notes) | 07 Jul 2022 | Upstream [1.16.0](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16) | | [1.15.5](1_15_5_rel_notes) | 7 Oct 2022 | Upstream [1.15.5](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | From d5d79460654dfe13dae7288d0abe51dabed213d7 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:49:27 -0400 Subject: [PATCH 042/223] made day two digits --- product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx index c511b176546..b5f5d3aa9d7 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx @@ -89,7 +89,7 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | [1.16.2](1_16_2_rel_notes) | 06 Sep 2022 | Upstream [1.16.2](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.1](1_16_1_rel_notes) | 12 Aug 2022 | Upstream [1.16.1](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.0](1_16_rel_notes) | 07 Jul 2022 | Upstream [1.16.0](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16) | -| [1.15.5](1_15_5_rel_notes) | 7 Oct 2022 | Upstream [1.15.5](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.5](1_15_5_rel_notes) | 07 Oct 2022 | Upstream [1.15.5](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | | [1.15.4](1_15_4_rel_notes) | 6 Sep 2022 | Upstream [1.15.4](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | | [1.15.3](1_15_3_rel_notes) | 12 Aug 2022 | Upstream [1.15.3](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | | [1.15.2](1_15_2_rel_notes) | 07 Jul 2022 | Upstream [1.15.2](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | From 72531e3d61c9c1860e883ae0a2eefe16addd2e0c Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 22 Aug 2023 13:49:40 -0400 Subject: [PATCH 043/223] made day two digits --- product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx index b5f5d3aa9d7..d490711144a 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx @@ -90,7 +90,7 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | [1.16.1](1_16_1_rel_notes) | 12 Aug 2022 | Upstream [1.16.1](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.0](1_16_rel_notes) | 07 Jul 2022 | Upstream [1.16.0](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16) | | [1.15.5](1_15_5_rel_notes) | 07 Oct 2022 | Upstream [1.15.5](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.15.4](1_15_4_rel_notes) | 6 Sep 2022 | Upstream [1.15.4](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.4](1_15_4_rel_notes) | 06 Sep 2022 | Upstream [1.15.4](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | | [1.15.3](1_15_3_rel_notes) | 12 Aug 2022 | Upstream [1.15.3](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | | [1.15.2](1_15_2_rel_notes) | 07 Jul 2022 | Upstream [1.15.2](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | | [1.15.1](1_15_1_rel_notes) | 27 May 2022 | Upstream [1.15.1](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | From 0b16cbfb70ee8422d86a61d60942bb2316cf8d5b Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 21 Aug 2023 14:28:25 -0400 Subject: [PATCH 044/223] OCL Connector: 15.2.0.4 release --- .../15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx | 10 ++++++++++ .../docs/ocl_connector/15/ocl_rel_notes/index.mdx | 2 ++ 2 files changed, 12 insertions(+) create mode 100644 product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx new file mode 100644 index 00000000000..326a3eb5878 --- /dev/null +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx @@ -0,0 +1,10 @@ +--- +title: "Version 15.2.0.4" +--- +The EDB OCL Connector provides an API similar to the Oracle Call Interface. + +New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 15.2.0.4 include: + +| Type | Description | +| ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Bug fix | Fixed a regression whereby a spurious rollback/begin occurs after deallocating a statement. [Support ticket: #94735]| diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx index a174db2f141..4af95474060 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx @@ -2,6 +2,7 @@ title: "EDB OCL Connector release notes" navTitle: Release Notes navigation: + - 15.2.0.4_ocl_release_notes - 15.2.0.3_ocl_release_notes - 15.2.0.2_ocl_release_notes - 01_ocl_release_notes @@ -13,6 +14,7 @@ Release notes describe what's new in a release. When a minor or patch release in | Version | Release date | | -------------------------------------- | ------------ | +| [15.2.0.4](15.2.0.4_ocl_release_notes) | 22 Aug 2023 | | [15.2.0.3](15.2.0.3_ocl_release_notes) | 20 Jun 2023 | | [15.2.0.2](15.2.0.2_ocl_release_notes) | 19 May 2023 | | [15.2.0.1](01_ocl_release_notes) | 14 Feb 2023 | From c97f6ef61b0a19c3d309a00c14df50437cc19bc2 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 22 Aug 2023 08:59:26 -0400 Subject: [PATCH 045/223] added epas 15.x requirement --- .../docs/ocl_connector/15/02_supported_platforms.mdx | 10 ++++++++++ .../15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx | 1 + 2 files changed, 11 insertions(+) diff --git a/product_docs/docs/ocl_connector/15/02_supported_platforms.mdx b/product_docs/docs/ocl_connector/15/02_supported_platforms.mdx index 9bf7285cd7b..127652f9ef4 100644 --- a/product_docs/docs/ocl_connector/15/02_supported_platforms.mdx +++ b/product_docs/docs/ocl_connector/15/02_supported_platforms.mdx @@ -7,3 +7,13 @@ title: "Supported platforms" The EDB OCL Connector is supported on the same platforms as EDB Postgres Advanced Server. To determine the platform support for the EDB OCL Connector, you can either refer to the platform support for EDB Postgres Advanced Server on the [Platform Compatibility page](https://www.enterprisedb.com/platform-compatibility#epas) on the EDB website or refer to [Installing EDB OCL Connector](./installing). +## Supported database versions + +This table lists the latest OCL Connector versions and their supported corresponding EDB Postgres Advanced Server (EPAS) versions. + +| ODBC Connector | EPAS 15.4 | EPAS 15.3 | EPAS 15.2 | EPAS 15.1 | +| -------------------------------------- | --------- | --------- | --------- | --------- | +| [15.2.0.4](15.2.0.4_ocl_release_notes) | Y | N | N | N | +| [15.2.0.3](15.2.0.3_ocl_release_notes) | N | Y | Y | Y | +| [15.2.0.2](15.2.0.2_ocl_release_notes) | N | N | Y | Y | +| [15.2.0.1](01_ocl_release_notes) | N | N | N | Y | diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx index 326a3eb5878..d57e5ccc853 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx @@ -8,3 +8,4 @@ New features, enhancements, bug fixes, and other changes in the EDB OCL Connecto | Type | Description | | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | Bug fix | Fixed a regression whereby a spurious rollback/begin occurs after deallocating a statement. [Support ticket: #94735]| +| Change | This version works with EDB Postgres Advanced Server 15 and later. | From ee9b8ae2e846c25786c64c1e89c8024b3f421f07 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 24 Aug 2023 10:11:25 -0400 Subject: [PATCH 046/223] added note instead of table --- .../docs/ocl_connector/15/02_supported_platforms.mdx | 10 ---------- .../15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx | 4 +++- 2 files changed, 3 insertions(+), 11 deletions(-) diff --git a/product_docs/docs/ocl_connector/15/02_supported_platforms.mdx b/product_docs/docs/ocl_connector/15/02_supported_platforms.mdx index 127652f9ef4..9bf7285cd7b 100644 --- a/product_docs/docs/ocl_connector/15/02_supported_platforms.mdx +++ b/product_docs/docs/ocl_connector/15/02_supported_platforms.mdx @@ -7,13 +7,3 @@ title: "Supported platforms" The EDB OCL Connector is supported on the same platforms as EDB Postgres Advanced Server. To determine the platform support for the EDB OCL Connector, you can either refer to the platform support for EDB Postgres Advanced Server on the [Platform Compatibility page](https://www.enterprisedb.com/platform-compatibility#epas) on the EDB website or refer to [Installing EDB OCL Connector](./installing). -## Supported database versions - -This table lists the latest OCL Connector versions and their supported corresponding EDB Postgres Advanced Server (EPAS) versions. - -| ODBC Connector | EPAS 15.4 | EPAS 15.3 | EPAS 15.2 | EPAS 15.1 | -| -------------------------------------- | --------- | --------- | --------- | --------- | -| [15.2.0.4](15.2.0.4_ocl_release_notes) | Y | N | N | N | -| [15.2.0.3](15.2.0.3_ocl_release_notes) | N | Y | Y | Y | -| [15.2.0.2](15.2.0.2_ocl_release_notes) | N | N | Y | Y | -| [15.2.0.1](01_ocl_release_notes) | N | N | N | Y | diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx index d57e5ccc853..a401f116870 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx @@ -8,4 +8,6 @@ New features, enhancements, bug fixes, and other changes in the EDB OCL Connecto | Type | Description | | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | Bug fix | Fixed a regression whereby a spurious rollback/begin occurs after deallocating a statement. [Support ticket: #94735]| -| Change | This version works with EDB Postgres Advanced Server 15 and later. | + +!!!Important + This version requires EDB Postgres Advanced Server 15.4 or later. From f42d2b7a0e5f1d2f2ea15811fca64ead7d437d1a Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 24 Aug 2023 10:29:02 -0400 Subject: [PATCH 047/223] fixed date --- product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx index 4af95474060..861724d4958 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx @@ -14,7 +14,7 @@ Release notes describe what's new in a release. When a minor or patch release in | Version | Release date | | -------------------------------------- | ------------ | -| [15.2.0.4](15.2.0.4_ocl_release_notes) | 22 Aug 2023 | +| [15.2.0.4](15.2.0.4_ocl_release_notes) | 24 Aug 2023 | | [15.2.0.3](15.2.0.3_ocl_release_notes) | 20 Jun 2023 | | [15.2.0.2](15.2.0.2_ocl_release_notes) | 19 May 2023 | | [15.2.0.1](01_ocl_release_notes) | 14 Feb 2023 | From 7b3b6df3928b42802189530857404a6a27f19223 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 24 Aug 2023 10:51:28 -0400 Subject: [PATCH 048/223] Fixed consistency and logo issues Missing exclamation point for several images --- .../02-PartnerInformation.mdx | 2 +- .../CommvaultBackupandRecovery/02-PartnerInformation.mdx | 4 ++-- .../02-PartnerInformation.mdx | 2 +- advocacy_docs/partner_docs/HashicorpVault/index.mdx | 2 +- .../partner_docs/ImpervaDataSecurityFabric/index.mdx | 2 +- .../partner_docs/LiquibasePro/02-PartnerInformation.mdx | 2 +- .../partner_docs/QuestToadEdge/02-PartnerInformation.mdx | 2 +- .../02-PartnerInformation.mdx | 2 +- .../partner_docs/SIBVisionsVisionX/02-PartnerInformation.mdx | 2 +- .../02-PartnerInformation.mdx | 2 +- .../VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx | 4 ++-- .../partner_docs/VeritasNetBackupforPostgreSQL/index.mdx | 2 +- 12 files changed, 14 insertions(+), 14 deletions(-) diff --git a/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/02-PartnerInformation.mdx index 1e7fc5e6322..60ad95e9d22 100644 --- a/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/02-PartnerInformation.mdx @@ -1,6 +1,6 @@ --- title: 'Partner information' -description: 'Details for Cohesity DataProtect for PostgreSQL' +description: 'Details of the partner' --- |   |   | diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx index d6abe7d2c7b..34a7b7cd7e0 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx @@ -1,11 +1,11 @@ --- title: 'Partner information' -description: 'Details of the Partner' +description: 'Details of the partner' --- |   |   | | ----------- | ----------- | -| **Partner Name** | Commvault | +| **Partner name** | Commvault | | **Partner product** | Commvault Backup & Recovery | | **Website** | https://www.commvault.com/ | | **Version** | Commvault Backup & Recovery 11.32 | diff --git a/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/02-PartnerInformation.mdx index 38fd7c9672d..6c1803e05c1 100644 --- a/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/02-PartnerInformation.mdx @@ -1,6 +1,6 @@ --- title: 'Partner information' -description: 'Details for Esri ArcGIS Pro and Esri ArcGIS Enterprise' +description: 'Details of the partner' --- |   |   | diff --git a/advocacy_docs/partner_docs/HashicorpVault/index.mdx b/advocacy_docs/partner_docs/HashicorpVault/index.mdx index 69c4276def1..e32eabb75b0 100644 --- a/advocacy_docs/partner_docs/HashicorpVault/index.mdx +++ b/advocacy_docs/partner_docs/HashicorpVault/index.mdx @@ -6,7 +6,7 @@ directoryDefaults: --- -[Partner Program Logo](Images/PartnerProgram.jpg.png) +![Partner Program Logo](Images/PartnerProgram.jpg.png)

EDB GlobalConnect Technology Partner Implementation Guide

Hashicorp Vault

diff --git a/advocacy_docs/partner_docs/ImpervaDataSecurityFabric/index.mdx b/advocacy_docs/partner_docs/ImpervaDataSecurityFabric/index.mdx index ae4269e96ea..7ef8c02bb31 100644 --- a/advocacy_docs/partner_docs/ImpervaDataSecurityFabric/index.mdx +++ b/advocacy_docs/partner_docs/ImpervaDataSecurityFabric/index.mdx @@ -5,7 +5,7 @@ directoryDefaults: iconName: handshake --- -[Partner Program Logo](Images/PartnerProgram.jpg.png) +![Partner Program Logo](Images/PartnerProgram.jpg.png)

EDB GlobalConnect Technology Partner Implementation Guide

Imperva Data Security Fabric

diff --git a/advocacy_docs/partner_docs/LiquibasePro/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/LiquibasePro/02-PartnerInformation.mdx index 24f8aa73b99..2f5b2ece766 100644 --- a/advocacy_docs/partner_docs/LiquibasePro/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/LiquibasePro/02-PartnerInformation.mdx @@ -1,6 +1,6 @@ --- title: 'Partner information' -description: 'Details for Liquibase Pro' +description: 'Details of the partner' --- |   |   | diff --git a/advocacy_docs/partner_docs/QuestToadEdge/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/QuestToadEdge/02-PartnerInformation.mdx index 273342c48a9..48874d8d86e 100644 --- a/advocacy_docs/partner_docs/QuestToadEdge/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/QuestToadEdge/02-PartnerInformation.mdx @@ -1,6 +1,6 @@ --- title: 'Partner information' -description: 'Details for Quest Toad Edge' +description: 'Details of the partner' --- |   |   | diff --git a/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/02-PartnerInformation.mdx index 19f05b129e3..ecb1da7c521 100644 --- a/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/02-PartnerInformation.mdx @@ -1,6 +1,6 @@ --- title: 'Partner information' -description: 'Details for Repostor Data Protector for PostgreSQL' +description: 'Details of the partner' redirects: - /partner_docs/RepostorGuide/02-PartnerInformation/ --- diff --git a/advocacy_docs/partner_docs/SIBVisionsVisionX/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/SIBVisionsVisionX/02-PartnerInformation.mdx index 2f238a1e9fc..be58e3e5eb5 100644 --- a/advocacy_docs/partner_docs/SIBVisionsVisionX/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/SIBVisionsVisionX/02-PartnerInformation.mdx @@ -1,6 +1,6 @@ --- title: 'Partner information' -description: 'Details for SIB Visions VisionX' +description: 'Details of the partner' --- |   |   | diff --git a/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/02-PartnerInformation.mdx index 1432e2264c4..159b187f912 100644 --- a/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/02-PartnerInformation.mdx @@ -1,6 +1,6 @@ --- title: 'Partner information' -description: 'Details for Thales CipherTrust Transparent Encryption (CTE)' +description: 'Details of the partner' --- diff --git a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx index 81606f06565..a4a7734d758 100644 --- a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx @@ -1,13 +1,13 @@ --- title: 'Partner information' -description: 'Details for Veritas NetBackup for PostgreSQL' +description: 'Details of the parnter' redirects: - /partner_docs/VeritasGuide/02-PartnerInformation/ --- |   |   | | ----------- | ----------- | | **Partner name** | Veritas | -| **Partner Product** | NetBackup for PostgreSQL | +| **Partner product** | NetBackup for PostgreSQL | | **Website** | https://www.veritas.com/ | | **Version & platform** | NetBackup for PostgreSQL 9.1: Linux, Windows | | **Product description** | Veritas NetBackup gives enterprise IT a simple and powerful way to ensure the integrity and availability of their dataa—from edge to core to cloud. Veritas NetBackup for PostgreSQL Agent extends the capabilities of NetBackup to include backup and restore of PostgreSQL databases. | diff --git a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/index.mdx b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/index.mdx index d8e90d8b500..50f5645a5eb 100644 --- a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/index.mdx +++ b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/index.mdx @@ -6,7 +6,7 @@ directoryDefaults: --- -[Partner Program Logo](Images/EDBPartnerProgram.png) +![Partner Program Logo](Images/EDBPartnerProgram.png)

EDB GlobalConnect Technology Partner Implementation Guide

Veritas NetBackup for PostgreSQL

From 6f4b6d25f040a94b51635d8ec67b4e561c0db302 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 16 Aug 2023 09:59:46 +0100 Subject: [PATCH 049/223] Styleguide and supporting content updated Signed-off-by: Dj Walker-Morgan --- .../community/contributing/index.mdx | 17 +- advocacy_docs/community/contributing/repo.mdx | 2 +- .../community/contributing/styleguide.mdx | 523 ++++++++++++++++++ advocacy_docs/community/index.mdx | 12 + 4 files changed, 546 insertions(+), 8 deletions(-) create mode 100644 advocacy_docs/community/contributing/styleguide.mdx create mode 100644 advocacy_docs/community/index.mdx diff --git a/advocacy_docs/community/contributing/index.mdx b/advocacy_docs/community/contributing/index.mdx index 7c09679cf3e..e754ebc07f2 100644 --- a/advocacy_docs/community/contributing/index.mdx +++ b/advocacy_docs/community/contributing/index.mdx @@ -1,19 +1,23 @@ --- -title: We love feedback! -navTitle: Feedback +title: Contributing Feedback and More +navTitle: Contributing description: Guidelines for offering feedback to EDB Docs. iconName: IdeaSharing --- All feedback is welcome: -1. an idea for something new +Is it a simple edit for a typo? Use the **Suggest Edits** button and you can make a change to the docs which we'll review it. + +If, on the other hand you: + +1. have an idea for something new 2. you feel there's something missing -3. a mistake +3. you can see a mistake thats more than a typo -Github Issues is the fastest way to get that feedback in front of us. +Then Github Issues is the fastest way to get that feedback in front of us. -[Open an issue on Github →](https://github.com/rocketinsights/edb_docs_advocacy/issues) +[Open an issue on Github →](https://github.com/EnterpriseDB/docs/issues) --- @@ -22,4 +26,3 @@ Github Issues is the fastest way to get that feedback in front of us. The only things we love more than feedback are pull requests. Check out [the README on Github](https://github.com/EnterpriseDB/docs) to get started. - diff --git a/advocacy_docs/community/contributing/repo.mdx b/advocacy_docs/community/contributing/repo.mdx index 879e228bd52..a5375442328 100644 --- a/advocacy_docs/community/contributing/repo.mdx +++ b/advocacy_docs/community/contributing/repo.mdx @@ -88,4 +88,4 @@ You'll make edits and additions via your IDE (VS Code). We recommend using [Gith ## Further reading -- [Format & Style](/community/contribute/style) +- [Format & Style](/community/contribute/styleguide) diff --git a/advocacy_docs/community/contributing/styleguide.mdx b/advocacy_docs/community/contributing/styleguide.mdx new file mode 100644 index 00000000000..58bcc508ed9 --- /dev/null +++ b/advocacy_docs/community/contributing/styleguide.mdx @@ -0,0 +1,523 @@ +--- +title: Documentation Style Guide +navTitle: Documentation Style Guide +iconName: Docs +description: Our style guide to help you get your writing right +indexdepth: 3 +rootisheading: true +deepToC: true +--- + + +## Introduction + +EDB docs follow the 5 Cs of technical writing: + +* Clear + +* Correct + +* Concise + +* Complete + +* Consistent + + +Follow these guidelines to ensure consistency. + +Included in this guide: + +* 1 [Language and tone](#language-and-tone) + * 1.1 [Tense and voice](#tense-and-voice) + * 1.2 [Person](#person) + * 1.3 [Sentence length](#sentence-length) + * 1.4 [Contractions](#contractions) + * 1.5 [Latin abbreviations](#latin-abbreviations) + * 1.6 [Em-dashes and en-dashes](#em-dashes-and-en-dashes) + * 1.7 [Numbers](#numbers) +* 2 [Capitalization and punctuation](#capitalization-and-punctuation) +* 3 [Topic structure](#topic-structure) +* 4 [Verbiage](#verbiage) + * 4.1 [Future and conditional tenses](#future-and-conditional-tenses) + * 4.2 [Empty phrases](#empty-phrases) + * 4.3 [Weak sentence starters](#weak-sentence-starters) + * 4.4 [“This” without a noun](#this-without-a-noun) + * 4.5 [Misplaced modifiers](#misplaced-modifiers) + * 4.6 [Hyphen use](#hyphen-use) + * 4.6.1 [With a prefix](#with-a-prefix) + * 4.6.2 [With compound adjectives](#with-compound-adjectives) + * 4.7 [Directing users up and down through a topic](#directing-users-up-and-down-through-a-topic) + * 4.8 [Select versus click](#select-versus-click) +* 5 [Common errors/words to avoid](#common-errors/words-to-avoid) + * 5.1 [Login and log in](#login-and-log-in) + * 5.2 [Setup and set up](#setup-and-set-up) + * 5.3 [Words to avoid](#words-to-avoid) +* 6 [Headings](#headings) +* 7 [Font treatments](#font-treatments) + * 7.1 [Bold (\*\*text\*\*)](#bold-text)) + * 7.2 [Courier aka code or monospace ('text')](#courier-aka-code-or-monospace-text) + * 7.3 [Italics (*text*)](#italics-text) + * 7.4 [Underline](#underline) +* 8 [Links](#links) +* 9 [Admonitions: notes, tips, and warnings](#admonitions:-notes,-tips,-and-warnings) + * 9.1 [Notes](#notes) + * 9.2 [Tips](#tips) + * 9.3 [Warnings](#warnings) + * 9.4 [Code](#inlinextensionCode) + * 9.4.1 [Inline code](#inline-code) + * 9.4.2 [Code blocks](#code-blocks) +* 10 [Tables](#tables) + * 10.1 [Markdown](#markdown) +* 11 [Lists](#lists) +* 12 [Images](#images) + +## Language and tone + +EDB docs are helpful, humble, positive, and friendly. To achieve this, write topics that are factual and free of hyperbole and wordiness. + +Where possible, use active voice instead of passive. + +### Tense and voice + +For reference and general task-based docs, use the second-person [imperative present tense](https://en.wikipedia.org/wiki/Imperative_mood), also known as "imperative mood." These docs should be straightforward and conventional. + +**Example:** Use the following command to create a user: + +`CREATE USER john IDENTIFIED BY abc;`  + +For tutorials, the docs can be more casual and conversational but must also be straightforward and clear. + +**Example:** In this lab, start with a fresh cluster. Make sure to stop and clean up the cluster from the previous labs. + +### Person + +Use second person (you) when referring to the user. Don’t use “the user,” which is third person, unless you are talking about the customer’s user. + +Use first person plural (we) to refer to EDB. For example, use: + +We recommend that you restart your server. + +Instead of + +EDB recommends that you restart your server. + +However, don’t use first person plural when talking about how the software works or in an example. For example: + +Instead of: + +Next, we process the instruction. + +Use: + +Next, Barman processes the instruction. + +Instead of: + +Next, we enter the following the information: + +Use: + +Enter the following information: + +### Sentence length + +Use simple and direct language and keep your sentences short. Avoid combining sentences, which makes the content complicated. Maximum sentence length is 26 words when possible. + +### Contractions + +In keeping with the casual and friendly tone, use contractions. However, use common contractions (isn’t, can’t, don’t). Don't use contractions that are unclear or difficult to pronounce (there’ll). + +### Latin abbreviations + +Don’t use the Latin abbreviations i.e. and e.g. Use “that is” and “for example” instead. + +### Em-dashes and en-dashes + +Avoid using em-dashes to set off phrases within a sentence, which creates a complicated sentence structure and can be difficult to translate. You can use em-dashes for definition lists such as: + +* Autonomous — Use to create autonomous calls to the server. + + +Use spaces around em-dashes in a definition list. Otherwise, don't put spaces around em-dashes. + +To create an em-dash, use the character entity —. + +Use en-dashes to mean “through,” for example, items 1–10. Don’t use en-dashes otherwise. (There's only one other use of en-dashes that doesn’t typically come up in technical writing.). To create an en-dash, use the character entity –. + +### Numbers + +Spell out numbers zero through nine. Use digits for numbers 10 and greater. Spell out any number that starts a sentence. For this reason, avoid starting a sentence with a long or complex number. + +Capitalization and punctuation +------------------------------ + +Capitalization rules: + +* Use sentence-case for headings (including column headings in tables). + +* Capitalize the first letter in each list item except for function and command names that are naturally lower case + +* Capitalize link labels to match the case of the topic you're linking to. + +* Capitalize proper nouns and match the case of UI features: + + **Examples:** EDB, the Overview dashboard, the SQL Queries graph + +* Don’t capitalize the words that make up an initialization unless they're part of proper noun. For example, single sign-on is not a proper noun even though it is usually written as the initialism SSO. + + +Punctuation rules: + +* Avoid semicolons. Instead, use two sentences. + +* Don’t join related sentences using a comma. This syntax is incorrect. + +* Don't end headings with a period or colon + +* Use periods at the end of list items that are a sentence or that complete a sentence. If one item in a list uses a period, use a period for all the items in that list. + +* Use the [Oxford (a.k.a. serial) comma](https://en.wikipedia.org/wiki/Serial_comma). + + +Topic structure +--------------- + +* Procedure headings use gerunds, for example, _Modifying your cluster_. + +* Use a stem sentence to introduce a procedure only if multiple paragraphs of text fall between the head and the start of the procedure. The stem sentence helps to reorient the user when the heading might have scrolled of the screen. A stem sentence starts with “To” and ends with a colon: + To modify your cluster: + +* In general, include text between a heading and any subheadings. However, if such text is superfluous, a subhead can directly follow the head. + + +See also [Headings](https://enterprisedb.atlassian.net/wiki/spaces/DCBC/pages/2387870239/Documentation+Style+Guide#Headings). + +## Verbiage + +Use language that's precise and informative. + +### Future and conditional tenses + +Avoid future tense (will) and conditional tenses (would, could, should). These tenses lack precision and can create passive voice. You can use future tense when an action occurs in the future, for example, “This feature will be removed in a future release.” + +### Empty phrases + +Phrases like, “This section tells you about how to \[do something\]” are empty and don’t impart any real information. The title of the chapter or section tells you what the section is about. These phrases describe the documentation (documenting the documentation) rather than the product or user actions. + +Replace these empty phrases with wording that focuses on the product or process. So instead of: + +This chapter is divided into five sections. Each section tells you about part of the process. + +Write: + +To complete the process, perform these five steps: + +You can then link to each of the sections. + +### Weak sentence starters + +“There is” and “there are” are [weak sentence starters](http://www2.ensc.sfu.ca/~whitmore/courses/style/templates/sentence.html). Avoid starting sentences this way. + +### “This” without a noun + +Avoid using “this” without a noun following. Doing so can lead to ambiguity. For example, instead of: + +This happens when… + +Write: + +This error happens when… + +### Misplaced modifiers + +Make sure the word “only” precedes the word or expression you mean to modify. For example, instead of: + +This condition only happens after you select **Okay**. + +Write: + +This condition happens only after you select **Okay**. + +### Hyphen use + +#### With a prefix + +Don't use hyphens with prefixes such as re, non, multi, and pre unless needed for readability or to eliminate ambiguity. Often, when two vowels end up up together, a hyphen is needed, for example, multi-instance. However, preexisting is a legitimate word; don’t hyphenate it. Re-create (create again) requires a hyphen to avoid confusion with recreate (play). You can check many words using a spell checker. For example, nonexistent is not flagged by the spell checker. + +If you're unsure whether to include a hyphen, check with your editor or google the word without the hyphen + +#### With compound adjectives + +A compound adjective is formed when two words together describe a noun, for example, _red-bellied warbler_. Don’t use a hyphen when and adverb and a verb together describe a noun. The adverb describes the verb and doesn’t need a hyphen to create the relationship between the words. An example is _finely tuned settings_. + +### Directing users up and down through a topic + +Don’t use words like “below” and “above” to refer to previous and following sections. Link to the section instead. + +It also isn't necessary to use the words “the following” to refer to list items. These words are empty. So, for example, instead of: + +The palette includes the following colors: + +Write: + +The color palette includes: + +### Select versus click + +House style is to use “select” instead of “click” to allow for mobile-device use. + +Common errors/words to avoid +---------------------------- + +Avoid these common errors and wording issues. + +### Login and log in + +The verb form is “log in”: + +To log in to the system… + +The adjective form is “login”: + +At the login screen, enter your username. + +### Setup and set up + +The verb form is “set up”: + +To set up your environment… + +The noun form is “setup”: + +Check your setup for errors. + +### Words to avoid + +Don't use: + +* Please + +* Note that + +* In order to (just use “to”) + + +## Headings + +Use headings to create a hierarchy for readers to navigate to more easily find information. + +In Markdown, headings are denoted by number signs (`#`) followed by one space. Enter a line break between a heading and its content. EDB docs use Heading 2 (`##`), Heading 3 (`###`) and Heading 4 (`####`). Use Heading 4 sparingly. + +Heading 1 is reserved for page titles. You can denote anything below Heading 4 using bold text or other layout options. (Consider redesigning the material.) + +Examples: + +* `## This is heading 2` + +* `### This is heading 3` + +* `## Step 2. This is a step in a tutorial` + + +## Font treatments + +Don’t use any font treatments for: + +* Roles + +* User names (e.g. edb_admin) + +* Permissions + +* Window or dialog box names + + +### Bold (\*\*text\*\*) + +Use for UI elements. For menu items, include a greater-than sign: Select **File > Save**. + +### Courier aka code or monospace (`'text'`) + +Use for text entered in text boxes, parameters, commands, text in configuration files, and file paths. Don’t use for utility names. + +If you need to enter a `value in a field`, type the `ls` or `dd` command, add a setting to a `configuration=file` or just refer to `/etc/passwd`, then this is the font treatment to use. + +See [Code](#code) for more information. + +### Italics (*_text_*) + +Use for book titles and first instance of terms. Do not use Italics for keywords. + +### Underline + +Do not use underlined text in EDB docs. + +## Links + +Whenever an EDB feature is referenced, provide a link to the relevant documentation. For example, “BDR (Bi-Directional Replication) dashboards and probes to monitor status and activities for Admin, Nodes, and Groups. See [Monitoring BDR Nodes](http://localhost:8000/pem/latest/pem_ent_feat/17_monitoring_BDR_nodes/).” + +Avoid using the URL as the label. For example, + +**Best practice:** For information about the platforms and versions supported by PEM, see [Product Compatibility](https://www.enterprisedb.com/services-support/edb-supported-products-and-platforms) on the EnterpriseDB website**.** + +**Avoid:** For information about the platforms and versions supported by PEM, visit the EnterpriseDB website at: [https://www.enterprisedb.com/services-support/edb-supported-products-and-platforms](https://www.enterprisedb.com/services-support/edb-supported-products-and-platforms). + +You can also provide links to external resources, but only if the resource is vetted and no EDB documentation covers the topic. For example: “Information about managing authentication is also available in the [Postgres core documentation](https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html).” + +If you're referring to a guide on Docs 2.0, the label is the name of the guide and in italics. For example, “For information about modifying the `pg_hba.conf` file, see the [_PEM Administrator's Guide_](https://www.enterprisedb.com/docs/pem/latest/pem_admin/).” + +Link capitalization can be either title- or sentence-case: + +* **Use title-case** and _italics_ when referring to the linked doc by name. For example. “For information about modifying the `pg_hba.conf` file, see the [_PEM Administrator's Guide_](https://www.enterprisedb.com/docs/pem/latest/pem_admin/).”). + +* **Use sentence-case** when linking in the middle of a sentence. For example, “\[…\] follow the identifier rules when creating \[…\]“). + + +Addresses are relative. In these examples of links to topics, “folder” means the folder in the repo such as the product folder or the guide folder. For the destination topic, use the name of the file without the .mdx extension. If the destination includes a topic\_identifier (sub-section of a file), include the topic\_identifier prefixed with a # sign, such as in “/09\_controlling\_logging/#enabling_syslog.” + +| | | | | | +| --- | --- | --- | --- | --- | +| **Link type** | **Syntax** | **Example** | **Source path** | **Destination path** | + +| | | | | | +| --- | --- | --- | --- | --- | +| **Link type** | **Syntax** | **Example** | **Source path** | **Destination path** | +| Another topic in the same folder | `[here](file_name)` | `[Using the EFM Utility](07_using_efm_utility/#using_efm_utility)` | /efm/4.2/efm\_user/07\_using_efm.mdx | /efm/4.2/efm\_user/07\_using\_efm\_utility.mdx | +| Another topic in a different folder at the same level | `[here](../dest_folder_name/file_name)` | \[The ERD Tool\](../pem\_ent\_feat/04\_pem\_erd_tool/) | /pem/8/pem\_rel\_notes/08\_810\_rel_notes.mdx | /pem/8/pem\_ent\_feat04\_pem\_erd_tool/ | +| Another topic in a different folder at a different level | `[here](../../folder_name/file_name`) | \[Enabling syslog Log File Entries\](../../09\_controlling\_logging/#enabling_syslog) | /efm/4.2/efm\_user/04\_configuring\_efm/01\_cluster_properties/index.mdx | /efm/4.2/efm\_user/09\_controlling\_logging.mdx/enabling\_syslog | + +* To link to a specific heading on another page, use the name of the file plus the heading. + + **Example:** `[xyz](file_name#heading-on-page)` + +* To link to a specific heading on the current page, use just the heading. + + **Example:** `[xyz](#heading-on-page)` + +* To link to a specific location on a page that isn't a heading (for example, a specific command-line flag in a table), add a manual anchor and use the `id` parameter: + + **Example:** + + ``# Anchor: `--max-offset` # Link: [--max-offset](#flags-max-offset)`` + + +## Admonitions: notes, tips, and warnings + +Our docs currently use notes, tips, and warnings. + +See [https://github.com/EnterpriseDB/docs/blob/develop/README.md](https://github.com/EnterpriseDB/docs/blob/develop/README.md) for more information on admonitions. + +For multiple, consecutive admonitions, use separate admonitions. If there are more than two consecutive admonitions, consider adding a subsection called **Additional notes** or **Additional information**. Admonitions can contain bullets and code, but consider instead adding a subsection (or whether an admonition is the appropriate mechanism) to keep the formatting simple. + +### Notes + +Use notes to call attention to a piece of clarifying information. This information isn't crucial to accomplishing the task in the document. + +For example, you might use a note to let users know that the `DELETE` command deletes only rows and that to delete columns you must use `ALTER TABLE`. This information helps to clarify the command's purpose and point users to the right place. + +### Tips + +Use for indicating a new version added in a particular release when working in the major version of the documentation for products that are adhering to semantic versioning. See the PEM documentation for examples. Also can use for information that might improve productivity. + +### Warnings + +Use warning to express that a piece of information is critical to preventing unexpected things from happening. + +For example, you might include a warning that using `CASCADE` in `DROP INDEX` drops dependent objects without warning. This is critical to prevent users from unexpectedly losing constraints or additional indexes. + +## Code + +Code can be shown inline or as a code block. + +### Inline code + +Inline `code` has `back-ticks (``) around` it and is used when referring to code, commands, or other technical syntax within a sentence. + +Example: The `CREATE TABLE` statement creates a new table in a database. + +### Code blocks + +Code blocks provide executable code samples, marked with an opening and closing set of three backticks (` ``` `). Code blocks can support syntax highlighting if you add the language name immediately after the first line of backticks. Use one returned line before and after a code block for better Markdown readability. For example: + +`This is a sample line of text. ``` {% include copy-clipboard.html %} ~~~shell $ go get -u github.com/lib/pq ~~~ ``` This is more sample text.` + +Use syntax highlighting for configuration file , shell, and SQL commands, where appropriate, as follows. + +**Shell code samples** + +Start shell code samples with ` ```shell` followed by a line break. Use the terminal marker `$` as the first character of the next line. For multi-line shell commands, use a backslash (`\`) at the end of each line to indicate a line break. + +**SQL code samples** + +SQL code samples are broken into two sections: commands and responses. + +* **Commands** (e.g., `SELECT`, `CREATE TABLE`) begin with ` ```sql` followed by a line break. The first character of the next line should be the terminal marker `>`. Capitalize commands properly. Use only one command per code sample. + +* **Responses** (e.g., retrieved tables) add (_ _ 0UTPUT _ _) on a line between the command and the output, you'll get highlights for the code but not the output. For example, + + ` + ```sql SELECT slot_name, slot_type, database, active FROM pg_replication_slots ORDER BY 1; __OUTPUT__ slot_name | slot_type | database | active -------------+-----------+-----------+-------- xdb_47877_5 | logical | MMRnode_a | t xdb_47878_5 | logical | MMRnode_b | t xdb_47879_5 | logical | MMRnode_c | t (3 rows) ``` ` + +``` +sql SELECT slot_name, slot_type, database, active FROM pg_replication_slots ORDER BY 1; __OUTPUT__ slot_name | slot_type | database | active -------------+-----------+-----------+-------- xdb_47877_5 | logical | MMRnode_a | t xdb_47878_5 | logical | MMRnode_b | t xdb_47879_5 | logical | MMRnode_c | t (3 rows) +``` + + +**Configuration file samples** + +For files that have key-value pairs use ` ```ini`. For example: + +` ```ini promotable=false auto.reconfigure=false ``` ` + +Tables +------ + +Use tables to display structured information in an easy-to-read format. There are two types of tables we use: Markdown and HTML. + +## Markdown + +If table formatting can be kept simple (e.g., basic text formatting and using `
` tags for paragraph breaks), create a table using Markdown. This is the preferred table format. + +To create a table, use pipes (`|`) between columns and at least 3 dashes (`-`) separating the header cells from the body cells. A return denotes the start of the next row. The text within each column does not need to align in order to be rendered correctly, and you can inline Markdown or HTML. + +We don’t use outer pipes. + +Example: + +``` +Term | Description | Example ----------|-----------------------------|---------------- `term_1` | This is a description. | `3.14` `term_2` | This is also a description. | `"lola mcdog"` +``` + +## Lists + +EDB docs uses two types of lists: + +* **Numbered** (ordered) — Use to list information that should appear in order, like tutorial steps. + + **Bulleted** (unordered) — Use to list related information in an easy-to-read way. + + Introduce lists with a sentence and a colon. Use periods at the end of list items if it is a sentence or completes a sentence. + + +For each item of a **numbered list**, use `1.` followed by a period and a space, for example,`1. This is a numbered list`. Markdown renders the steps in the correct order. + +For each item of a **bulleted list**, use one dash followed by one space to denote a list item, e.g., `- This is a bulleted list`. + +## Images + +Use images to clarify a topic, but use them only as needed. Images are either: + +* **Screenshots** — Provide a UI visual. Don’t use to show dialog boxes and parts of the UI a user can see for themselves, as these are hard to maintain and don’t provide useful information. If a screenshot needs an annotation, use a red box. + +* **Diagrams** — Provide a visual of a complicated theory. Diagrams must be simple and easy to read. + + +**Syntax:** + +! \[Alternate\_text\](<path\_to\_image\_file>/<image_filename.png>) + +**Example:** + +`![PEM Architecture](../images/pem_architecture.png)` + diff --git a/advocacy_docs/community/index.mdx b/advocacy_docs/community/index.mdx new file mode 100644 index 00000000000..6d5c00feeab --- /dev/null +++ b/advocacy_docs/community/index.mdx @@ -0,0 +1,12 @@ +--- +title: Community +navTitle: Community +description: The EDB Docs Community +iconName: IdeaSharing +--- + +All guides, notes and documentation for anyone working in the community of EDB documenters. + +* [Contributing Documentation](contributing) + + From 8cfd9463949d76e83ad90c71db002c82ef3375aa Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 16 Aug 2023 10:10:33 +0100 Subject: [PATCH 050/223] Tidied community/contrib page Signed-off-by: Dj Walker-Morgan --- advocacy_docs/community/contributing/index.mdx | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/advocacy_docs/community/contributing/index.mdx b/advocacy_docs/community/contributing/index.mdx index e754ebc07f2..1144730282a 100644 --- a/advocacy_docs/community/contributing/index.mdx +++ b/advocacy_docs/community/contributing/index.mdx @@ -7,7 +7,7 @@ iconName: IdeaSharing All feedback is welcome: -Is it a simple edit for a typo? Use the **Suggest Edits** button and you can make a change to the docs which we'll review it. +Is it a simple edit for a typo? Use the **Suggest Edits** button and you can make a change to the docs which we'll review before including in the next docs update. If, on the other hand you: @@ -19,10 +19,9 @@ Then Github Issues is the fastest way to get that feedback in front of us. [Open an issue on Github →](https://github.com/EnterpriseDB/docs/issues) ---- - ### Have code or content to contribute? -The only things we love more than feedback are pull requests. Check out [the README on Github](https://github.com/EnterpriseDB/docs) to get started. +The only things we love more than feedback are pull requests. +Check out [the README on Github](https://github.com/EnterpriseDB/docs) to get started. From 130255fa6699d566e57c934ad3eb25b6421084bd Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 23 Aug 2023 09:10:50 +0100 Subject: [PATCH 051/223] Added date formatting rules and release note dates Signed-off-by: Dj Walker-Morgan --- .../community/contributing/styleguide.mdx | 7 ++++ docs/agreements/release-notes-guidelines.md | 36 +++++++++++++++---- 2 files changed, 36 insertions(+), 7 deletions(-) diff --git a/advocacy_docs/community/contributing/styleguide.mdx b/advocacy_docs/community/contributing/styleguide.mdx index 58bcc508ed9..6ea7ba2c3d9 100644 --- a/advocacy_docs/community/contributing/styleguide.mdx +++ b/advocacy_docs/community/contributing/styleguide.mdx @@ -71,6 +71,7 @@ Included in this guide: * 10.1 [Markdown](#markdown) * 11 [Lists](#lists) * 12 [Images](#images) +* 13 [Dates](#dates) ## Language and tone @@ -521,3 +522,9 @@ Use images to clarify a topic, but use them only as needed. Images are either: `![PEM Architecture](../images/pem_architecture.png)` +## Dates + +When specifying dates for human readability, use the DD mmm YYYY format with a short month name in English. Where the date is being used in a column in a table, use a leading 0 on the day of month, e.g. 01 Jan 2024, for easier alignment. + +When specifying dates as solely numbers, use [ISO8601](https://www.iso.org/iso-8601-date-and-time-format.html) format; YYYY/MM/DD. This is the internationally accepted, disambiguous format and should be used where you may expect the date to be read by automated systems. + diff --git a/docs/agreements/release-notes-guidelines.md b/docs/agreements/release-notes-guidelines.md index 73bedfef8f1..53d19869b11 100644 --- a/docs/agreements/release-notes-guidelines.md +++ b/docs/agreements/release-notes-guidelines.md @@ -1,6 +1,28 @@ -# Guidelines for wording release notes +# Guidelines for release notes -## General guidelines +## Structural guidelines + +Release notes start with the name of the product, the version number being released and the words "Release Notes". +This should be the setting for the frontmatter title field. The frontmatter will also need a short navigation title +(navTitle). This should just be the version number, preceded by the word "Version". + +This is followed, in the body of the content, by a date of release in the `Released: DD mmm YYYY` format: + +``` +--- +title: EDB Postgres Advanced Server 64.0 Release Notes +navTitle: Version 64.0 +--- + +Released: 1 Jan 2024 + +``` + +If the release notes are substantially updated after release, add an `Updated: DD mmm YYYY` line, or update any existing `Updated:` line. + +## Guidelines for wording release notes + +### General guidelines - For features and enhancements, use second person (you) instead of third person (the user). - For bug fixes, avoid referring to the user. Instead, describe the software behavior. If the description is clearer by referring to the user, use third person. @@ -10,11 +32,11 @@ - Use contractions. - Use serial (aka Oxford) commas. -## Phrasing guidelines for enhancements +### Phrasing guidelines for enhancements You can use either of the forms described in the following sections for enhancements. Add as much detail as needed to convey the relevance of the enhancement. If you need to describe how the product worked before, use “previously,” not “currently.” -### Past tense description of the development work +#### Past tense description of the development work Start with a past-tense word that describes what you did. Then provide any relevant detail. @@ -24,7 +46,7 @@ Examples: - Added the ability to copy probes and alerts to all servers in a group without having to select them individually. - Enabled multi-insert support for the dynamic partition for EDB*Loader and COPY command. -### “Now” phrase +#### “Now” phrase Describe what the product does now as a result of the enhancement, generally in the form: The *product/feature* now *does the new behavior*. @@ -32,7 +54,7 @@ Examples: - EDB Postgres Advanced Server now provides INDEX and NO_INDEX hints for the partitioned table. The optimizer hints apply to the inherited index in the partitioned table. The execution plan internally expands to include the corresponding inherited child indexes and applies them in later processing. - The INTO clause now accepts multiple composite row type targets in SPL. This enhancement allows you to assign a SELECT list having a mix of scalar and composite type values that are fetched from a table to corresponding scalar or composite variables (including collection variables) in the SPL code. -### Enhancement don’ts +#### Enhancement don’ts Don’t start the enhancement with a gerund, which suggests the work is still in progress: - **Correct**: Added the XYZ function. @@ -44,7 +66,7 @@ Don’t use a title or short description: - **Correct**: You can now configure the durability options, such as Group Commit, CAMO, Eager Replication, and Lag Control, through Commit Scope. - **Incorrect**: Unified replication durability configuration - The durability options such as Group Commit, CAMO, Eager Replication, or Lag Control are now all configured through Commit Scope configuration. -## Bug fix writing guidelines +### Bug fix writing guidelines Start bug fix descriptions with: - Fixed an issue whereby… From ee38153619c149d44953d84ee331cdd9d9c8a427 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Wed, 23 Aug 2023 10:29:10 +0100 Subject: [PATCH 052/223] Update repo.mdx Fix link --- advocacy_docs/community/contributing/repo.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/community/contributing/repo.mdx b/advocacy_docs/community/contributing/repo.mdx index a5375442328..36c5d4ad8be 100644 --- a/advocacy_docs/community/contributing/repo.mdx +++ b/advocacy_docs/community/contributing/repo.mdx @@ -88,4 +88,4 @@ You'll make edits and additions via your IDE (VS Code). We recommend using [Gith ## Further reading -- [Format & Style](/community/contribute/styleguide) +- [Format & Style](/community/contributing/styleguide) From 83bb336856ce6115641419d9df2cd6323feb863f Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Wed, 23 Aug 2023 10:32:59 +0100 Subject: [PATCH 053/223] Update release-notes-guidelines.md Release Notes -> release notes --- docs/agreements/release-notes-guidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/agreements/release-notes-guidelines.md b/docs/agreements/release-notes-guidelines.md index 53d19869b11..9a8d80482f4 100644 --- a/docs/agreements/release-notes-guidelines.md +++ b/docs/agreements/release-notes-guidelines.md @@ -2,7 +2,7 @@ ## Structural guidelines -Release notes start with the name of the product, the version number being released and the words "Release Notes". +Release notes start with the name of the product, the version number being released and the words "release notes". This should be the setting for the frontmatter title field. The frontmatter will also need a short navigation title (navTitle). This should just be the version number, preceded by the word "Version". @@ -10,7 +10,7 @@ This is followed, in the body of the content, by a date of release in the `Relea ``` --- -title: EDB Postgres Advanced Server 64.0 Release Notes +title: EDB Postgres Advanced Server 64.0 release notes navTitle: Version 64.0 --- From 56795b504e2d2c98a33a3420b37ab01dd14e4a78 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 24 Aug 2023 11:24:46 -0400 Subject: [PATCH 054/223] fixed typo --- .../PreciselyConnectCDC/04-Configuratingpreciselyconnectcdc.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/04-Configuratingpreciselyconnectcdc.mdx b/advocacy_docs/partner_docs/PreciselyConnectCDC/04-Configuratingpreciselyconnectcdc.mdx index 5d900d58895..719aaf20945 100644 --- a/advocacy_docs/partner_docs/PreciselyConnectCDC/04-Configuratingpreciselyconnectcdc.mdx +++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/04-Configuratingpreciselyconnectcdc.mdx @@ -1,5 +1,5 @@ --- -title: 'ConfiguringC' +title: 'Configuring' description: 'Walkthrough of configuring the integration' --- From 030bb633f6b60cdd6fb1788aec5ac1deacc61ff1 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 24 Aug 2023 12:40:28 -0400 Subject: [PATCH 055/223] Made the short descriptions consistent --- ...guringCohesityDataProtectforPostgreSQL.mdx | 2 +- ...-UsingCohesityDataProtectforPostgreSQL.mdx | 2 +- .../06-CertificationEnvironment.mdx | 2 +- .../07-SupportandLogging.mdx | 32 +++++++++++-------- .../DBeaverPRO/07-SupportandLogging.mdx | 26 +++++++-------- ...ngEsriArcGISProandEsriArcGISEnterprise.mdx | 2 +- ...ngEsriArcGISProandEsriArcGISEnterprise.mdx | 2 +- .../06-CertificationEnvironment.mdx | 2 +- .../04-ConfiguringTransitSecretsEngine.mdx | 2 +- .../04-ConfiguringLiquibasePro.mdx | 2 +- .../LiquibasePro/05-UsingLiquibasePro.mdx | 2 +- .../06-CertificationEnvironment.mdx | 2 +- .../04-ConfiguringQuestToadEdge.mdx | 2 +- .../QuestToadEdge/05-UsingQuestToadEdge.mdx | 2 +- .../06-CertificationEnvironment.mdx | 2 +- ...ringRepostorDataProtectorforPostgreSQL.mdx | 2 +- ...singRepostorDataProtectorforPostgreSQL.mdx | 2 +- .../06-CertificationEnvironment.mdx | 2 +- .../04-ConfiguringSIBVisionsVisionX.mdx | 2 +- .../05-UsingSIBVisionsVisionX.mdx | 2 +- .../06-CertificationEnvironment.mdx | 2 +- ...ThalesCipherTrustTransparentEncryption.mdx | 2 +- ...ThalesCipherTrustTransparentEncryption.mdx | 2 +- .../06-CertificationEnvironment.mdx | 2 +- ...nfiguringVeritasNetBackupforPostgreSQL.mdx | 2 +- .../05-UsingVeritasNetBackupForPostgreSQL.mdx | 2 +- .../06-CertificationEnvironment.mdx | 2 +- 27 files changed, 56 insertions(+), 52 deletions(-) diff --git a/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/04-ConfiguringCohesityDataProtectforPostgreSQL.mdx b/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/04-ConfiguringCohesityDataProtectforPostgreSQL.mdx index f463b877357..a649e353e4a 100644 --- a/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/04-ConfiguringCohesityDataProtectforPostgreSQL.mdx +++ b/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/04-ConfiguringCohesityDataProtectforPostgreSQL.mdx @@ -1,6 +1,6 @@ --- title: 'Configuring' -description: 'Walkthrough of configuring Cohesity DataProtect for PostgreSQL' +description: 'Walkthrough of configuring the integration' --- Implementing Cohesity DataProtect for PostgreSQL with EDB Postgres Advanced Server requires the following components: diff --git a/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/05-UsingCohesityDataProtectforPostgreSQL.mdx b/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/05-UsingCohesityDataProtectforPostgreSQL.mdx index 0ee222986b2..ae4d3ca210c 100644 --- a/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/05-UsingCohesityDataProtectforPostgreSQL.mdx +++ b/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/05-UsingCohesityDataProtectforPostgreSQL.mdx @@ -1,6 +1,6 @@ --- title: 'Using' -description: 'Walkthroughs of multiple Cohesity DataProtect for PostgreSQL usage scenarios' +description: 'Walkthrough of example usage scenarios' --- These use cases show how backups are taken and restored from EDB Postgres Advanced Server using Cohesity DataProtect for PostgreSQL. diff --git a/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/06-CertificationEnvironment.mdx index 59344126b31..6a78be85955 100644 --- a/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/CohesityDataProtectforPostgreSQL/06-CertificationEnvironment.mdx @@ -1,6 +1,6 @@ --- title: 'Certification environment' -description: 'Overview of the certification environment used in the certification of Cohesity DataProtect for PostgreSQL' +description: 'Overview of the certification environment' --- |   |   | diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx index 303d6c2bb43..bdc628d1ec6 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx @@ -1,23 +1,25 @@ --- -title: 'Support and Logging Details' +title: 'Support and logging details' description: 'Details of the support process and logging information' --- ## Support -Technical support for the use of these products is provided by both EDB and Commvault. A proper support contract is required to be in place at both EDB and Commvault. A support ticket can be opened on either side to start the process. If it is determined through the support ticket that resources from the other vendor is required, the customer should open a support ticket with that vendor through normal support channels. This will allow both companies to work together to help the customer as needed. +Technical support for the use of these products is provided by both EDB and Commvault. A support contract must be in place at both EDB and Commvault. You can open a support ticket with either company to start the process. If it's determined through the support ticket that resources from the other vendor are required, open a support ticket with that vendor through normal support channels. This approach allows both companies to work together to help you as needed. ## Logging -**EDB Postgres Advanced Server Logs:** +The following logs are available. -Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance and from here you can navigate to `log`, `current_logfiles` or you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs. +### EDB Postgres Advanced Server logs -**EDB Postgres Extended Server Logs** +Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance. From there, you can navigate to `log` or `current_logfiles`. Or, you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs. -Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance and from here you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options. An example of the full path to view EDB Postgres Extended logs: `/var/lib/edb-pge/15/data/log`. +### EDB Postgres Extended Server logs -**PostgreSQL Server Logs** +Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance. From there you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options. An example of the full path to view EDB Postgres Extended logs is `/var/lib/edb-pge/15/data/log`. + +### PostgreSQL Server logs The default log directories for PostgreSQL logs vary depending on the operating system: @@ -27,16 +29,18 @@ The default log directories for PostgreSQL logs vary depending on the operating - Windows: `C:\Program Files\PostgreSQL\9.3\data\pg_log` -** Commvault Logs** +### Commvault logs + +You can find Commvault logs using either of these methods: -Commvault logs can be found a few ways. A first way is within the Content Store directory/folder in the Commvault folder on your system. For example if on a Windows system the Log File path would be `C:\Program Files\Commvault\ContentStore\LogFiles` where you can then see all of the differnt types of logs Commvault collects. +- Look in the Content Store directory/folder in the Commvault folder on your system. For example, on a Windows system, the log file path is `C:\Program Files\Commvault\ContentStore\LogFiles`. There you can see all of the different types of logs Commvault collects. -You can also gather some job specific logs within the Commvault interface. +- Gather some job-specific logs in the Commvault interface: -1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to `Jobs > Job History`. + 1. Open Commvault Backup & Recovery's Command Center. From the navigation pane, go to **Jobs > Job History**. -2. Find the specific job you would like to view logs for and click on the `...` beside that job. + 2. Find the specific job you want to view logs for, and select `...` next to that job. -3. Select `View Logs`. + 3. Select **View Logs**. - ![View Job Logs](Images/CommvaultViewLogsForJob.png) + ![View Job Logs](Images/CommvaultViewLogsForJob.png) diff --git a/advocacy_docs/partner_docs/DBeaverPRO/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/DBeaverPRO/07-SupportandLogging.mdx index 5f476add649..f78487e87ea 100644 --- a/advocacy_docs/partner_docs/DBeaverPRO/07-SupportandLogging.mdx +++ b/advocacy_docs/partner_docs/DBeaverPRO/07-SupportandLogging.mdx @@ -1,23 +1,25 @@ --- -title: 'Support and Logging Details' +title: 'Support and logging details' description: 'Details of the support process and logging information' --- ## Support -Technical support for the use of these products is provided by both EDB and DBeaver. A proper support contract is required to be in place at both EDB and DBeaver. A support ticket can be opened on either side to start the process. If it is determined through the support ticket that resources from the other vendor is required, the customer should open a support ticket with that vendor through normal support channels. This will allow both companies to work together to help the customer as needed. +Technical support for the use of these products is provided by both EDB and DBeaver. A support contract must be in place at both EDB and DBeaver. You can open a support ticket with either company to start the process. If it's determined through the support ticket that resources from the other vendor are required, open a support ticket with that vendor through normal support channels. This approach allows both companies to work together to help you as needed. ## Logging -**EDB Postgres Advanced Server Logs:** +The following logs are available. -Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance and from here you can navigate to `log`, `current_logfiles` or you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs. +### EDB Postgres Advanced Server logs -**EDB Postgres Extended Server Logs** +Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance. From there, you can navigate to `log` or `current_logfiles`. Or, you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs. -Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance and from here you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options. An example of the full path to view EDB Postgres Extended logs: `/var/lib/edb-pge/15/data/log`. +### EDB Postgres Extended Server logs -**PostgreSQL Server Logs** +Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance. From there you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options. An example of the full path to view EDB Postgres Extended logs is `/var/lib/edb-pge/15/data/log`. + +### PostgreSQL Server logs The default log directories for PostgreSQL logs vary depending on the operating system: @@ -27,15 +29,13 @@ The default log directories for PostgreSQL logs vary depending on the operating - Windows: `C:\Program Files\PostgreSQL\9.3\data\pg_log` -** DBeaver Logs** - -If you are experiencing errors during the DBeaver runtime you can gather those within the DBeaver Pro interface. +## DBeaver logs -1. On the top menu bar navigate to `Window` and select it. +If you experience errors during the DBeaver runtime, you can gather them in the DBeaver Pro interface: -2. Scroll down to `Show View`. +1. At the top menu bar, select **Window**. -3. In the menu options that come up select `Error Log` and this will contain all the errors that occur during the DBeaver runtime. +2. Select **Show View > Error Log**. The log contains all the errors that occur during the DBeaver runtime. ![DBeaver Log Viewer](Images/DBeaverLogViewer.png) 4. You can save and attach these logs to a support ticket or bug report to DBeaver support. diff --git a/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/04-ConfiguringEsriArcGISProandEsriArcGISEnterprise.mdx b/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/04-ConfiguringEsriArcGISProandEsriArcGISEnterprise.mdx index 1562aced751..ac0448ffbc8 100644 --- a/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/04-ConfiguringEsriArcGISProandEsriArcGISEnterprise.mdx +++ b/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/04-ConfiguringEsriArcGISProandEsriArcGISEnterprise.mdx @@ -1,6 +1,6 @@ --- title: 'Configuring' -description: 'Walkthrough of configuring Esri ArcGIS Pro and Esri ArcGIS Enterprise' +description: 'Walkthrough of configuring the integration' --- Implementing Esri ArcGIS Pro and Esri ArcGIS Enterprise with EDB Postgres Advanced Server requires the following components: diff --git a/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/05-UsingEsriArcGISProandEsriArcGISEnterprise.mdx b/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/05-UsingEsriArcGISProandEsriArcGISEnterprise.mdx index 20727db6af6..1df16dbc962 100644 --- a/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/05-UsingEsriArcGISProandEsriArcGISEnterprise.mdx +++ b/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/05-UsingEsriArcGISProandEsriArcGISEnterprise.mdx @@ -1,6 +1,6 @@ --- title: 'Using' -description: 'Walkthroughs of multiple Esri ArcGIS Pro and Esri ArcGIS Enterprise usage scenarios' +description: 'Walkthrough of example usage scenarios' --- ## Create file geodatabase diff --git a/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/06-CertificationEnvironment.mdx index 4eb20c5cecc..6c7b3d68f34 100644 --- a/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/06-CertificationEnvironment.mdx @@ -1,6 +1,6 @@ --- title: 'Certification environment' -description: 'Overview of the certification environment used in the certification of Esri ArcGIS Pro and Esri ArcGIS Enterprise' +description: 'Overview of the certification environment' --- |   |   | diff --git a/advocacy_docs/partner_docs/HashicorpVaultTransitSecretsEngine/04-ConfiguringTransitSecretsEngine.mdx b/advocacy_docs/partner_docs/HashicorpVaultTransitSecretsEngine/04-ConfiguringTransitSecretsEngine.mdx index 5d6357b42ca..5475fd3cf5b 100644 --- a/advocacy_docs/partner_docs/HashicorpVaultTransitSecretsEngine/04-ConfiguringTransitSecretsEngine.mdx +++ b/advocacy_docs/partner_docs/HashicorpVaultTransitSecretsEngine/04-ConfiguringTransitSecretsEngine.mdx @@ -1,6 +1,6 @@ --- title: 'Configuring' -description: 'Walkthrough on configuring the integration' +description: 'Walkthrough of configuring the integration' --- Implementing Hashicorp Vault with EDB Postgres Advanced Server version 15.2 and later or EDB Postgres Extended Server version 15.2 and later requires the following components: diff --git a/advocacy_docs/partner_docs/LiquibasePro/04-ConfiguringLiquibasePro.mdx b/advocacy_docs/partner_docs/LiquibasePro/04-ConfiguringLiquibasePro.mdx index e7b6d8e6e62..dac57dc6cf0 100644 --- a/advocacy_docs/partner_docs/LiquibasePro/04-ConfiguringLiquibasePro.mdx +++ b/advocacy_docs/partner_docs/LiquibasePro/04-ConfiguringLiquibasePro.mdx @@ -1,6 +1,6 @@ --- title: 'Configuring' -description: 'Walkthrough of configuring Liquibase Pro' +description: 'Walkthrough of configuring the integration' --- Implementing Liquibase with EDB Postgres Advanced Server requires the following components: diff --git a/advocacy_docs/partner_docs/LiquibasePro/05-UsingLiquibasePro.mdx b/advocacy_docs/partner_docs/LiquibasePro/05-UsingLiquibasePro.mdx index 30b0d520f29..b44a91a5246 100644 --- a/advocacy_docs/partner_docs/LiquibasePro/05-UsingLiquibasePro.mdx +++ b/advocacy_docs/partner_docs/LiquibasePro/05-UsingLiquibasePro.mdx @@ -1,6 +1,6 @@ --- title: 'Using' -description: 'Walkthroughs of multiple Liquibase Pro usage scenarios' +description: 'Walkthrough of example usage scenarios' --- Liquibase is a development tool that allows you to apply changes to the EDB database using the Liquibase CLI and view them on the Liquibase Hub. diff --git a/advocacy_docs/partner_docs/LiquibasePro/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/LiquibasePro/06-CertificationEnvironment.mdx index 4192e3e5828..a8960b444a0 100644 --- a/advocacy_docs/partner_docs/LiquibasePro/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/LiquibasePro/06-CertificationEnvironment.mdx @@ -1,6 +1,6 @@ --- title: 'Certification environment' -description: 'Overview of the certification environment used in the certification of Liquibase Pro' +description: 'Overview of the certification environment' --- |   |   | diff --git a/advocacy_docs/partner_docs/QuestToadEdge/04-ConfiguringQuestToadEdge.mdx b/advocacy_docs/partner_docs/QuestToadEdge/04-ConfiguringQuestToadEdge.mdx index 1c2cd26138f..44128048aa3 100644 --- a/advocacy_docs/partner_docs/QuestToadEdge/04-ConfiguringQuestToadEdge.mdx +++ b/advocacy_docs/partner_docs/QuestToadEdge/04-ConfiguringQuestToadEdge.mdx @@ -1,6 +1,6 @@ --- title: 'Configuring' -description: 'Walkthrough of configuring Quest Toad Edge' +description: 'Walkthrough of configuring the integration' --- Implementing Quest Toad Edge with EDB Postgres Advanced Server or EDB Postgres Extended Server requires the following components: diff --git a/advocacy_docs/partner_docs/QuestToadEdge/05-UsingQuestToadEdge.mdx b/advocacy_docs/partner_docs/QuestToadEdge/05-UsingQuestToadEdge.mdx index 2f4b607cefe..b420540c62b 100644 --- a/advocacy_docs/partner_docs/QuestToadEdge/05-UsingQuestToadEdge.mdx +++ b/advocacy_docs/partner_docs/QuestToadEdge/05-UsingQuestToadEdge.mdx @@ -1,6 +1,6 @@ --- title: 'Using' -description: 'Walkthroughs of multiple Quest Toad Edge usage scenarios' +description: 'Walkthrough of example usage scenarios' --- After you connect an instance of EDB Postgres Advanced Server or EDB Postgres Extended to Quest Toad Edge, you can access the capabilities of Toad Edge. diff --git a/advocacy_docs/partner_docs/QuestToadEdge/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/QuestToadEdge/06-CertificationEnvironment.mdx index a70d85b3bf1..484542b7533 100644 --- a/advocacy_docs/partner_docs/QuestToadEdge/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/QuestToadEdge/06-CertificationEnvironment.mdx @@ -1,6 +1,6 @@ --- title: 'Certification environment' -description: 'Overview of the certification environment used in the certification of Quest Toad Edge' +description: 'Overview of the certification environment' redirects: - /partner_docs/ToadEdgeGuide/06-CertificationEnvironment/ --- diff --git a/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/04-ConfiguringRepostorDataProtectorforPostgreSQL.mdx b/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/04-ConfiguringRepostorDataProtectorforPostgreSQL.mdx index 6e386a32fc9..948bc82ef22 100644 --- a/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/04-ConfiguringRepostorDataProtectorforPostgreSQL.mdx +++ b/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/04-ConfiguringRepostorDataProtectorforPostgreSQL.mdx @@ -1,6 +1,6 @@ --- title: 'Configuring' -description: 'Walkthrough of configuring Repostor Data Protector for PostgreSQL' +description: 'Walkthrough of configuring the integration' --- ## Prerequisites diff --git a/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/05-UsingRepostorDataProtectorforPostgreSQL.mdx b/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/05-UsingRepostorDataProtectorforPostgreSQL.mdx index 45ef071fca7..0f3d8d49404 100644 --- a/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/05-UsingRepostorDataProtectorforPostgreSQL.mdx +++ b/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/05-UsingRepostorDataProtectorforPostgreSQL.mdx @@ -1,6 +1,6 @@ --- title: 'Using' -description: 'Walkthroughs of multiple Repostor Data Protector for PostgreSQL usage scenarios' +description: 'Walkthrough of example usage scenarios' --- The current RDP version is a command-line client. You run three commands: `postgresbackup`, `postgresquery`, and `postgresrestore`. The logwriter and logreader tools are called by PostgreSQL during execution of `archive_command` and `restore_command`. diff --git a/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/06-CertificationEnvironment.mdx index dd700ca1c67..78bc46cc22c 100644 --- a/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/06-CertificationEnvironment.mdx @@ -1,6 +1,6 @@ --- title: 'Certification environment' -description: 'Overview of the certification environment used for certifying Repostor Data Protector for PostgreSQL' +description: 'Overview of the certification environment' redirects: - /partner_docs/RepostorGuide/06-CertificationEnvironment/ --- diff --git a/advocacy_docs/partner_docs/SIBVisionsVisionX/04-ConfiguringSIBVisionsVisionX.mdx b/advocacy_docs/partner_docs/SIBVisionsVisionX/04-ConfiguringSIBVisionsVisionX.mdx index 559f6487c74..9a6e5027b26 100644 --- a/advocacy_docs/partner_docs/SIBVisionsVisionX/04-ConfiguringSIBVisionsVisionX.mdx +++ b/advocacy_docs/partner_docs/SIBVisionsVisionX/04-ConfiguringSIBVisionsVisionX.mdx @@ -1,6 +1,6 @@ --- title: 'Configuring' -description: 'Walkthrough of configuring SIB Visions VisionX' +description: 'Walkthrough of configuring the integration' --- Implementing SIB Visions VisionX with EDB Postgres Advanced Server or EDB Postgres Extended Server requires the following components: diff --git a/advocacy_docs/partner_docs/SIBVisionsVisionX/05-UsingSIBVisionsVisionX.mdx b/advocacy_docs/partner_docs/SIBVisionsVisionX/05-UsingSIBVisionsVisionX.mdx index 459f669fc14..be6a1dbaed6 100644 --- a/advocacy_docs/partner_docs/SIBVisionsVisionX/05-UsingSIBVisionsVisionX.mdx +++ b/advocacy_docs/partner_docs/SIBVisionsVisionX/05-UsingSIBVisionsVisionX.mdx @@ -1,6 +1,6 @@ --- title: 'Using' -description: 'Walkthroughs of multiple SIB Visions VisionX usage scenarios' +description: 'Walkthrough of example usage scenarios' --- These examples walk you though some of the common usage scenarios that can be used with EDB Postgres Advanced Server or EDB Postgres Extended Server. These are examples to help get you started and show how the products can work together. diff --git a/advocacy_docs/partner_docs/SIBVisionsVisionX/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/SIBVisionsVisionX/06-CertificationEnvironment.mdx index 1e32fc978a5..3104d19b267 100644 --- a/advocacy_docs/partner_docs/SIBVisionsVisionX/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/SIBVisionsVisionX/06-CertificationEnvironment.mdx @@ -1,6 +1,6 @@ --- title: 'Certification environment' -description: 'Overview of the certification environment used for certifying SIB Visions VisionX' +description: 'Overview of the certification environment' --- |   |   | diff --git a/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/04-ConfiguringThalesCipherTrustTransparentEncryption.mdx b/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/04-ConfiguringThalesCipherTrustTransparentEncryption.mdx index bfe650e1e87..d11d30109ce 100644 --- a/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/04-ConfiguringThalesCipherTrustTransparentEncryption.mdx +++ b/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/04-ConfiguringThalesCipherTrustTransparentEncryption.mdx @@ -1,6 +1,6 @@ --- title: 'Configuring' -description: 'Walkthrough of configuring Thales CipherTrust Transparent Encryption (CTE)' +description: 'Walkthrough of configuring the integration' --- diff --git a/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/05-UsingThalesCipherTrustTransparentEncryption.mdx b/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/05-UsingThalesCipherTrustTransparentEncryption.mdx index a61583ac745..0fc6d06ceac 100644 --- a/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/05-UsingThalesCipherTrustTransparentEncryption.mdx +++ b/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/05-UsingThalesCipherTrustTransparentEncryption.mdx @@ -1,6 +1,6 @@ --- title: 'Using' -description: 'Walkthroughs of multiple Thales CipherTrust Transparent Encryption (CTE) usage scenarios' +description: 'Walkthrough of example usage scenarios' --- CTE protects data either at the file level or at the storage device level. A CTE agent running on the Postgres host manages the files behind a GuardPoint by enforcing the policy associated with it and communicates data access events to the CipherTrust Manager for logging. A GuardPoint is usually associated with a Linux mount point or a Windows volume but can also be associated with a directory subtree. diff --git a/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/06-CertificationEnvironment.mdx index 13966b47a9e..685f65c5d1e 100644 --- a/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/ThalesCipherTrustTransparentEncryption/06-CertificationEnvironment.mdx @@ -1,6 +1,6 @@ --- title: 'Certification environment' -description: 'Overview of the certification environment used in the certification of Thales CipherTrust Transparent Encryption (CTE)' +description: 'Overview of the certification environment' --- |   |   | diff --git a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/04-ConfiguringVeritasNetBackupforPostgreSQL.mdx b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/04-ConfiguringVeritasNetBackupforPostgreSQL.mdx index b135cc2f49f..1756937df97 100644 --- a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/04-ConfiguringVeritasNetBackupforPostgreSQL.mdx +++ b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/04-ConfiguringVeritasNetBackupforPostgreSQL.mdx @@ -1,6 +1,6 @@ --- title: 'Configuring' -description: 'Walkthrough of configuring Veritas NetBackup for PostgreSQL' +description: 'Walkthrough of configuring the integration' --- Implementing Veritas NetBackup solution for backup/restore of PostgreSQL databases requires the following components: diff --git a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/05-UsingVeritasNetBackupForPostgreSQL.mdx b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/05-UsingVeritasNetBackupForPostgreSQL.mdx index 2fbb3b67d4a..d2ea6f6ec77 100644 --- a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/05-UsingVeritasNetBackupForPostgreSQL.mdx +++ b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/05-UsingVeritasNetBackupForPostgreSQL.mdx @@ -1,6 +1,6 @@ --- title: 'Using' -description: 'Walkthroughs of multiple Veritas NetBackup for PostgreSQL usage scenarios' +description: 'Walkthrough of example usage scenarios' --- Common backup/restore operations for PostgreSQL databases using Veritas NetBackup for PostgreSQL are: diff --git a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/06-CertificationEnvironment.mdx index 1539573025d..bcc4e553f23 100644 --- a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/06-CertificationEnvironment.mdx @@ -1,6 +1,6 @@ --- title: 'Certification environment' -description: 'Overview of the certification environment used in the certification of NetBackup for PostgreSQL' +description: 'Overview of the certification environment' --- |   |   | From a5563f5456185b0ece07de795780e9e97401d113 Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Thu, 3 Aug 2023 16:29:54 -0500 Subject: [PATCH 056/223] Update index.mdx Updated Long Term Support content and added supporting links for features described in other parts of the doc --- .../docs/postgres_for_kubernetes/1/index.mdx | 33 ++++++++++--------- 1 file changed, 18 insertions(+), 15 deletions(-) diff --git a/product_docs/docs/postgres_for_kubernetes/1/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/index.mdx index 6f00e5e9e10..523dbc4964d 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/index.mdx @@ -89,11 +89,12 @@ primary/standby architecture, using native streaming replication. ## Features unique to EDB Postgres of Kubernetes -- [Long Term Support](#long-term-support) for 1.18.x +- [Long Term Support](#long-term-support) - Red Hat certified operator for OpenShift -- Support on IBM Power +- Support on IBM Power and z/Linux through partnership with IBM +- [Oracle compatibility](https://www.enterprisedb.com/docs/epas/latest/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/) through EDB Postgres Advanced Sever +- [Transparent Data Encryption (TDE)](https://www.enterprisedb.com/docs/tde/latest/) through EDB Postgres Advanced Server - EDB Postgres for Kubernetes Plugin -- Oracle compatibility through EDB Postgres Advanced Sever - Velero/OADP cold backup support - Generic adapter for third-party Kubernetes backup tools @@ -107,18 +108,20 @@ You need a valid license key to use EDB Postgres for Kubernetes in production. ### Long Term Support -EDB is committed to declaring one version of EDB Postgres for Kubernetes per -year as a Long Term Support version. This version will be supported and receive -maintenance releases for an additional 12 months beyond the last release of -CloudNativePG by the community for the same version. For example, the last -version of 1.18 of CloudNativePG was released on June 12, 2023. This was -declared a LTS version of EDB Postgres for Kubernetes and it will be supported -for additional 12 months until June 12, 2024. Customers can expect that they -will have at least 6 months to move between LTS versions. So they should -expect the next LTS to be available by January 12, 2024 to allow at least 6 -months to migrate. While we encourage customers to regularly upgrade to the -latest version of the operator to take advantage of new features, having LTS -versions allows customers desiring additional stability to stay on the same +EDB is committed to declaring a Long Term Support (LTS) version of EDB +Postgres for Kubernetes annually (1.18 was our first). Each LTS version will +receive maintenance releases and be supported for an additional 12 months beyond +the last community release of CloudNativePG for the same version. + +For example, the last version of 1.18 of CloudNativePG was released on June 12, 2023. +Because this was declared an LTS version of EDB Postgres for Kubernetes, it will be supported +for additional 12 months until June 12, 2024. + +In addition, customers will always have at least 6 months to move between LTS versions. This +means a new LTS version will be available by January 12, 2024 at the latest. + +While we encourage customers to regularly upgrade to the latest version of the operator to take +advantage of new features, having LTS versions allows customers desiring additional stability to stay on the same version for 12-18 months before upgrading. ## Licensing From a81ae444fe7a9c193f3f192b8a6b5030b23f5cca Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 24 Aug 2023 13:38:49 -0400 Subject: [PATCH 057/223] Update configuring_cli.mdx --- product_docs/docs/pgd/5/cli/configuring_cli.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/cli/configuring_cli.mdx b/product_docs/docs/pgd/5/cli/configuring_cli.mdx index b1bc7a1f88a..8a3ba373087 100644 --- a/product_docs/docs/pgd/5/cli/configuring_cli.mdx +++ b/product_docs/docs/pgd/5/cli/configuring_cli.mdx @@ -7,7 +7,7 @@ PGD CLI can be installed on any system that can connect to the PGD cluster. To u ## PGD CLI and database connection strings -You might not need a database connection string. For example, when Trusted Postgres Architect installs the PGD CLI on a system, it also configures the connection to the PGD cluster, which means that the PGD CLI connects when run. +You might not need a database connection string. For example, when Trusted Postgres Architect installs the PGD CLI on a system, it also configures the connection to the PGD cluster, which means that the PGD CLI can connect to the cluster when run. If you're installing PGD CLI manually, you must give PGD CLI a database connection string so it knows which PGD cluster to connect to. From 700d7252f7a05ae550f9dfb0ddb7b13dbe624c16 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Thu, 24 Aug 2023 14:26:43 -0400 Subject: [PATCH 058/223] typo --- .../VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx index a4a7734d758..3941a3964af 100644 --- a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx @@ -1,6 +1,6 @@ --- title: 'Partner information' -description: 'Details of the parnter' +description: 'Details of the partner' redirects: - /partner_docs/VeritasGuide/02-PartnerInformation/ --- From 72f1d0d3d21773be7c64e21ab423878c21c454af Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 24 Aug 2023 16:15:47 -0400 Subject: [PATCH 059/223] Small edits to this biganimal content --- .../biganimal/release/reference/cli/managing_clusters.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index a866f5b2a69..2f97f75a835 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -249,7 +249,7 @@ You can list all deleted clusters using the `show-deleted-clusters` command and ### Restore a cluster -BigAnimal continuously backs up your PostgreSQL clusters. Using the CLI, you can restore a cluster from its backup to any point in time as long as the backups are retained in the backup storage. The restored cluster can be in another region and with different configurations. You can specify new configurations in the `cluster restore` command. For example: +BigAnimal continuously backs up your PostgreSQL clusters. Using the CLI, you can restore a cluster from its backup to any point in time as long as the backups are retained in the backup storage. The restored cluster can be in another region and have different configurations. You can specify new configurations in the `cluster restore` command. For example: ```shell biganimal cluster restore\ @@ -284,7 +284,7 @@ You can restore a cluster in a single cluster to a primary/standby high-availabi Use the BigAnimal `pgd` commands to create, retrieve information on, and manage distributed high-availability clusters. !!!note - In addition to the BigAnimal `pgd` commands, you can switch over and use additional commands available in the [EDB Postgres Distributed CLI](/pgd/latest/cli/) to perform PGD-specific operations. The only EDB Postgres Distributed CLI commands that aren't applicable with BigAnimal are `create-proxy` and `delete-proxy`. + In addition to the BigAnimal `pgd` commands, you can switch over and use commands available in the [EDB Postgres Distributed CLI](/pgd/latest/cli/) to perform PGD-specific operations. The only EDB Postgres Distributed CLI commands that don't apply to BigAnimal are `create-proxy` and `delete-proxy`. ### Create a distributed high-availability cluster @@ -403,7 +403,7 @@ biganimal pgd show [--id] [--deleted] ### Restore a distributed high-availability cluster -Restore a distributed high-availability cluster or a deleted distributed high-availability cluster to a new cluster on the same cloud provider. You can restore an active cluster or a deleted cluster within its retention period. You can only restore one data group. By default, the new cluster inherits all settings of the source cluster. You can change the cluster setting and database configurations by specifying new values in the configuration file. +Restore a distributed high-availability cluster or a deleted distributed high-availability cluster to a new cluster on the same cloud provider. You can restore an active cluster or a deleted cluster within its retention period. You can restore only one data group. By default, the new cluster inherits all settings of the source cluster. You can change the cluster setting and database configurations by specifying new values in the configuration file. The syntax of the command is: @@ -438,7 +438,7 @@ dataGroups: ### Get distributed high-availability cluster connection information -You first need to get your cluster group's connection information in order to connect to and use your BigAnimal distributed high-availability cluster. +To connect to and use your BigAnimal distributed high-availability cluster, you first need to get your cluster group's connection information. The syntax of the command is: From 6d1111a323c4695a8e58cb45347f4b0e43c55f33 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 24 Aug 2023 17:21:48 -0400 Subject: [PATCH 060/223] Light edits to reorged content --- .../ecpgplus_guide/installing_ecpgplus.mdx | 26 +++++++++---------- .../01_creating_a_procedure.mdx | 2 +- .../declaring_parameters.mdx | 6 ++--- .../about_transactions.mdx | 8 +++--- .../10_collections/about_collections.mdx | 2 +- .../03_using_the_forall_statement.mdx | 7 +++-- .../13_triggers/02_types_of_triggers.mdx | 4 +-- .../06_compound_trigger.mdx | 2 +- .../01_basic_object_concepts/02_methods.mdx | 6 ++--- .../01_basic_object_concepts/index.mdx | 4 +-- .../03_constructor_methods.mdx | 2 +- .../about_optimizer_hints.mdx | 6 ++--- 12 files changed, 39 insertions(+), 36 deletions(-) diff --git a/product_docs/docs/epas/15/application_programming/ecpgplus_guide/installing_ecpgplus.mdx b/product_docs/docs/epas/15/application_programming/ecpgplus_guide/installing_ecpgplus.mdx index 240bca41fd7..7570615a7ee 100644 --- a/product_docs/docs/epas/15/application_programming/ecpgplus_guide/installing_ecpgplus.mdx +++ b/product_docs/docs/epas/15/application_programming/ecpgplus_guide/installing_ecpgplus.mdx @@ -39,7 +39,7 @@ export PATH=$EDB_PATH:$PATH A makefile contains a set of instructions that tell the make utility how to transform a program written in C that contains embedded SQL into a C program. To try the examples, you need: -- A C compiler (and linker) +- A C compiler and linker - The make utility - ECPGPlus preprocessor and library - A makefile that contains instructions for ECPGPlus @@ -62,14 +62,14 @@ LDLIBS += $(LIBPATH) -lecpg -lpq ecpg -C PROC -c $(INCLUDES) $? ``` -The first two lines use the `pg_config` program to locate the necessary header files and library directories: +The first two lines use the pg_config program to locate the necessary header files and library directories: ```sql INCLUDES = -I$(shell pg_config --includedir) LIBPATH = -L $(shell pg_config --libdir) ``` -The `pg_config` program is shipped with EDB Postgres Advanced Server. +The pg_config program is shipped with EDB Postgres Advanced Server. make knows to use the `CFLAGS` variable when running the C compiler and `LDFLAGS` and `LDLIBS` when invoking the linker. ECPG programs must be linked against the ECPG runtime library (`-lecpg`) and the libpq library (`-lpq`). @@ -111,7 +111,7 @@ The make utility: In the sample makefile, make includes the `-C` option when invoking ECPGPlus to invoke ECPGPlus in Pro\*C-compatible mode. -If you include the `-C` `PROC` keywords on the command line, in addition to the ECPG syntax, you can use Pro\*C command line syntax. For example: +If you include the `-C` `PROC` keywords at the command line, in addition to the ECPG syntax, you can use Pro\*C command line syntax. For example: ```shell $ ecpg -C PROC INCLUDE=/usr/edb/as14/include acct_update.c @@ -127,16 +127,16 @@ The command line options are: | Option | Description | | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| -c | Automatically generate C code from embedded SQL code. | -| -C *mode* | Use the `-C` option to specify a compatibility mode:

`INFORMIX`

`INFORMIX_SE`

`PROC` | -| -D *symbol* | Define a preprocessor *symbol*.

The *-D* keyword is not supported when compiling in *PROC mode.* Instead, use the Oracle-style *‘DEFINE=’* clause. | -| -h | Parse a header file, this option includes option `'-c'`. | -| -i | Parse system, include files as well. | -| -I directory | Search *directory* for `include` files. | -| -o *outfile* | Write the result to *outfile*. | -| -r *option* | Specify runtime behavior; *option* can be:

`no_indicator` - Don't use indicators, but instead use special values to represent NULL values.

`prepare` - Prepare all statements before using them.

`questionmarks` - Allow use of a question mark as a placeholder.

`usebulk` - Enable bulk processing for `INSERT`, `UPDATE`, and `DELETE` statements that operate on host variable arrays. | +| -c | Generate C code from embedded SQL code. | +| -C <mode> | Specify a compatibility mode:

`INFORMIX`

`INFORMIX_SE`

`PROC` | +| -D <symbol> | Define a preprocessor symbol.

The -D keyword isn't supported when compiling in `PROC` mode. Instead, use the Oracle-style `‘DEFINE=’` clause. | +| -h | Parse a header file. This option includes option `'-c'`. | +| -i | Parse system. Include files as well. | +| -I <directory> | Search for `include` files. | +| -o <outfile> | Write the result to <outfile>. | +| -r <option> | Specify runtime behavior. The value of <option> can be:

`no_indicator` — Don't use indicators, but instead use special values to represent NULL values.

`prepare` — Prepare all statements before using them.

`questionmarks` — Allow use of a question mark as a placeholder.

`usebulk` — Enable bulk processing for `INSERT`, `UPDATE`, and `DELETE` statements that operate on host variable arrays. | | --regression | Run in regression testing mode. | -| -t | Turn on `autocommit` of transactions. | +| -t | Turn on autocommit of transactions. | | -l | Disable `#line` directives. | | --help | Display the help options. | | --version | Output version information. | diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx index 2c53ad027ad..6b3eb1053d3 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx @@ -11,7 +11,7 @@ The `CREATE PROCEDURE` command defines and names a standalone procedure that's s If you include a schema name, then the procedure is created in the specified schema. Otherwise it's created in the current schema. The name of the new procedure must not match any existing procedure with the same input argument types in the same schema. However, procedures of different input argument types can share a name. This is called *overloading*. !!! Note - Overloading of procedures is an EDB Postgres Advanced Server feature. **Overloading of stored, standalone procedures isn't compatible with Oracle databases.** + Overloading of procedures is an EDB Postgres Advanced Server feature. Overloading of stored, standalone procedures isn't compatible with Oracle databases. ## Updating the definition of an existing procedure diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/declaring_parameters.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/declaring_parameters.mdx index 807061bacd6..a84ced4e434 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/declaring_parameters.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/declaring_parameters.mdx @@ -4,7 +4,7 @@ title: "Declaring parameters" Declare parameters in the procedure or function definition, and enclose them in parentheses following the procedure or function name. Parameters declared in the procedure or function definition are known as *formal parameters*. When you invoke the procedure or function, the calling program supplies the actual data to use in the called program’s processing as well as the variables that receive the results of the called program’s processing. The data and variables supplied by the calling program when the procedure or function is called are referred to as the *actual parameters*. -The following is the general format of a formal parameter declaration. +The following is the general format of a formal parameter declaration: ```text ( [ IN | OUT | IN OUT ] [ DEFAULT ]) @@ -40,9 +40,9 @@ END; In this example, `p_deptno` is an `IN` formal parameter, `p_empno` and `p_ename` are `IN OUT` formal parameters, and `p_job, p_hiredate` and `p_sal` are `OUT` formal parameters. !!! Note - In the example, no maximum length was specified on the `VARCHAR2` parameters and no precision and scale were specified on the `NUMBER` parameters. It's illegal to specify a length, precision, scale, or other constraints on parameter declarations. These constraints are inherited from the actual parameters that are used when the procedure or function is called. + In the example, no maximum length was specified on the `VARCHAR2` parameters, and no precision and scale were specified on the `NUMBER` parameters. It's illegal to specify a length, precision, scale, or other constraints on parameter declarations. These constraints are inherited from the actual parameters that are used when the procedure or function is called. -The `emp_query` procedure can be called by another program, passing it the actual parameters. This example is another SPL program that calls `emp_query`. +The `emp_query` procedure can be called by another program, passing it the actual parameters. This example is another SPL program that calls `emp_query`: ```sql DECLARE diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/06_transaction_control/about_transactions.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/06_transaction_control/about_transactions.mdx index 42cc6364f32..2469034108f 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/06_transaction_control/about_transactions.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/06_transaction_control/about_transactions.mdx @@ -6,10 +6,10 @@ A transaction begins when the first SQL command is encountered in the SPL progra The transaction ends when one of the following occurs: -- **An unhandled exception occurs**. In this case, the effects of all database updates made during the transaction are rolled back, and the transaction is aborted. -- **A `COMMIT` command is encountered**. In this case, the effect of all database updates made during the transaction become permanent. -- **A `ROLLBACK` command is encountered**. In this case, the effects of all database updates made during the transaction are rolled back, and the transaction is aborted. If a new SQL command is encountered, a new transaction begins. -- **Control returns to the calling application** (such as Java or PSQL). In this case, the action of the application determines whether the transaction is committed or rolled back. The exception is when the transaction is in a block in which `PRAGMA AUTONOMOUS_TRANSACTION` was declared. In this case, the commitment or rollback of the transaction occurs independently of the calling program. +- An unhandled exception occurs. In this case, the effects of all database updates made during the transaction are rolled back, and the transaction is aborted. +- A `COMMIT` command is encountered. In this case, the effect of all database updates made during the transaction become permanent. +- A `ROLLBACK` command is encountered. In this case, the effects of all database updates made during the transaction are rolled back, and the transaction is aborted. If a new SQL command is encountered, a new transaction begins. +- Control returns to the calling application, such as Java or PSQL. In this case, the action of the application determines whether the transaction is committed or rolled back. The exception is when the transaction is in a block in which `PRAGMA AUTONOMOUS_TRANSACTION` was declared. In this case, the commitment or rollback of the transaction occurs independently of the calling program. !!! Note Unlike Oracle, DDL commands such as `CREATE TABLE` don't implicitly occur in their own transaction. Therefore, DDL commands don't cause an immediate database commit as in Oracle, and you can roll back DDL commands just like DML commands. diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/about_collections.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/about_collections.mdx index 312f99a6310..1071875345f 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/about_collections.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/about_collections.mdx @@ -12,7 +12,7 @@ The most commonly known type of collection is an array. In EDB Postgres Advanced To set up a collection: 1. Define a collection of the desired type. You can do this in the declaration section of an SPL program, which results in a *local type* that you can access only in that program. For nested table and varray types, you can also do this using the `CREATE TYPE` command, which creates a persistent, *standalone type* that any SPL program in the database can reference. -2. Declare variables of the collection type. The collection associated with the declared variable is *uninitialized* at this point if no value assignment is made as part of the variable declaration. +2. Declare variables of the collection type. The collection associated with the declared variable is uninitialized at this point if no value assignment is made as part of the variable declaration. ## Initializing a null collection diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement.mdx index 2a5dc71c8cc..860cfa6e692 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement.mdx @@ -6,7 +6,7 @@ redirects: -You can use collections to process DML commands more efficiently by passing all the values to be used for repetitive execution of a `DELETE`, `INSERT`, or `UPDATE` command in one pass to the database server. The alternative is to reiteratively invoking the DML command with new values. Specify the DML command to process this way with the `FORALL` statement. In addition, provide one or more collections in the DML command where you want to subsitute different values each time the command is executed. +You can use collections to process DML commands more efficiently by passing all the values to be used for repetitive execution of a `DELETE`, `INSERT`, or `UPDATE` command in one pass to the database server. The alternative is to reiteratively invoke the DML command with new values. Specify the DML command to process this way with the `FORALL` statement. In addition, provide one or more collections in the DML command where you want to subsitute different values each time the command is executed. ## Syntax @@ -19,7 +19,10 @@ FORALL IN .. ## How it works -If an exception occurs during any iteration of the `FORALL` statement, all updates that occurred since the start of the execution of the `FORALL` statement are rolled back. This behavior **isn't compatible** with Oracle databases. Oracle allows explicit use of the `COMMIT` or `ROLLBACK` commands to control whether to commit or roll back updates that occurred prior to the exception. +If an exception occurs during any iteration of the `FORALL` statement, all updates that occurred since the start of the execution of the `FORALL` statement are rolled back. + +!!! Note + This behavior isn't compatible with Oracle databases. Oracle allows explicit use of the `COMMIT` or `ROLLBACK` commands to control whether to commit or roll back updates that occurred prior to the exception. The `FORALL` statement creates a loop. Each iteration of the loop increments the `index` variable. You typically use the `index` in the loop to select a member of a collection. Control the number of iterations with the `lower_bound .. upper_bound` clause. The loop executes once for each integer between the `lower_bound` and `upper_bound` (inclusive), and the index increments by one for each iteration. diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/13_triggers/02_types_of_triggers.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/13_triggers/02_types_of_triggers.mdx index 390529a1f64..347856c8faa 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/13_triggers/02_types_of_triggers.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/13_triggers/02_types_of_triggers.mdx @@ -12,9 +12,9 @@ redirects: EDB Postgres Advanced Server supports *row-level* and *statement-level* triggers. -- A *row-level trigger* fires once for each row that's affected by a triggering event. For example, suppose deletion is defined as a triggering event on a table, and a single `DELETE` command is issued that deletes five rows from the table. In this case, the trigger fires five times, once for each row. +- A row-level trigger fires once for each row that's affected by a triggering event. For example, suppose deletion is defined as a triggering event on a table, and a single `DELETE` command is issued that deletes five rows from the table. In this case, the trigger fires five times, once for each row. -- A *statement-level* trigger fires once per triggering statement, regardless of the number of rows affected by the triggering event. In the previous example of a single `DELETE` command deleting five rows, a statement-level trigger fires only once. +- A statement-level trigger fires once per triggering statement, regardless of the number of rows affected by the triggering event. In the previous example of a single `DELETE` command deleting five rows, a statement-level trigger fires only once. You can define the sequence of actions regarding whether the trigger code block executes before or after the triggering statement for statement-level triggers. For row-level triggers, you can define whether the trigger code block executes before or after each row is affected by the triggering statement. diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/06_compound_trigger.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/06_compound_trigger.mdx index 790774bb68d..9f267d486f1 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/06_compound_trigger.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/06_compound_trigger.mdx @@ -8,7 +8,7 @@ redirects: ## Defining a compound trigger on a table -This example shows a compound trigger that records a change to the employee salary by defining a compound trigger (named `hr_trigger`) on the `emp` table. +This example shows a compound trigger that records a change to the employee salary by defining a compound trigger named `hr_trigger` on the `emp` table. 1. Create a table named `emp`: diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx index 37e4955855e..5a048e37fa7 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx @@ -8,6 +8,6 @@ redirects: Methods are SPL procedures or functions defined in an object type. Methods are categorized into three general types: -- *Member methods* — Procedures or functions that operate in the context of an object instance. Member methods have access to and can change the attributes of the object instance on which they're operating. -- *Static methods* — Procedures or functions that operate independently of any particular object instance. Static methods don't have access to and can't change the attributes of an object instance. -- *Constructor methods* — Functions used to create an instance of an object type. A default constructor method is always provided when an object type is defined. +- Member methods — Procedures or functions that operate in the context of an object instance. Member methods have access to and can change the attributes of the object instance on which they're operating. +- Static methods — Procedures or functions that operate independently of any particular object instance. Static methods don't have access to and can't change the attributes of an object instance. +- Constructor methods — Functions used to create an instance of an object type. A default constructor method is always provided when an object type is defined. diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/index.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/index.mdx index e6369debb98..89c4ee511b3 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/index.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/index.mdx @@ -13,8 +13,8 @@ redirects: An object type is a description or definition of some entity. This definition of an object type is characterized by two components: -- *Attributes* — Fields that describe particular characteristics of an object instance. For a person object, examples are name, address, gender, date of birth, height, weight, eye color, and occupation. -- *Methods* — Programs that perform some type of function or operation on or are related to an object. For a person object, examples are calculating the person’s age, displaying the person’s attributes, and changing the values assigned to the person’s attributes. +- Attributes — Fields that describe particular characteristics of an object instance. For a person object, examples are name, address, gender, date of birth, height, weight, eye color, and occupation. +- Methods — Programs that perform some type of function or operation on or are related to an object. For a person object, examples are calculating the person’s age, displaying the person’s attributes, and changing the values assigned to the person’s attributes.
diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx index 2053696e50a..5b156e5b03d 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx @@ -36,7 +36,7 @@ CONSTRUCTOR FUNCTION address The body of the default constructor sets each member to `NULL`. -To create a custom constructor, declare the constructor function (using the keyword constructor) in the `CREATE TYPE` command and define the construction function in the `CREATE TYPE BODY` command. For example, you might want to create a custom constructor for the `address` type that computes the city and state given a `street_address` and `postal_code`: +To create a custom constructor, using the keyword constructor, declare the constructor function in the `CREATE TYPE` command and define the construction function in the `CREATE TYPE BODY` command. For example, you might want to create a custom constructor for the `address` type that computes the city and state given a `street_address` and `postal_code`: ```sql CREATE TYPE address AS OBJECT diff --git a/product_docs/docs/epas/15/application_programming/optimizing_code/05_optimizer_hints/about_optimizer_hints.mdx b/product_docs/docs/epas/15/application_programming/optimizing_code/05_optimizer_hints/about_optimizer_hints.mdx index 9e16c46c6d0..0fd018abed8 100644 --- a/product_docs/docs/epas/15/application_programming/optimizing_code/05_optimizer_hints/about_optimizer_hints.mdx +++ b/product_docs/docs/epas/15/application_programming/optimizing_code/05_optimizer_hints/about_optimizer_hints.mdx @@ -2,7 +2,7 @@ title: "About optimizer hints" --- -An *optimizer hint* is one or more directives embedded in a comment-like syntax that immediately follows a `DELETE`, `INSERT`, `SELECT` or `UPDATE` command. Keywords in the comment instruct the server to use or avoid a specific plan when producing the result set. +An *optimizer hint* is one or more directives embedded in a comment-like syntax that immediately follows a `DELETE`, `INSERT`, `SELECT`, or `UPDATE` command. Keywords in the comment instruct the server to use or avoid a specific plan when producing the result set. ## Synopsis @@ -23,8 +23,8 @@ If you're using the first form, the hint and optional comment might span multipl Note: - The database server always tries to use the specified hints if at all possible. -- If a planner method parameter is set so as to disable a certain plan type, then this plan isn't used even if it is specified in a hint, unless there are no other possible options for the planner. Examples of planner method parameters are `enable_indexscan`, `enable_seqscan`, `enable_hashjoin`, `enable_mergejoin`, and `enable_nestloop`. These are all Boolean parameters. -- The hint is embedded in a comment. As a consequence, if the hint is misspelled or if any parameter to a hint such as view, table, or column name is misspelled or nonexistent in the SQL command, there's no indication that an error occurred. No syntax error is given. The entire hint is silently ignored. +- If a planner method parameter is set so as to disable a certain plan type, then this plan isn't used even if it's specified in a hint, unless there are no other possible options for the planner. Examples of planner method parameters are `enable_indexscan`, `enable_seqscan`, `enable_hashjoin`, `enable_mergejoin`, and `enable_nestloop`. These are all Boolean parameters. +- The hint is embedded in a comment. As a consequence, if the hint is misspelled or if any parameter to a hint, such as view, table, or column name, is misspelled or nonexistent in the SQL command, there's no indication that an error occurred. No syntax error is given. The entire hint is silently ignored. - If an alias is used for a table name in the SQL command, then you must use the alias name in the hint, not the original table name. For example, in the command `SELECT /*+ FULL(acct) */ * FROM accounts acct ..., acct`, you must specify the alias for `accounts` in the `FULL` hint, not in the table name `accounts`. Use the `EXPLAIN` command to ensure that the hint is correctly formed and the planner is using the hint. From ec1b3f1de5491fe5b536c2fa8b4bd072979f54df Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Thu, 24 Aug 2023 15:21:41 -0700 Subject: [PATCH 061/223] Update architectures.mdx --- product_docs/docs/pgd/5/architectures.mdx | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/pgd/5/architectures.mdx b/product_docs/docs/pgd/5/architectures.mdx index aee575d6b11..210ac0bcf2f 100644 --- a/product_docs/docs/pgd/5/architectures.mdx +++ b/product_docs/docs/pgd/5/architectures.mdx @@ -94,12 +94,14 @@ they aren't part of the standard Always On architectures. * Can be 3 data nodes (recommended) * Can be 2 data nodes and 1 witness that doesn't hold data (not depicted) * A PGD Proxy for each data node with affinity to the applications - * Can be colocated with data node + * Can be colocated with data node (recommended) + * Can be located on a separate node + * Configuration and infrastructure symmetry of data nodes is expected to ensure proper resources are available to handle application workload when rerouted * Barman for backup and recovery (not depicted) * Offsite is optional but recommended - * Can be shared by multiple clusters + * Can be shared by multiple PGD clusters * Postgres Enterprise Manager (PEM) for monitoring (not depicted) - * Can be shared by multiple clusters + * Can be shared by multiple PGD clusters ### Always On multi-location @@ -112,14 +114,17 @@ they aren't part of the standard Always On architectures. * Can be 3 data nodes (recommended) * Can be 2 data nodes and 1 witness which does not hold data (not depicted) * A PGD-Proxy for each data node with affinity to the applications - * can be co-located with data node + * can be co-located with data node (recommended) + * can be located on a separate node + * Configuration and infrastructure symmetry of data nodes and locations is expected to ensure proper resources are available to handle application workload when rerouted * Barman for backup and recovery (not depicted). - * Can be shared by multiple clusters + * Can be shared by multiple PGD clusters * Postgres Enterprise Manager (PEM) for monitoring (not depicted). - * Can be shared by multiple clusters + * Can be shared by multiple PGD clusters * An optional witness node must be placed in a third region to increase tolerance for location failure. * Otherwise, when a location fails, actions requiring global consensus are blocked, such as adding new nodes and distributed DDL. + ## Choosing your architecture All architectures provide the following: From 836845aedb01b1a0ecaa35bab1031d07edd2cf0b Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Thu, 24 Aug 2023 17:53:36 -0700 Subject: [PATCH 062/223] Update index.mdx removed Extreme HA nomenclature - (link may still need to be updated if path changes) --- product_docs/docs/pgd/5/quickstart/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/quickstart/index.mdx b/product_docs/docs/pgd/5/quickstart/index.mdx index e7d45925288..9101908990a 100644 --- a/product_docs/docs/pgd/5/quickstart/index.mdx +++ b/product_docs/docs/pgd/5/quickstart/index.mdx @@ -20,7 +20,7 @@ navigation: EDB Postgres Distributed (PGD) is a multi-master replicating implementation of Postgres designed for high performance and availability. You can create database clusters made up of many bidirectionally synchronizing database nodes. The clusters can have a number of proxy servers that direct your query traffic to the most available nodes, adding further resilience to your cluster configuration. !!! Note Fully managed BigAnimal - If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as the Extreme High Availability option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal Extreme High Availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-preview). + If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal Distributed High Availability clusters](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-preview). PGD is very configurable. To quickly evaluate and deploy PGD, use this quick start. It'll get you up and running with a fully configured PGD cluster using the same tools that you'll use to deploy to production. This quick start includes: From 63a60c7013e4ff394e3a1956dcdd480a6b3d13eb Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Thu, 24 Aug 2023 18:13:29 -0700 Subject: [PATCH 063/223] Update deployments.mdx updated deployment info --- product_docs/docs/pgd/5/deployments.mdx | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index f57916d3e1b..743593a332a 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,9 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. See [Deploying with TPA](tpa) for more information. -- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account where it's operated by the Postgres experts. BigAnimal makes it easy to set up, manage, and scale your databases. The addition of extreme-high-availability support through EDB Postgres Distributed (PGD) allows single-region Always On Gold clusters. These clusters are two PGD groups in different availability zones in a single cloud region, with a witness node in a third availability zone. See [Extreme high availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-beta) in the [BigAnimal documentation](/biganimal/latest) for more information. +- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or an EDB hosted account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed, high availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-beta) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. -Coming soon: - -- EDB Postgres Distributed for Kubernetes will be a Kubernetes operator designed, developed, and supported by EDB. It will cover the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server and additional supported platforms including IBM Power and OpenShift. +- EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview. From 1f02bee835dc73e048f85adee20d2a5e66367720 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Fri, 25 Aug 2023 11:03:57 +0530 Subject: [PATCH 064/223] Added more in release notes --- product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx | 3 ++- product_docs/docs/pem/9/pem_rel_notes/index.mdx | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx index 1e01310c8ab..9d0f9cb8b66 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx @@ -16,4 +16,5 @@ New features, enhancements, bug fixes, and other changes in PEM 9.3.0 include: | Bug Fix | Removed the newline character in the alert details from the payload of Webhook. | | Bug Fix | Added the support to allow the webhook endpoint registration without providing the client SSL certificates and key files or CA certificates using `allow_insecure_webhooks` parameter in the `agent.cfg` file. Also set `ssl_verifypeer` parameter to `false` while establishing the connection with webhook endpoint. | | Bug Fix | Improved the error message for better user understanding of put/post server REST API. | -| Bug Fix | Fixed an issue related to the backup sizes displaying on the PEM's Barman dashbaord. | \ No newline at end of file +| Bug Fix | Fixed an issue related to the backup sizes displaying on the PEM's Barman dashbaord. | +| Bug Fix | Fixed an issue with unformatted data while importing the audit logs. | \ No newline at end of file diff --git a/product_docs/docs/pem/9/pem_rel_notes/index.mdx b/product_docs/docs/pem/9/pem_rel_notes/index.mdx index e7909211984..03b08dbda47 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/index.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/index.mdx @@ -1,6 +1,7 @@ --- title: "Release notes" navigation: + - 930_rel_notes - 922_rel_notes - 921_rel_notes - 920_rel_notes From c571b14ee1d32159d8de9053f56187544ea9feae Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Fri, 25 Aug 2023 11:36:38 +0530 Subject: [PATCH 065/223] Edited release notes --- .../docs/pem/9/pem_rel_notes/930_rel_notes.mdx | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx index 9d0f9cb8b66..96a0525d819 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx @@ -6,15 +6,14 @@ New features, enhancements, bug fixes, and other changes in PEM 9.3.0 include: | Type | Description | | ----------- | -------------------------------------------------------------------------------------------------| -| Enhancement | Added the functionality to delete all the existing alert while using the copy alert feature. | +| Enhancement | Added the functionality to delete all the existing alerts while using the copy alert feature. | | Enhancement | Added PostgreSQL and EPAS 16 support as a backend database server and monitoring server. | | Enhancement | Added support to customize the default email templates. | -| Enhancement | Added the support to download the alert history report for agents and servers from the reports tab. | +| Enhancement | Added support to download the alert history report for agents and servers from the reports tab. | | Enhancement | Added options to reuse the existing agent SSL certificates and key files while configuring the PEM server. | | Bug Fix | Added the functionality to add/view ignore mount points in the agent REST API. | | Bug Fix | Added the `hostaddr` body parameter to the server REST API. | -| Bug Fix | Removed the newline character in the alert details from the payload of Webhook. | -| Bug Fix | Added the support to allow the webhook endpoint registration without providing the client SSL certificates and key files or CA certificates using `allow_insecure_webhooks` parameter in the `agent.cfg` file. Also set `ssl_verifypeer` parameter to `false` while establishing the connection with webhook endpoint. | -| Bug Fix | Improved the error message for better user understanding of put/post server REST API. | -| Bug Fix | Fixed an issue related to the backup sizes displaying on the PEM's Barman dashbaord. | +| Bug Fix | Fixed an issue by removing the newline character in the alert details from the payload of Webhook. | +| Bug Fix | Added support to allow the Webhook endpoint registration without providing the client SSL certificates and key files or CA certificates using `allow_insecure_webhooks` parameter in the `agent.cfg` file.| +| Bug Fix | Fixed an issue related to the backup sizes displaying on the PEM's Barman dashboard. | | Bug Fix | Fixed an issue with unformatted data while importing the audit logs. | \ No newline at end of file From 1e4040cdc1d1f01872b0485ec966473b03895b32 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Fri, 25 Aug 2023 13:47:14 +0530 Subject: [PATCH 066/223] Edits done as per feedback from Shubam Tondare and Shubham Agrawal --- .../9/installing/configuring_the_pem_server_on_linux.mdx | 2 +- product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/pem/9/installing/configuring_the_pem_server_on_linux.mdx b/product_docs/docs/pem/9/installing/configuring_the_pem_server_on_linux.mdx index 1372d7d887e..8d3a039b251 100644 --- a/product_docs/docs/pem/9/installing/configuring_the_pem_server_on_linux.mdx +++ b/product_docs/docs/pem/9/installing/configuring_the_pem_server_on_linux.mdx @@ -37,7 +37,7 @@ When invoking the script, you can include command line options to specify config | `-t` or `--type` | The installation type: Specify `1` if the configuration is for web services and backend database, `2` if you're configuring web services, or `3` if you're configuring the backend database. If you specify `3`, the database must reside on the local host. | | `-un` or `--uninstall-pem-server` | The option to uninstall the PEM server. | | `-nhc` or `--no-hba-change` | The option to skip the changes done to `pg_hba.conf` and `pg_config` files. | -| `-uac` or `--use-agent-sslcert` | The option to reuse the existing agent SSL certificates while configuring the PEM server. | +| `-uac` or `--use-agent-sslcert` | The option to reuse the existing agent SSL certificate while configuring the PEM server. | | `-uak` or `--use-agent-sslkey` | The option to reuse the existing agent SSL key while configuring the PEM server. | | `-h` or `--help` | The option to list all the available options while configuring the PEM server. | diff --git a/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx index 96a0525d819..fe54a38d40a 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx @@ -7,10 +7,10 @@ New features, enhancements, bug fixes, and other changes in PEM 9.3.0 include: | Type | Description | | ----------- | -------------------------------------------------------------------------------------------------| | Enhancement | Added the functionality to delete all the existing alerts while using the copy alert feature. | -| Enhancement | Added PostgreSQL and EPAS 16 support as a backend database server and monitoring server. | +| Enhancement | Added PostgreSQL and EPAS 16 beta support as a backend database server and monitoring server. | | Enhancement | Added support to customize the default email templates. | -| Enhancement | Added support to download the alert history report for agents and servers from the reports tab. | -| Enhancement | Added options to reuse the existing agent SSL certificates and key files while configuring the PEM server. | +| Enhancement | Added support to download the alert history report for agents and servers. | +| Enhancement | Added options to reuse the existing agent SSL certificate and key file while configuring the PEM server. | | Bug Fix | Added the functionality to add/view ignore mount points in the agent REST API. | | Bug Fix | Added the `hostaddr` body parameter to the server REST API. | | Bug Fix | Fixed an issue by removing the newline character in the alert details from the payload of Webhook. | From 56d335b118bf7a1ff278bc01e2adc5ff08f67883 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 05:24:40 -0400 Subject: [PATCH 067/223] fixed link to BA docs --- product_docs/docs/pgd/5/deployments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index 743593a332a..365f7b6ff22 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,7 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. See [Deploying with TPA](tpa) for more information. -- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or an EDB hosted account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed, high availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-beta) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. +- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or an EDB hosted account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed, high availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. - EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview. From e2854896eeeeb40e39c10bd1ed5933e0ea7a8185 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 08:54:26 -0400 Subject: [PATCH 068/223] Replication Server: adding driver step to upgrade instructions --- .../eprs/7/installing/upgrading_replication_server/index.mdx | 3 ++- .../upgrading_replication_server/upgrading_linux.mdx | 3 +++ .../upgrading_with_gui_installer.mdx | 2 ++ .../upgrading_with_xdb_rpm_package.mdx | 2 ++ 4 files changed, 9 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx index 35567da06db..48eb227facf 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx @@ -15,11 +15,12 @@ It is assumed that you are installing Replication Server 7.x on the same host ma If you are using a version of Replication Server earlier than 6.2.x on Linux, first upgrade to 6.2.x, and then upgrade to version 7.x. See: - [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) - For more details on upgrading Replication Server, see: - [Updating the publication and subscription server](updating_sub_and_pub_ports) - [Upgrading from a Replication Server 7.x installation on Linux](upgrading_linux) - [Upgrading with the graphical user interface installer](upgrading_with_gui_installer) +After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it (for Linux) or rename the driver (for Windows). See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. + diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx index 9649957e183..988eaf4f128 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx @@ -15,3 +15,6 @@ If you have an existing Replication Server 7.x installation on Linux, you can us `yum upgrade edb-xdb*` If you are upgrading from a Replication Server 6.2 installation on Linux, see [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) for details. + +After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. + diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx index 6ea33561b9a..d15969f4d99 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx @@ -47,6 +47,8 @@ You can upgrade to Replication Server 7 using the graphical user interface insta If you don't need to adjust the port numbers, register the publication server and subscription server with the Replication Server console as described in [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). The existing replication systems appear in the replication tree of the Replication Server Console. +After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink (for Linux) to it or rename the driver (for Windows). See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. + You are now ready to use Replication Server 7 to create new replication systems and manage existing ones. !!! Note diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx index ef0d1a47e7e..97c6a720728 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx @@ -183,4 +183,6 @@ If you're using Replication Server 6.2.x that was installed using the Replicatio If you don't need to adjust the port numbers, register the publication server and subscription server with the Replication Server console as described in [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server)). The existing replication systems appear in the replication tree of the Replication Server console. +After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. + You are now ready to use Replication Server 7 to create new replication systems and manage existing ones. From f8e108c2f53001fd6623615aa2f2b5acaecc67e5 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 10:20:06 -0400 Subject: [PATCH 069/223] BigAnimal: a few more name change misses --- product_docs/docs/biganimal/release/overview/updates.mdx | 2 +- .../using_cluster/03_modifying_your_cluster/index.mdx | 6 +++--- .../biganimal/release/using_cluster/managing_replicas.mdx | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/biganimal/release/overview/updates.mdx b/product_docs/docs/biganimal/release/overview/updates.mdx index 8ade89424af..04deef53917 100644 --- a/product_docs/docs/biganimal/release/overview/updates.mdx +++ b/product_docs/docs/biganimal/release/overview/updates.mdx @@ -8,7 +8,7 @@ EDB reserves the right to upgrade customers to the latest minor version without In some cases, these updates might terminate existing network connections to your clusters. If that happens, the outage is typically less than 30 seconds. Be sure your applications are configured to automatically reconnect when connections are interrupted. Most modern database libraries do this by default. -If you want to control when the updates are pushed, you can specify a weekly maintenance window for each cluster or each data group in the case of an extreme-high-availability cluster. BigAnimal displays a *scheduled maintenance* message on your cluster list four hours prior to the scheduled maintenance time to remind you of the upcoming maintenance window. This reminder allows you to make any necessary preparations, such as saving your work and closing any open connections. For more information on specifying maintenance windows, see [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). +If you want to control when the updates are pushed, you can specify a weekly maintenance window for each cluster or each data group in the case of an distributed high-availability cluster. BigAnimal displays a *scheduled maintenance* message on your cluster list four hours prior to the scheduled maintenance time to remind you of the upcoming maintenance window. This reminder allows you to make any necessary preparations, such as saving your work and closing any open connections. For more information on specifying maintenance windows, see [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). ## Connectivity issues after an automatic upgrade diff --git a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx index 22468f65f91..c70eceb791b 100644 --- a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx @@ -25,14 +25,14 @@ You can also modify your cluster by installing Postgres extensions. See [Postgre | Settings | Tab | Notes | | ---------------------------------------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Cluster type | **Cluster Info** | You can't switch from a single-node cluster or a high-availability cluster to an extreme-high-availability cluster or vice versa. | + | Cluster type | **Cluster Info** | You can't switch from a single-node cluster or a high-availability cluster to an distributed high-availability cluster or vice versa. | | Number of replicas (for a high-availability cluster) | **Cluster Info** | — | | Cluster name and password | **Cluster Settings** | — | | Instance type | **Cluster Settings** | Changing the instance type can incur higher cloud infrastructure charges. | | Volume type | **Cluster Settings** | You can't switch between the io2 and io2 Block Express volume types in an AWS cluster. | | Volume properties | **Cluster Settings** | It can take up to six hours to tune IOPS or resize the disks of your cluster because AWS requires a cooldown period after volume modifications, as explained in [Limitations](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/modify-volume-requirements.html). The volume properties are disabled and can't be modified while this is in progress. | | Networking type (public or private) | **Cluster Settings** | If you're using Azure and previously set up a private link and want to change to a public network, you must remove the private link resources before making the change. | - | Nodes (for an extreme-high-availability cluster) | **Data Groups** | — | + | Nodes (for an distributed high-availability cluster) | **Data Groups** | — | | Database configuration parameters | **DB Configuration** | If you're using faraway replicas, only a small subset of parameters are editable. These parameters need to be modified in the replica when increased in the replica's source cluster. See [Modify a faraway replica](/biganimal/latest/using_cluster/managing_replicas/#modify-a-faraway-replica) for details. | | Retention period for backups | **Additional Settings** | — | | Custom maintenance window | **Additional Settings** | Set or modify a maintenance window in which maintenance upgrades occur for the cluster. See [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). | @@ -48,7 +48,7 @@ You can also modify your cluster by installing Postgres extensions. See [Postgre ## Modify a data group -You can modify the data groups in your extreme-high-availability cluster by editing the configuration settings. +You can modify the data groups in your distributed high-availability cluster by editing the configuration settings. 1. Sign in to the [BigAnimal portal](https://portal.biganimal.com). diff --git a/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx b/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx index 55073ed6224..07a6eff2185 100644 --- a/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx @@ -97,7 +97,7 @@ You can promote a faraway replica to a full-fledged cluster, which makes it capa 1. The cluster settings are populated with values inherited from the source cluster. You can edit the cluster settings while creating your cluster. !!! NoteNotes - - You can promote a faraway replica to a single node or high-availability cluster but not to an extreme-high-availability cluster. + - You can promote a faraway replica to a single node or high-availability cluster but not to an distributed high-availability cluster. - While promoting a replica to a cluster, you can't modify the **Provider** and **Region** fields and the **Database Type** section or enable read-only workloads. 1. Select **Promote Replica**. From 6748fb249e43e92afdb9e93b0cb11c6e13e536a6 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Fri, 25 Aug 2023 10:49:28 -0400 Subject: [PATCH 070/223] update to terminology used in BA docs --- product_docs/docs/pgd/5/deployments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index 365f7b6ff22..8bd88c5b120 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,7 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. See [Deploying with TPA](tpa) for more information. -- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or an EDB hosted account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed, high availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. +- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. - EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview. From 036c2b210836982e89250e4e48805cb852b76538 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 11:14:28 -0400 Subject: [PATCH 071/223] Homepage: What's new - epas reorg --- src/pages/index.js | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/pages/index.js b/src/pages/index.js index 9ae45ffbb86..8358dcdc884 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -99,18 +99,18 @@ const Page = () => ( className="homepage-headling-link" to="/pgd/latest/reference/" > - EDB Postgres Distributed's ready reference + Find the EPAS content you're looking for

- Use the new reference section in EDB Postgres Distributed to - quickly look up views, catalogs, functions, and variables. - It's a new view of the documentation designed to centralize - essential information and speed up your development. + Whether you are an application programmer trying to debug your + programs or a DBA configuring your database, the new structure + of the EDB Postgres Advanced Server documentation makes + finding relevant content a snap.

From 82b42548c1eeec1df086b4a7c6d391fe24c202ea Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Fri, 25 Aug 2023 11:22:47 -0400 Subject: [PATCH 072/223] fixed link (keeping preview until GA) --- product_docs/docs/pgd/5/deployments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index 8bd88c5b120..ea5c28523f4 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,7 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. See [Deploying with TPA](tpa) for more information. -- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. +- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability-preview) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. - EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview. From 56945e6d8f5aa889c072bcf2819e8e61aca2921c Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 11:36:36 -0400 Subject: [PATCH 073/223] fixed articles --- product_docs/docs/biganimal/release/overview/updates.mdx | 2 +- .../release/using_cluster/03_modifying_your_cluster/index.mdx | 4 ++-- .../biganimal/release/using_cluster/managing_replicas.mdx | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/biganimal/release/overview/updates.mdx b/product_docs/docs/biganimal/release/overview/updates.mdx index 04deef53917..f232efe1632 100644 --- a/product_docs/docs/biganimal/release/overview/updates.mdx +++ b/product_docs/docs/biganimal/release/overview/updates.mdx @@ -8,7 +8,7 @@ EDB reserves the right to upgrade customers to the latest minor version without In some cases, these updates might terminate existing network connections to your clusters. If that happens, the outage is typically less than 30 seconds. Be sure your applications are configured to automatically reconnect when connections are interrupted. Most modern database libraries do this by default. -If you want to control when the updates are pushed, you can specify a weekly maintenance window for each cluster or each data group in the case of an distributed high-availability cluster. BigAnimal displays a *scheduled maintenance* message on your cluster list four hours prior to the scheduled maintenance time to remind you of the upcoming maintenance window. This reminder allows you to make any necessary preparations, such as saving your work and closing any open connections. For more information on specifying maintenance windows, see [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). +If you want to control when the updates are pushed, you can specify a weekly maintenance window for each cluster or each data group in the case of a distributed high-availability cluster. BigAnimal displays a *scheduled maintenance* message on your cluster list four hours prior to the scheduled maintenance time to remind you of the upcoming maintenance window. This reminder allows you to make any necessary preparations, such as saving your work and closing any open connections. For more information on specifying maintenance windows, see [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). ## Connectivity issues after an automatic upgrade diff --git a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx index c70eceb791b..69f3e3dfed0 100644 --- a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx @@ -25,14 +25,14 @@ You can also modify your cluster by installing Postgres extensions. See [Postgre | Settings | Tab | Notes | | ---------------------------------------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Cluster type | **Cluster Info** | You can't switch from a single-node cluster or a high-availability cluster to an distributed high-availability cluster or vice versa. | + | Cluster type | **Cluster Info** | You can't switch from a single-node cluster or a high-availability cluster to a distributed high-availability cluster or vice versa. | | Number of replicas (for a high-availability cluster) | **Cluster Info** | — | | Cluster name and password | **Cluster Settings** | — | | Instance type | **Cluster Settings** | Changing the instance type can incur higher cloud infrastructure charges. | | Volume type | **Cluster Settings** | You can't switch between the io2 and io2 Block Express volume types in an AWS cluster. | | Volume properties | **Cluster Settings** | It can take up to six hours to tune IOPS or resize the disks of your cluster because AWS requires a cooldown period after volume modifications, as explained in [Limitations](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/modify-volume-requirements.html). The volume properties are disabled and can't be modified while this is in progress. | | Networking type (public or private) | **Cluster Settings** | If you're using Azure and previously set up a private link and want to change to a public network, you must remove the private link resources before making the change. | - | Nodes (for an distributed high-availability cluster) | **Data Groups** | — | + | Nodes (for a distributed high-availability cluster) | **Data Groups** | — | | Database configuration parameters | **DB Configuration** | If you're using faraway replicas, only a small subset of parameters are editable. These parameters need to be modified in the replica when increased in the replica's source cluster. See [Modify a faraway replica](/biganimal/latest/using_cluster/managing_replicas/#modify-a-faraway-replica) for details. | | Retention period for backups | **Additional Settings** | — | | Custom maintenance window | **Additional Settings** | Set or modify a maintenance window in which maintenance upgrades occur for the cluster. See [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). | diff --git a/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx b/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx index 07a6eff2185..2f0727e496a 100644 --- a/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx @@ -97,7 +97,7 @@ You can promote a faraway replica to a full-fledged cluster, which makes it capa 1. The cluster settings are populated with values inherited from the source cluster. You can edit the cluster settings while creating your cluster. !!! NoteNotes - - You can promote a faraway replica to a single node or high-availability cluster but not to an distributed high-availability cluster. + - You can promote a faraway replica to a single node or high-availability cluster but not to a distributed high-availability cluster. - While promoting a replica to a cluster, you can't modify the **Provider** and **Region** fields and the **Database Type** section or enable read-only workloads. 1. Select **Promote Replica**. From 915f86a4bbf3864cce2a9f4dd7da571a291e7fa2 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 12:32:25 -0400 Subject: [PATCH 074/223] updated links --- src/pages/index.js | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/src/pages/index.js b/src/pages/index.js index 8358dcdc884..89f663535ac 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -95,10 +95,7 @@ const Page = () => (

- + Find the EPAS content you're looking for

@@ -114,7 +111,7 @@ const Page = () => (

- + Find out more →

From 83760420bff9b1f1663b37affa9a5f79f5d26168 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 25 Aug 2023 14:03:55 -0400 Subject: [PATCH 075/223] Update alerts.mdx --- product_docs/docs/pem/9/monitoring_performance/alerts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/alerts.mdx b/product_docs/docs/pem/9/monitoring_performance/alerts.mdx index b61ffe029d7..d84e2b4ed4b 100644 --- a/product_docs/docs/pem/9/monitoring_performance/alerts.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/alerts.mdx @@ -62,7 +62,7 @@ Use the Quick Links toolbar to open dialog boxes and tabs for managing alerts: - Select **Copy Alerts** to open the Copy Alert Configuration dialog box and copy an alert definition. - Select **Alert Templates** to open the **Alert Template** tab and modify or create an alert template. -- Select **Email Templates** to open the **Email Template** dialog, and modify the default email template to customize an email notification. +- Select **Email Templates** to open the Email Template dialog box and modify the default email template to customize an email notification. - Select **Email Groups** to open the **Email Groups** tab and modify or create an email group. - Select **Webhooks** to open the **Webhooks** tab and create or manage the webhooks endpoints. - Select **Server Configurations** to open the Server Configuration dialog box and review or modify server configuration settings. From 463d846d32fb852db194e22d01ae5ade8242da93 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 25 Aug 2023 14:08:06 -0400 Subject: [PATCH 076/223] Update notifications.mdx --- .../docs/pem/9/monitoring_performance/notifications.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index 04ebaeec7a5..a0b726c4fc8 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -283,7 +283,7 @@ These are the default email templates that are customizable: - Job step - Job step (Database server) -If any of the default alert template is customized then a green tick mark is displayed against that template in the `Custom Template?` column. +If any of the default alert template is customized, then a green tick mark is displayed against that template in the `Custom Template?` column. Select the edit button to customize the email template: From e669898a7de46434147efcabf53de9732a8ff731 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 25 Aug 2023 14:11:18 -0400 Subject: [PATCH 077/223] Update notifications.mdx --- .../docs/pem/9/monitoring_performance/notifications.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index a0b726c4fc8..8e6ff214bdf 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -289,9 +289,9 @@ Select the edit button to customize the email template: ![Email Template Edit](../images/email_template_edit.png) -Edit the `Subject` and `Payload` fields, as needed, from the available list of placeholders. +From the available list of placeholders, edit the **Subject** and **Payload** fields, as needed. -Select the custom template and select the undo button at the top, to restore it as default template: +To restore it as the default template, select the custom template and select the undo button at the top: ![Email Template Restore](../images/email_template_restore.png) From 0ca72edc504bef7470732cca57d9724b61610331 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 10:14:21 -0400 Subject: [PATCH 078/223] OCL Connector: libpq requirement --- .../ocl_connector/15/installing/upgrading.mdx | 23 +++++++++++++++++++ .../15.2.0.4_ocl_release_notes.mdx | 3 ++- 2 files changed, 25 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/ocl_connector/15/installing/upgrading.mdx b/product_docs/docs/ocl_connector/15/installing/upgrading.mdx index 46baa8d506e..417679a100b 100644 --- a/product_docs/docs/ocl_connector/15/installing/upgrading.mdx +++ b/product_docs/docs/ocl_connector/15/installing/upgrading.mdx @@ -30,3 +30,26 @@ Where `` is the package manager used with your operating system | apt-get | Debian and Ubuntu | +## Upgrading libpq + +You may need to upgrade the EDB Postgres Advanced Server libpq library to a required version on the client machine where you installed EDB OCL Connector. Any new libpq version dependencies are listed in the release notes. If you need to upgrade libpq, run the appropriate command for your operating system. + +### For Ubuntu/Debian + +``` +sudo apt-get install edb-as15-libpq5 +``` + +### For RHEL and SLES + +``` +sudo install edb-as15-server-libs +``` + +Where `` is the package manager used with your operating system: + +| Package manager | Operating system | +| --------------- | -------------------------------- | +| dnf | RHEL 8/9 and derivatives | +| yum | RHEL 7 and derivatives, CentOS 7 | +| zypper | SLES | diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx index a401f116870..69544d6e9a2 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx @@ -10,4 +10,5 @@ New features, enhancements, bug fixes, and other changes in the EDB OCL Connecto | Bug fix | Fixed a regression whereby a spurious rollback/begin occurs after deallocating a statement. [Support ticket: #94735]| !!!Important - This version requires EDB Postgres Advanced Server 15.4 or later. + This version requires EDB Postgres Advanced Server libpq version 15.4 or later on the client machine where the EDB OCL Connector is installed. See [Upgrading libpq](../installing/upgrading/#upgrading-libpq). + From 3b7b59b11cc996005987616097fbbc3e73287baf Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 25 Aug 2023 14:21:00 -0400 Subject: [PATCH 079/223] Update reports.mdx --- product_docs/docs/pem/9/reports.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/product_docs/docs/pem/9/reports.mdx b/product_docs/docs/pem/9/reports.mdx index 0d2c3ef1c79..14f217dd99d 100644 --- a/product_docs/docs/pem/9/reports.mdx +++ b/product_docs/docs/pem/9/reports.mdx @@ -11,7 +11,7 @@ redirects: You can generate the System Configuration report and Core Usage report for all locally and remotely managed servers. To generate this report, select **Management > Reports**. -Reports has following options: +Reports has the following options: - Alert History Report (JSON) - System Configuration Report (JSON) @@ -23,23 +23,23 @@ Only superusers or the users with the pem_admin role can download the System Con Information in these reports shows the latest probe run time. -## Alert History Report +## Alert History report -The Alert History Report provides detailed information about the alerts history at the agent or server level in JSON format. +The Alert History report provides detailed information about the alerts history at the agent or server level in JSON format. -Go to `Management` menu, select `Reports` then select `Alert History Report`. A new dialogue box opens: +Select **Management > Reports > Alert History Report**. A dialog box opens: ![Alert History Report](../images/alert_history_report_general.png) -- **Agent/Server Name**— Select the agents and servers from the drop-down list. `Overall System Report` option is also available to generate a report for all the registered and active agents and servers. +- **Agent/Server Name** — Select the agents and servers from the list. The **Overall System Report** option is also available to generate a report for all the registered and active agents and servers. -- **Timeframe**— Select the required timeframe from the drop-down list. +- **Timeframe** — Select the required timeframe from the list. -- **Alert Types**— Select the alert types you wish to generate the alert history report for. +- **Alert Types** — Select the alert types you want to generate the alert history report for. -## System Configuration Report +## System Configuration report -The System Configuration Report provides detailed information about the PEM Agents group, PEM Server Directory group, and custom groups listed under the browser tree. These groups can contain Postgres Enterprise Manager, PEM agent, and database servers. You can download this report in HTML and JSON formats. +The System Configuration report provides detailed information about the PEM Agents group, PEM Server Directory group, and custom groups listed under the browser tree. These groups can contain Postgres Enterprise Manager, PEM agent, and database servers. You can download this report in HTML and JSON formats. The Postgres Enterprise Manager Summary provides details about: From f266cee94be0bac522c7eee728d9ae789ef56fbe Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 25 Aug 2023 14:36:45 -0400 Subject: [PATCH 080/223] Update 02_methods.mdx --- .../01_basic_object_concepts/02_methods.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx index 5a048e37fa7..4e7ba1654be 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx @@ -8,6 +8,6 @@ redirects: Methods are SPL procedures or functions defined in an object type. Methods are categorized into three general types: -- Member methods — Procedures or functions that operate in the context of an object instance. Member methods have access to and can change the attributes of the object instance on which they're operating. -- Static methods — Procedures or functions that operate independently of any particular object instance. Static methods don't have access to and can't change the attributes of an object instance. -- Constructor methods — Functions used to create an instance of an object type. A default constructor method is always provided when an object type is defined. +- **Member methods** — Procedures or functions that operate in the context of an object instance. Member methods have access to and can change the attributes of the object instance on which they're operating. +- **Static methods** — Procedures or functions that operate independently of any particular object instance. Static methods don't have access to and can't change the attributes of an object instance. +- **Constructor methods** — Functions used to create an instance of an object type. A default constructor method is always provided when an object type is defined. From d5440e896a4c136d168f6fc2705eafa17ef80db5 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 25 Aug 2023 14:37:46 -0400 Subject: [PATCH 081/223] Update 03_constructor_methods.mdx --- .../03_creating_object_types/03_constructor_methods.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx index 5b156e5b03d..3ce3180cc15 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx @@ -36,7 +36,7 @@ CONSTRUCTOR FUNCTION address The body of the default constructor sets each member to `NULL`. -To create a custom constructor, using the keyword constructor, declare the constructor function in the `CREATE TYPE` command and define the construction function in the `CREATE TYPE BODY` command. For example, you might want to create a custom constructor for the `address` type that computes the city and state given a `street_address` and `postal_code`: +To create a custom constructor, using the keyword constructor, declare the constructor function in the `CREATE TYPE` command, and define the construction function in the `CREATE TYPE BODY` command. For example, you might want to create a custom constructor for the `address` type that computes the city and state given a `street_address` and `postal_code`: ```sql CREATE TYPE address AS OBJECT From 1a4ccbf832bba2e99528bf7841e81f3f59f2896d Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 14:47:45 -0400 Subject: [PATCH 082/223] refining language --- .../15/03_libpq_compatibility.mdx | 28 ++++++++++++++++++- .../ocl_connector/15/installing/upgrading.mdx | 22 --------------- .../15.2.0.4_ocl_release_notes.mdx | 2 +- 3 files changed, 28 insertions(+), 24 deletions(-) diff --git a/product_docs/docs/ocl_connector/15/03_libpq_compatibility.mdx b/product_docs/docs/ocl_connector/15/03_libpq_compatibility.mdx index 078f6e096e6..2f5ea245c55 100644 --- a/product_docs/docs/ocl_connector/15/03_libpq_compatibility.mdx +++ b/product_docs/docs/ocl_connector/15/03_libpq_compatibility.mdx @@ -5,8 +5,34 @@ title: "libpq cross-version compatibility" -EDB OCL installation always uses the latest libpq. The different scenarios supported under libpq cross-version compatibility are as following: +EDB OCL installation always uses the latest libpq. The different scenarios supported under libpq cross-version compatibility are as following when upgrading to a new major release of EDB Postgres Advanced Server (EPAS): - If the latest libpq is installed on the machine, OCL uses it. - If the latest libpq isn't already installed, OCL installs it. It doesn't use the existing libpq of older versions even if it's installed. - If you upgrade the OCL version, then libpq is also upgraded to its latest version. + +If you are upgrading to a minor release, you need to manually upgrade libpq. See the following section for instructions. + +## Upgrading libpq for minor releases of EPAS + +For minor releases of EDB Postgres Advanced Server, you may need to upgrade libpq to a required version on the client machine where you installed EDB OCL Connector. (Any new libpq version dependencies are listed in the release notes.) If you need to upgrade libpq, run the appropriate command for your operating system. + +### For Ubuntu/Debian + +``` +sudo apt-get install edb-as15-libpq5 +``` + +### For RHEL and SLES + +``` +sudo install edb-as15-server-libs +``` + +Where `` is the package manager used with your operating system: + +| Package manager | Operating system | +| --------------- | -------------------------------- | +| dnf | RHEL 8/9 and derivatives | +| yum | RHEL 7 and derivatives, CentOS 7 | +| zypper | SLES | \ No newline at end of file diff --git a/product_docs/docs/ocl_connector/15/installing/upgrading.mdx b/product_docs/docs/ocl_connector/15/installing/upgrading.mdx index 417679a100b..376b5dbdcfa 100644 --- a/product_docs/docs/ocl_connector/15/installing/upgrading.mdx +++ b/product_docs/docs/ocl_connector/15/installing/upgrading.mdx @@ -30,26 +30,4 @@ Where `` is the package manager used with your operating system | apt-get | Debian and Ubuntu | -## Upgrading libpq -You may need to upgrade the EDB Postgres Advanced Server libpq library to a required version on the client machine where you installed EDB OCL Connector. Any new libpq version dependencies are listed in the release notes. If you need to upgrade libpq, run the appropriate command for your operating system. - -### For Ubuntu/Debian - -``` -sudo apt-get install edb-as15-libpq5 -``` - -### For RHEL and SLES - -``` -sudo install edb-as15-server-libs -``` - -Where `` is the package manager used with your operating system: - -| Package manager | Operating system | -| --------------- | -------------------------------- | -| dnf | RHEL 8/9 and derivatives | -| yum | RHEL 7 and derivatives, CentOS 7 | -| zypper | SLES | diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx index 69544d6e9a2..ecdef1079f4 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx @@ -10,5 +10,5 @@ New features, enhancements, bug fixes, and other changes in the EDB OCL Connecto | Bug fix | Fixed a regression whereby a spurious rollback/begin occurs after deallocating a statement. [Support ticket: #94735]| !!!Important - This version requires EDB Postgres Advanced Server libpq version 15.4 or later on the client machine where the EDB OCL Connector is installed. See [Upgrading libpq](../installing/upgrading/#upgrading-libpq). + This version requires EDB Postgres Advanced Server libpq version 15.4 or later on the client machine where the EDB OCL Connector is installed. See [Upgrading libpq for minor releases](../03_libpq_compatibility/#upgrading-libpq-for-minor-releases-of-epas). From e5c26577be39898868423562bdf17b3a13572746 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 15:12:54 -0400 Subject: [PATCH 083/223] PGD: fixing link and tweaking language --- product_docs/docs/pgd/5/quickstart/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/quickstart/index.mdx b/product_docs/docs/pgd/5/quickstart/index.mdx index 9101908990a..7bd143a9660 100644 --- a/product_docs/docs/pgd/5/quickstart/index.mdx +++ b/product_docs/docs/pgd/5/quickstart/index.mdx @@ -20,7 +20,7 @@ navigation: EDB Postgres Distributed (PGD) is a multi-master replicating implementation of Postgres designed for high performance and availability. You can create database clusters made up of many bidirectionally synchronizing database nodes. The clusters can have a number of proxy servers that direct your query traffic to the most available nodes, adding further resilience to your cluster configuration. !!! Note Fully managed BigAnimal - If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal Distributed High Availability clusters](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-preview). + If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal distributed high-availability clusters](/biganimal/latest/overview/02_high_availability/#distributed-high-availability-preview). PGD is very configurable. To quickly evaluate and deploy PGD, use this quick start. It'll get you up and running with a fully configured PGD cluster using the same tools that you'll use to deploy to production. This quick start includes: From 90ba836020d4acfabc9c5854fca31c86c32ffd51 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 25 Aug 2023 15:36:07 -0400 Subject: [PATCH 084/223] Edits to Commvault updates --- .../02-PartnerInformation.mdx | 2 +- .../03-SolutionSummary.mdx | 2 +- ...-ConfiguringCommvaultBackupandRecovery.mdx | 12 ++-- .../05-UsingCommvaultBackupandRecovery.mdx | 71 ++++++++++--------- .../06-CertificationEnvironment.mdx | 2 +- .../07-SupportandLogging.mdx | 4 +- 6 files changed, 49 insertions(+), 44 deletions(-) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx index 34a7b7cd7e0..a1ca60ece76 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx @@ -9,4 +9,4 @@ description: 'Details of the partner' | **Partner product** | Commvault Backup & Recovery | | **Website** | https://www.commvault.com/ | | **Version** | Commvault Backup & Recovery 11.32 | -| **Product description** | Wherever your data resides, ensure availability by way of a single interface with Commvault Backup & Recovery. It offers domprehensive workload coverage, files, apps, and databases, including EDB Postgres Advanced Server, EDB Postgres Extended Server and PostgreSQL, from a single extensible platform and user interface. Commvault Backup & Recovery provides a comprehensive backup and archiving solution for your trusted recovery, ransomware protection, and security. | +| **Product description** | Wherever your data resides, ensure availability by way of a single interface with Commvault Backup & Recovery. It offers comprehensive workload coverage, files, apps, and databases, including EDB Postgres Advanced Server, EDB Postgres Extended Server, and PostgreSQL, from a single extensible platform and user interface. Commvault Backup & Recovery provides a comprehensive backup and archiving solution for your trusted recovery, ransomware protection, and security. | diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx index 0839f8fc321..130c61bd9d6 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx @@ -6,6 +6,6 @@ Commvault enables your business to streamline management of its continuously evo Commvault PostgreSQL iDataAgent provides the flexibility to back up PostgreSQL, EDB Postgres Advanced Server, and EDB Postgres Extended Server databases in different modes and restore them when needed. You can perform a full/log backup or restore of database servers, individual databases, and archive logs at any time and have full control over the process. -Managing your data means knowing that it's protected and being able to effectively report on success or failure. Through an easy-to-use interface, you can quickly check on the progress of your jobs to ensure things are moving as expected. To keep you in the know, you can also use prebuilt reports either on demand or on a scheduled basis. +Managing your data means knowing that it's protected and being able to effectively report on success or failure. Through an easy-to-use interface, you can quickly check on the progress of your jobs to ensure things are moving as expected. To keep you in the know, you can also use prebuilt reports either on demand or on a scheduled basis. ![Commvault Architecture](Images/Final-SolutionSummaryImage.png) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx index db7372a2446..2d350d56b2b 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx @@ -5,13 +5,13 @@ redirects: - /partner_docs/CommVaultGuide/04-ConfiguringCommvaultBackupandRecovery/ --- -Implementing Commvault Backup & Recovery with an EDB Postgres Advanced Server, EDB Postgres Extended Server or PostgreSQL Server database requires the following components: +Implementing Commvault Backup & Recovery with an EDB Postgres Advanced Server, EDB Postgres Extended Server, or PostgreSQL Server database requires the following components: -- EDB Postgres Advanced Server, EDB Postgres Extended Server or PostgreSQL Server +- EDB Postgres Advanced Server, EDB Postgres Extended Server, or PostgreSQL Server - Commvault Backup & Recovery software !!! Note - We refer to the EDB Postgres Advanced Server, EDB Postgres Extended Server, and PostgreSQL Server products as Postgres distribution. The specific distribution type depends on your needs and preferences. + We refer to the EDB Postgres Advanced Server, EDB Postgres Extended Server, and PostgreSQL Server products as the Postgres distribution. The specific distribution type depends on your needs and preferences. ## Prerequisites @@ -25,7 +25,7 @@ Implementing Commvault Backup & Recovery with an EDB Postgres Advanced Server, E ### Set up a disk storage pool -1. From the machine where Commvault Backup & Recovery is installed, run the Core Setup wizard from the Commvault Backup & Recovery's Command Center. The wizard helps to set up a disk storage pool and to modify the server backup plan according to your requirements. +1. From the machine where Commvault Backup & Recovery is installed, run the Core Setup wizard from the Commvault Backup & Recovery Command Center. The wizard helps to set up a disk storage pool and to modify the server backup plan according to your requirements. 2. Set up storage pool/disk storage. From the Welcome page, select **Let's get started**. On the **Disk** tab, in the **Name** box, enter a name for the storage pool. 3. In the **MediaAgent** box, accept the default value. 4. For **Type**, select **Local**. @@ -47,7 +47,7 @@ Next, create a server backup plan in Core Setup. To create a server backup plan ### Install a client on a Postgres distribution database -1. From the Navigation pane of the Commvault Backup & Recovery's Command Center, select **Protect > Databases**. +1. From the Navigation pane of the Commvault Backup & Recovery Command Center, select **Protect > Databases**. 2. Select **Add server**. 3. Select the database type for the Postgres distribution database, which in this case is **PostgreSQL**. @@ -69,7 +69,7 @@ Next, create a server backup plan in Core Setup. To create a server backup plan ![Creating a Server Backup Plan in Core Setup](Images/ServerAdd6.png) -### Configure the Postgres distribution instances to backup and protect +### Configure the Postgres distribution instances to back up and protect 1. From the navigation pane, select **Protect > Databases > DB Instances**. 2. Select **Add instance**, and then select **PostgreSQL**. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index 876a5d237cf..5305d86d7ff 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -13,15 +13,15 @@ Commvault provides two methods of taking the backup from a Postgres distribution - FSBasedBackupSet backup and restore !!! Note - At this time there is a known issue with FSBased Incremental/PITR Restore that does not allow for proper restoration of the database using the defined process. See the known issues section of the guide for more information and workaround. + At this time, there's a known issue with FSBased Incremental/PITR Restore that doesn't allow for proper restoration of the database using the defined process. See [Known issues](#known-issues) for more information and workarounds. -### DumpBasedBackupSet Backup and Restore +### DumpBasedBackupSet backup and restore Dump-based backup uses the pg_dump utility to take the backup. -## Taking DumpBasedBackupSet backup +## Taking a DumpBasedBackupSet backup -1. Open the Commvault Backup & Recovery's Command Center. From the navigation pane, select **Protect > Databases**. +1. Open the Commvault Backup & Recovery Command Center. From the navigation pane, select **Protect > Databases**. ![Instances Page](Images/Dumpbackup1.png) @@ -39,7 +39,7 @@ Dump-based backup uses the pg_dump utility to take the backup. ![Backup Section](Images/Dumpbackup4.png) -6. in the Select Backup Level screen, select **Full**. +6. In the Select Backup Level screen, select **Full**. ![Backup Level Screen](Images/Dumpbackup5.png) @@ -51,7 +51,7 @@ Dump-based backup uses the pg_dump utility to take the backup. ![Backup Job](Images/Dumpbackup7.png) -## Restoring DumpBasedBackupSet backup +## Restoring a DumpBasedBackupSet backup You can use DumpBasedBackupSet to restore the individual databases. @@ -62,7 +62,7 @@ You can use DumpBasedBackupSet to restore the individual databases. ![Recovery Points Calendar](Images/Dumprestore1.png) 4. Select a date from the calendar, and then select **Restore**. -5. The Backup Content screen displays the databases to restore. Select the required database to restore or select all of them to restore all. +5. The Backup Content screen displays the databases to restore. Select the required database to restore, or select all of them to restore all. ![Backup Content Screen](Images/Dumprestore2.png) @@ -77,7 +77,7 @@ You can use DumpBasedBackupSet to restore the individual databases. ![Restore Job](Images/Dumprestore5.png) -8. When the Restore has completed successfully, log in to the Postgres distribution database and check that the restore operation recovered the data. This example connected to an EDB Postgres Advanced Server instance: +8. When the restore has completed successfully, log in to the Postgres distribution database and check that the restore operation recovered the data. This example connected to an EDB Postgres Advanced Server instance: ```bash edb=# @@ -158,34 +158,34 @@ epas13_test=# ``` -### FSBasedBackupSet Backup and Restore +### FSBasedBackupSet backup and restore A file system backup backs up data that resides on a Windows or UNIX computer. -## Taking FSBasedBackupSet Backup -1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to **Protect > Databases**. +## Taking a FSBasedBackupSet backup +1. Open the Commvault Backup & Recovery Command Center. From the navigation pane, go to **Protect > Databases**. -2. Click on the required instance. +2. Select the required instance. -3. In the **Backup sets** section, click on **FSBasedBackupSet** backup set. +3. In the **Backup sets** section, select the **FSBasedBackupSet** backup set. -4. In the **Database groups** section, click the database group that you want to back up. In this case it is **default**. +4. In the **Database groups** section, select the database group that you want to back up. In this case, it's **default**. -5. In the **Backup** section, click **Back up**. +5. In the **Backup** section, select **Back up**. -6. Choose between a Full or Incremental backup in the **Select Backup Level** screen, this example chose an incremental backup. +6. In the **Select Backup Level** screen, choose between a full or incremental backup. This example uses an incremental backup. ![Select FSBased Backup Type](Images/SelectFSBasedBackupType.png) -7. A job will be created to take the backup, which you can view by clicking on the **Job ID** for that backup. +7. A job is created to take the backup. View the job by selecting the **Job ID** for that backup. ![FSBased Backup Job](Images/FSBasedBackupJob.png) -8. When the job is complete, the information about the job can be found on the job's page. +8. When the job is complete, you can find the information about the job on the job's page. ![FSBased Backup Job Details](Images/FSBasedBackupJobDetails.png) -## Restoring FSBasedBackupSet Full Backup -Backed up data can be restored for a subclient or an entire backup set with either an in-place restore, out-of-place restore or for a Linux file server to a standalone file server. +## Restoring a FSBasedBackupSet full backup +You can restore backed-up data for a subclient or an entire backup set using either an in-place restore, out-of-place restore, or, for a Linux file server, to a standalone file server. 1. Ensure that your Postgres distribution instance is stopped. @@ -193,29 +193,29 @@ Backed up data can be restored for a subclient or an entire backup set with eith 3. From the Commvault navigation pane, go to **Protect > Databases**. -4. Click the instance you want to restore. +4. Select the instance you want to restore. 5. In the **Recovery Points** calender, select **FSBasedBackupSet**. -6. Select a date where a full FSBasedBackupSet was taken and click **Restore**. +6. Select a date when a full FSBasedBackupSet was taken and select **Restore**. -7. The **Backup Content** screen will display the databases to be restored, select the required database to restore or select all of them to restore all. +7. The Backup Content screen displays the databases to restore. Select the required database to restore, or select all of them to restore all. ![FSBased Backup Restore Databases](Images/FSBasedFullRestoreDatabases.png) -8. Click **Restore**. +8. Select **Restore**. -9. From the **Restore Options** screen, select where you want the restore to complete, in-place, out-of-place or restore to disk for a Linux server. +9. From the Restore Options screen, select where you want the restore to complete: in-place, out-of-place, or restore to disk for a Linux server. ![FSBased Backup Restore Details](Images/FSBasedFullRestoreOptions.png) -10. Select the **Destination Server** and **Destination Instance** and click on submit. +10. Select the **Destination Server** and **Destination Instance**, and select **Submit**. -11. A Job will be created to restore the backup. +11. A job is created to restore the backup. -12. When the Restore has completed successfully, Commvault will automatically start the server using the pg_ctl utility. +12. When the restore has completed successfully, Commvault starts the server using the pg_ctl utility. -13. You can check that the server was started successfully with a command like, `"C:\Program Files\edb\as15\bin\pg_ctl" -U enterprisedb status -D "C:\Program Files\edb\as15\data"` and it should return a message that the server is running. + You can check that the server was started successfully with a command like, `"C:\Program Files\edb\as15\bin\pg_ctl" -U enterprisedb status -D "C:\Program Files\edb\as15\data"`. It returns a message that the server is running. ```bash C:\Program Files\edb\as15>"C:\Program Files\edb\as15\bin\pg_ctl" -U enterprisedb status -D "C:\Program Files\edb\as15\data" @@ -223,9 +223,14 @@ pg_ctl: server is running (PID: 20896) C:/Program Files/edb/as15/bin/edb-postgres.exe "-D" "C:\Program Files\edb\as15\data" ``` -14. If you would like the server to be controlled by a Services utility you will need to stop it with the pg_ctl utility and start it again in your Services utility, for example Services(Local) in Windows or systemctl in UNIX. +14. If you want the server to be controlled by a Services utility, you need to stop it with the pg_ctl utility and start it again in your Services utility, for example, Services(Local) in Windows or systemctl in UNIX. + +15. After you start the service using your utility of choice, log in to your EDB database and check that the restore operation recovered the data. + +## Known issues + +FSBaseBackupSet Incremental or Point-In-Time(PITR) Restore has issues with PostgreSQL server, EDB Postgres Advanced Server, and EDB Postgres Extended versions 13 and later. The behavior is due to a change that was made in Postgres version 13. From the release notes, `Generate an error if recovery does not reach the specified recovery target`. While Commvault does provide a time target for the recovery, the recovery is performed entirely by Postgres, and Postgres doesn't know how to reach that time target. Therefore, it fails. This can happen when there are no transactions between backup jobs. -15. After you have started the service with your utility of choice, login to your EDB database and check that the restore operation recovered the data. +A workaround for this issue is to always introduce a transaction scenario, such as a create and drop database, before doing a log backup. Another workaround is to use `recovery_target_lsn` in the `postgresql.conf` file instead of using `recovery_target_time`. -## Known Issues -FSBaseBackupSet Incremental or Point-In-Time(PITR) Restore has issues with PostgreSQL server, EDB Postgres Advanced Server and EDB Postgres Extended versions 13 and onward. The behavior is due to a change that was made in Postgres version 13. From the release notes, `Generate an error if recovery does not reach the specified recovery target`. While Commvault does provide a time target for the recovery, the recovery is performed entirely by Postgres and Postgres does not know how to reach that time target, therefore it fails. This can happen when there are no transactions between backup jobs. A workaround for this solution is to always introduce a transaction scenario, such as a create and drop database, before doing a log backup. Another workaround is to use `recovery_target_lsn` in the postgresql.conf file instead of uisng `recovery_target_time`. Commvault is aware of this error on their side and is working on a fix. +Commvault is aware of this error and is working on a fix. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx index 772fe4e5b5c..237e72146d0 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx @@ -5,7 +5,7 @@ description: 'Overview of the certification environment' |   |   | | ----------- | ----------- | -| **Certification Test Date** | August 22, 2023 | +| **Certification test date** | August 22, 2023 | | **EDB Postgres Advanced Server** | 12, 13, 14, 15 | | **EDB Postgres Extended Server** | 12, 13 | | **Commvault Backup & Recovery** | 11.32 | diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx index bdc628d1ec6..65dec90fb94 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx @@ -37,9 +37,9 @@ You can find Commvault logs using either of these methods: - Gather some job-specific logs in the Commvault interface: - 1. Open Commvault Backup & Recovery's Command Center. From the navigation pane, go to **Jobs > Job History**. + 1. Open the Commvault Backup & Recovery Command Center. From the navigation pane, go to **Jobs > Job History**. - 2. Find the specific job you want to view logs for, and select `...` next to that job. + 2. Find the specific job you want to view logs for, and select **...** next to that job. 3. Select **View Logs**. From 5b82bc23a99b0ea8f0d7eee914c96774b002e6b8 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Sun, 27 Aug 2023 05:51:29 -0400 Subject: [PATCH 085/223] fixed left angle bracket --- .../ecpgplus_guide/installing_ecpgplus.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/15/application_programming/ecpgplus_guide/installing_ecpgplus.mdx b/product_docs/docs/epas/15/application_programming/ecpgplus_guide/installing_ecpgplus.mdx index 7570615a7ee..29605d0a77d 100644 --- a/product_docs/docs/epas/15/application_programming/ecpgplus_guide/installing_ecpgplus.mdx +++ b/product_docs/docs/epas/15/application_programming/ecpgplus_guide/installing_ecpgplus.mdx @@ -132,7 +132,7 @@ The command line options are: | -D <symbol> | Define a preprocessor symbol.

The -D keyword isn't supported when compiling in `PROC` mode. Instead, use the Oracle-style `‘DEFINE=’` clause. | | -h | Parse a header file. This option includes option `'-c'`. | | -i | Parse system. Include files as well. | -| -I <directory> | Search for `include` files. | +| -I <directory> | Search <directory> for `include` files. | | -o <outfile> | Write the result to <outfile>. | | -r <option> | Specify runtime behavior. The value of <option> can be:

`no_indicator` — Don't use indicators, but instead use special values to represent NULL values.

`prepare` — Prepare all statements before using them.

`questionmarks` — Allow use of a question mark as a placeholder.

`usebulk` — Enable bulk processing for `INSERT`, `UPDATE`, and `DELETE` statements that operate on host variable arrays. | | --regression | Run in regression testing mode. | From 8f1e612f3a6172cff0defc3426f6e3b7d127b5c4 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 28 Aug 2023 14:11:28 +0530 Subject: [PATCH 086/223] Edited as per review comments from Betsy --- .../9/monitoring_performance/notifications.mdx | 15 ++++----------- .../docs/pem/9/pem_rel_notes/930_rel_notes.mdx | 2 +- product_docs/docs/pem/9/reports.mdx | 4 +--- 3 files changed, 6 insertions(+), 15 deletions(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index 8e6ff214bdf..a282fd81d8e 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -268,7 +268,7 @@ After confirming that Nagios is configured correctly, restart the Nagios service ## Customizing email templates -Postgres Enterprise Manager monitors your system for conditions that require user attention and sends email notifications. Use the `Email Templates` to customize the email subject and the payload that the server sends if the current values deviate from the threshold values specified by an alert. +Postgres Enterprise Manager monitors your system for conditions that require user attention and sends email notifications. Use the **Email Templates** to customize the email subject and the payload that the server sends if the current values deviate from the threshold values specified by an alert. These are the default email templates that are customizable: @@ -283,15 +283,8 @@ These are the default email templates that are customizable: - Job step - Job step (Database server) -If any of the default alert template is customized, then a green tick mark is displayed against that template in the `Custom Template?` column. +To customize the email template, select the edit button next to the email template name. Edit the **Subject** and **Payload** fields, as needed from the available list of placeholders. After modifying the field values, select the **Save** in the lower-right corner. -Select the edit button to customize the email template: - -![Email Template Edit](../images/email_template_edit.png) - -From the available list of placeholders, edit the **Subject** and **Payload** fields, as needed. - -To restore it as the default template, select the custom template and select the undo button at the top: - -![Email Template Restore](../images/email_template_restore.png) +If any of the default email templates are customized, then a green tick mark is displayed for that template in the `Custom Template?` column on the **Email Templates** tab. +To restore the customized email template as the default template, select the custom template and select the undo button at the top on the **Email Templates** tab. diff --git a/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx index fe54a38d40a..c8012cd752b 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx @@ -15,5 +15,5 @@ New features, enhancements, bug fixes, and other changes in PEM 9.3.0 include: | Bug Fix | Added the `hostaddr` body parameter to the server REST API. | | Bug Fix | Fixed an issue by removing the newline character in the alert details from the payload of Webhook. | | Bug Fix | Added support to allow the Webhook endpoint registration without providing the client SSL certificates and key files or CA certificates using `allow_insecure_webhooks` parameter in the `agent.cfg` file.| -| Bug Fix | Fixed an issue related to the backup sizes displaying on the PEM's Barman dashboard. | +| Bug Fix | Fixed an issue related to the backup sizes displaying on the PEM Barman dashboard. | | Bug Fix | Fixed an issue with unformatted data while importing the audit logs. | \ No newline at end of file diff --git a/product_docs/docs/pem/9/reports.mdx b/product_docs/docs/pem/9/reports.mdx index 14f217dd99d..f81d03c01e7 100644 --- a/product_docs/docs/pem/9/reports.mdx +++ b/product_docs/docs/pem/9/reports.mdx @@ -27,9 +27,7 @@ Information in these reports shows the latest probe run time. The Alert History report provides detailed information about the alerts history at the agent or server level in JSON format. -Select **Management > Reports > Alert History Report**. A dialog box opens: - -![Alert History Report](../images/alert_history_report_general.png) +Select **Management > Reports > Alert History Report**. From the dialog box, select your options: - **Agent/Server Name** — Select the agents and servers from the list. The **Overall System Report** option is also available to generate a report for all the registered and active agents and servers. From 8739b919015a413d74153ce4a962d431cc8c8ce5 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Sat, 26 Aug 2023 13:43:57 +0100 Subject: [PATCH 087/223] Updates with final CVEs Signed-off-by: Dj Walker-Morgan --- .../security/advisories/cve20074639.mdx | 2 +- .../security/advisories/cve201910128.mdx | 2 +- .../security/advisories/cve202331043.mdx | 2 +- .../{cve2023xxxxx3.mdx => cve202341113.mdx} | 13 +- .../{cve2023xxxxx6.mdx => cve202341114.mdx} | 13 +- .../{cve2023xxxxx7.mdx => cve202341115.mdx} | 14 +- .../{cve2023xxxxx5.mdx => cve202341116.mdx} | 16 +- .../{cve2023xxxxx1.mdx => cve202341117.mdx} | 13 +- .../{cve2023xxxxx4.mdx => cve202341118.mdx} | 13 +- .../{cve2023xxxxx2.mdx => cve202341119.mdx} | 13 +- .../{cve2023xxxxx8.mdx => cve202341120.mdx} | 13 +- advocacy_docs/security/advisories/index.mdx | 145 +++++++++--------- advocacy_docs/security/index.mdx | 134 ++++++++-------- 13 files changed, 201 insertions(+), 192 deletions(-) rename advocacy_docs/security/advisories/{cve2023xxxxx3.mdx => cve202341113.mdx} (77%) rename advocacy_docs/security/advisories/{cve2023xxxxx6.mdx => cve202341114.mdx} (79%) rename advocacy_docs/security/advisories/{cve2023xxxxx7.mdx => cve202341115.mdx} (84%) rename advocacy_docs/security/advisories/{cve2023xxxxx5.mdx => cve202341116.mdx} (84%) rename advocacy_docs/security/advisories/{cve2023xxxxx1.mdx => cve202341117.mdx} (80%) rename advocacy_docs/security/advisories/{cve2023xxxxx4.mdx => cve202341118.mdx} (80%) rename advocacy_docs/security/advisories/{cve2023xxxxx2.mdx => cve202341119.mdx} (78%) rename advocacy_docs/security/advisories/{cve2023xxxxx8.mdx => cve202341120.mdx} (82%) diff --git a/advocacy_docs/security/advisories/cve20074639.mdx b/advocacy_docs/security/advisories/cve20074639.mdx index c6bcadfe967..87c6c3bb631 100644 --- a/advocacy_docs/security/advisories/cve20074639.mdx +++ b/advocacy_docs/security/advisories/cve20074639.mdx @@ -1,5 +1,5 @@ --- -title: EDB Advanced Server 8.2 improperly handles debugging function calls +title: CVE-2007-4639 - EDB Advanced Server 8.2 improperly handles debugging function calls navTitle: CVE-2007-4639 --- diff --git a/advocacy_docs/security/advisories/cve201910128.mdx b/advocacy_docs/security/advisories/cve201910128.mdx index c1d8586d38f..1625190c580 100644 --- a/advocacy_docs/security/advisories/cve201910128.mdx +++ b/advocacy_docs/security/advisories/cve201910128.mdx @@ -1,5 +1,5 @@ --- -title: EDB supplied PostgreSQL inherits ACL for installation directory +title: CVE-2019-10128 - EDB supplied PostgreSQL inherits ACL for installation directory navTitle: CVE-2019-10128 --- diff --git a/advocacy_docs/security/advisories/cve202331043.mdx b/advocacy_docs/security/advisories/cve202331043.mdx index 5bae8969359..bbdace27441 100644 --- a/advocacy_docs/security/advisories/cve202331043.mdx +++ b/advocacy_docs/security/advisories/cve202331043.mdx @@ -1,5 +1,5 @@ --- -title: EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0 +title: CVE-2023-31043 - EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0 navTitle: CVE-2023-31043 --- diff --git a/advocacy_docs/security/advisories/cve2023xxxxx3.mdx b/advocacy_docs/security/advisories/cve202341113.mdx similarity index 77% rename from advocacy_docs/security/advisories/cve2023xxxxx3.mdx rename to advocacy_docs/security/advisories/cve202341113.mdx index 9eeffc826cb..e9c67e52f30 100644 --- a/advocacy_docs/security/advisories/cve2023xxxxx3.mdx +++ b/advocacy_docs/security/advisories/cve202341113.mdx @@ -1,19 +1,19 @@ --- -title: EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() -navTitle: CVE-2023-XXXXX-3 +title: CVE-2023-41113 - EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() +navTitle: CVE-2023-41113 --- First Published: 2023/08/21 -Last Updated: 2023/08/21 +Last Updated: 2023/08/28 ## Summary -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 allow an authenticated user to to obtain information about whether certain files exist on disk, what errors if any occur when attempting to read them, and some limited information about their contents regardless of permissions. This can occur when a superuser has configured one or more directories for filesystem access via CREATE DIRECTORY and adopted certain non-default settings for log_line_prefix and log_connections. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It allows an authenticated user to to obtain information about whether certain files exist on disk, what errors if any occur when attempting to read them, and some limited information about their contents (regardless of permissions). This can occur when a superuser has configured one or more directories for filesystem access via CREATE DIRECTORY and adopted certain non-default settings for log_line_prefix and log_connections. ## Vulnerability details -CVE-ID: CVE-2023-XXXXX-3 +CVE-ID: CVE-2023-41113 CVSS Base Score: 4.3 @@ -45,7 +45,7 @@ Impacted users must upgrade to a fixed version of EPAS and then patch existing d | EPAS | All versions prior to 15.4.0 | Update to latest supported version
(at least [15.4.0](/epas/15/epas_rel_notes/epas15_4_0_rel_notes/)) !!! Note Update -No updates as of August 21st 2023 +No updates as of 28 August 2023 !!! !!! Warning Warning: @@ -71,6 +71,7 @@ EnterpriseDB ## Change history 21 August 2023: Original Copy Published +28 August 2023: Updated with assigned CVE number ## Disclaimer diff --git a/advocacy_docs/security/advisories/cve2023xxxxx6.mdx b/advocacy_docs/security/advisories/cve202341114.mdx similarity index 79% rename from advocacy_docs/security/advisories/cve2023xxxxx6.mdx rename to advocacy_docs/security/advisories/cve202341114.mdx index 4d12fc9d97b..8fb4c6a9d37 100644 --- a/advocacy_docs/security/advisories/cve2023xxxxx6.mdx +++ b/advocacy_docs/security/advisories/cve202341114.mdx @@ -1,19 +1,19 @@ --- -title: EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL -navTitle: CVE-2023-XXXXX-6 +title: CVE-2023-41114 - EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL +navTitle: CVE-2023-41114 --- First Published: 2023/08/21 -Last Updated: 2023/08/21 +Last Updated: 2023/08/28 ## Summary -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 contain the functions get_url_as_text and get_url_as_bytea. These functions are publicly executable, thus permitting an authenticated user to read any file from the local filesystem or remote system regardless of that user's permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contains the functions get_url_as_text and get_url_as_bytea that are publicly executable, thus permitting an authenticated user to read any file from the local filesystem or remote system regardless of that user's permissions. ## Vulnerability details -CVE-ID: CVE-2023-XXXXX-6 +CVE-ID: CVE-2023-41114 CVSS Base Score: 6.5 @@ -43,7 +43,7 @@ EnterpriseDB Postgres Advanced Server (EPAS) | EPAS | All versions prior to 15.4.0 | Update to latest supported version
(at least [15.4.0](/epas/15/epas_rel_notes/epas15_4_0_rel_notes/)) !!! Note Update -No updates as of August 21st 2023 +No updates as of 28 August 2023 !!! !!! Warning Warning: @@ -69,6 +69,7 @@ EnterpriseDB ## Change history 21 August 2023: Original Copy Published +28 August 2023: Updated with assigned CVE number ## Disclaimer diff --git a/advocacy_docs/security/advisories/cve2023xxxxx7.mdx b/advocacy_docs/security/advisories/cve202341115.mdx similarity index 84% rename from advocacy_docs/security/advisories/cve2023xxxxx7.mdx rename to advocacy_docs/security/advisories/cve202341115.mdx index f4be16f2e63..43a171e6f74 100644 --- a/advocacy_docs/security/advisories/cve2023xxxxx7.mdx +++ b/advocacy_docs/security/advisories/cve202341115.mdx @@ -1,19 +1,19 @@ --- -title: EDB Postgres Advanced Server (EPAS) permission bypass for large objects -navTitle: CVE-2023-XXXXX-7 +title: CVE-2023-41115 - EDB Postgres Advanced Server (EPAS) permission bypass for large objects +navTitle: CVE-2023-41115 --- First Published: 2023/08/21 -Last Updated: 2023/08/21 +Last Updated: 2023/08/28 ## Summary -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0, using UTL_ENCODE allows an authenticated user to read any large object, regardless of that users permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. When using UTL_ENCODE, an authenticated user can read any large object, regardless of that user's permissions. ## Vulnerability details -CVE-ID: CVE-2023-XXXXX-7 +CVE-ID: CVE-2023-41115 CVSS Base Score: 6.5 @@ -45,7 +45,7 @@ Impacted users must upgrade to a fixed version of EPAS and then patch existing d | EPAS | All versions prior to 15.4.0 | Update to latest supported version
(at least [15.4.0](/epas/15/epas_rel_notes/epas15_4_0_rel_notes/)) !!! Note Update -No updates as of August 14th 2023 +No updates as of 28 August 2023 !!! !!! Warning Warning: @@ -71,6 +71,8 @@ EnterpriseDB ## Change history 21 August 2023: Original Copy Published +28 August 2023: Updated with assigned CVE number + ## Disclaimer diff --git a/advocacy_docs/security/advisories/cve2023xxxxx5.mdx b/advocacy_docs/security/advisories/cve202341116.mdx similarity index 84% rename from advocacy_docs/security/advisories/cve2023xxxxx5.mdx rename to advocacy_docs/security/advisories/cve202341116.mdx index 66ae38b4c2d..2183c207db8 100644 --- a/advocacy_docs/security/advisories/cve2023xxxxx5.mdx +++ b/advocacy_docs/security/advisories/cve202341116.mdx @@ -1,19 +1,22 @@ --- -title: EDB Postgres Advanced Server (EPAS) permission bypass for materialized views -navTitle: CVE-2023-XXXXX-5 +title: CVE-2023-41116 - EDB Postgres Advanced Server (EPAS) permission bypass for materialized views +navTitle: CVE-2023-41116 --- First Published: 2023/08/21 -Last Updated: 2023/08/21 +Last Updated: 2023/08/28 ## Summary -All versions of EnterpriseDB Postgres Advanced Server (EPAS) up to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 using DBMS_MVIEW allows an authenticated user to refresh any materialized view, regardless of that user’s permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before +11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and +15.x before 15.4.0. It allows an authenticated user to refresh any materialized +view, regardless of that user's permissions. ## Vulnerability details -CVE-ID: CVE-2023-XXXXX-5 +CVE-ID: CVE-2023-41116 CVSS Base Score: 4.3 @@ -45,7 +48,7 @@ Impacted users must upgrade to a fixed version of EPAS and then patch existing d | EPAS | All versions prior to 15.4.0 | Update to latest supported version
(at least [15.4.0](/epas/15/epas_rel_notes/epas15_4_0_rel_notes/)) !!! Note Update -No updates as of August 21st 2023 +No updates as of 28 August 2023 !!! !!! Warning Warning: @@ -71,6 +74,7 @@ EnterpriseDB ## Change history 21 August 2023: Original Copy Published +28 August 2023: Updated with assigned CVE number ## Disclaimer diff --git a/advocacy_docs/security/advisories/cve2023xxxxx1.mdx b/advocacy_docs/security/advisories/cve202341117.mdx similarity index 80% rename from advocacy_docs/security/advisories/cve2023xxxxx1.mdx rename to advocacy_docs/security/advisories/cve202341117.mdx index 869b2456e8b..956850f22f1 100644 --- a/advocacy_docs/security/advisories/cve2023xxxxx1.mdx +++ b/advocacy_docs/security/advisories/cve202341117.mdx @@ -1,19 +1,19 @@ --- -title: EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path -navTitle: CVE-2023-XXXXX-1 +title: CVE-2023-41117 - EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path +navTitle: CVE-2023-41117 --- First Published: 2023/08/21 -Last Updated: 2023/08/21 +Last Updated: 2023/08/28 ## Summary -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 contain packages, standalone packages and functions that run SECURITY DEFINER but are inadequately secured against search_path attacks. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contain packages, standalone packages, and functions that run SECURITY DEFINER but are inadequately secured against search_path attacks. ## Vulnerability details -CVE-ID: CVE-2023-XXXXX-1 +CVE-ID: CVE-2023-41117 CVSS Base Score: 8.8 @@ -43,7 +43,7 @@ EnterpriseDB Postgres Advanced Server (EPAS) | EPAS | All versions prior to 15.4.0 | Update to latest supported version
(at least [15.4.0](/epas/15/epas_rel_notes/epas15_4_0_rel_notes/)) !!! Note Update -No updates as of August 21st 2023 +No updates as of 28 August 2023 !!! !!! Warning Warning: @@ -68,6 +68,7 @@ Source: TBD ## Change history 21 August 2023: Original Copy Published +28 August 2023: Updated with assigned CVE number ## Disclaimer diff --git a/advocacy_docs/security/advisories/cve2023xxxxx4.mdx b/advocacy_docs/security/advisories/cve202341118.mdx similarity index 80% rename from advocacy_docs/security/advisories/cve2023xxxxx4.mdx rename to advocacy_docs/security/advisories/cve202341118.mdx index 8df45b62dfa..10947eb6eb8 100644 --- a/advocacy_docs/security/advisories/cve2023xxxxx4.mdx +++ b/advocacy_docs/security/advisories/cve202341118.mdx @@ -1,19 +1,19 @@ --- -title: EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass -navTitle: CVE-2023-XXXXX-4 +title: CVE-2023-41118 - EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass +navTitle: CVE-2023-41118 --- First Published: 2023/08/21 -Last Updated: 2023/08/21 +Last Updated: 2023/08/28 ## Summary -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 may allow an authenticated user to bypass authorization requirements and access underlying implementation functions. When a superuser has configured file locations using CREATE DIRECTORY, these functions allow users to take a wide range of actions, including read, write, copy, rename, and delete. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It may allow an authenticated user to bypass authorization requirements and access underlying implementation functions. When a superuser has configured file locations using CREATE DIRECTORY, these functions allow users to take a wide range of actions, including read, write, copy, rename, and delete. ## Vulnerability details -CVE-ID: CVE-2023-XXXXX-4 +CVE-ID: CVE-2023-41118 CVSS Base Score: 8.8 @@ -45,7 +45,7 @@ Impacted users must upgrade to a fixed version of EPAS and then patch existing d | EPAS | All versions prior to 15.4.0 | Update to latest supported version
(at least [15.4.0](/epas/15/epas_rel_notes/epas15_4_0_rel_notes/)) !!! Note Update -No updates as of August 21st 2023 +No updates as of 28 August 2023 !!! !!! Warning Warning: @@ -71,6 +71,7 @@ EnterpriseDB ## Change history 21 August 2023: Original Copy Published +28 August 2023: Updated with assigned CVE number ## Disclaimer diff --git a/advocacy_docs/security/advisories/cve2023xxxxx2.mdx b/advocacy_docs/security/advisories/cve202341119.mdx similarity index 78% rename from advocacy_docs/security/advisories/cve2023xxxxx2.mdx rename to advocacy_docs/security/advisories/cve202341119.mdx index db7df82c0a1..cb7a1141fa1 100644 --- a/advocacy_docs/security/advisories/cve2023xxxxx2.mdx +++ b/advocacy_docs/security/advisories/cve202341119.mdx @@ -1,19 +1,19 @@ --- -title: EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser -navTitle: CVE-2023-XXXXX-2 +title: CVE-2023-41119 - EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser +navTitle: CVE-2023-41119 --- First Published: 2023/08/21 -Last Updated: 2023/08/21 +Last Updated: 2023/08/28 ## Summary -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 contain the function _dbms_aq_move_to_exception_queue which may be used to elevate a user’s privileges to superuser. This function accepts the OID of a table, then accesses that table as the superuser using SELECT and DML commands. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contains the function _dbms_aq_move_to_exception_queue that may be used to elevate a user's privileges to superuser. This function accepts the OID of a table, and then accesses that table as the superuser by using SELECT and DML commands. ## Vulnerability details -CVE-ID: CVE-2023-XXXXX-2 +CVE-ID: CVE-2023-41119 CVSS Base Score: 8.8 @@ -43,7 +43,7 @@ EnterpriseDB Postgres Advanced Server (EPAS) | EPAS | All versions prior to 15.4.0 | Update to latest supported version
(at least [15.4.0](/epas/15/epas_rel_notes/epas15_4_0_rel_notes/)) !!! Note Update -No updates as of August 21st 2023 +No updates as of 28 August 2023 !!! !!! Warning Warning: @@ -69,6 +69,7 @@ EnterpriseDB ## Change history 21 August 2023: Original Copy Published +28 August 2023: Updated with assigned CVE number ## Disclaimer diff --git a/advocacy_docs/security/advisories/cve2023xxxxx8.mdx b/advocacy_docs/security/advisories/cve202341120.mdx similarity index 82% rename from advocacy_docs/security/advisories/cve2023xxxxx8.mdx rename to advocacy_docs/security/advisories/cve202341120.mdx index cc5af3eeada..36b0918f025 100644 --- a/advocacy_docs/security/advisories/cve2023xxxxx8.mdx +++ b/advocacy_docs/security/advisories/cve202341120.mdx @@ -1,19 +1,19 @@ --- -title: EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission -navTitle: CVE-2023-XXXXX-8 +title: CVE-2023-41120 - EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission +navTitle: CVE-2023-41120 --- First Published: 2023/08/21 -Last Updated: 2023/08/21 +Last Updated: 2023/08/28 ## Summary -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 permit an authenticated user to use DBMS_PROFILER to remove all accumulated profiling data on a system-wide basis, regardless of that user’s permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It permits an authenticated user to use DBMS_PROFILER to remove all accumulated profiling data on a system-wide basis, regardless of that user's permissions. ## Vulnerability details -CVE-ID: CVE-2023-XXXXX-8 +CVE-ID: CVE-2023-41120 CVSS Base Score: 6.5 @@ -45,7 +45,7 @@ Impacted users must upgrade to a fixed version of EPAS and then patch existing d | EPAS | All versions prior to 15.4.0 | Update to latest supported version
(at least [15.4.0](/epas/15/epas_rel_notes/epas15_4_0_rel_notes/)) !!! Note Update -No updates as of August 21st 2023 +No updates as of 28 August 2023 !!! !!! Warning Warning: @@ -70,6 +70,7 @@ EnterpriseDB ## Change history 21 August 2023: Original Copy Published +28 August 2023: Updated with assigned CVE number ## Disclaimer diff --git a/advocacy_docs/security/advisories/index.mdx b/advocacy_docs/security/advisories/index.mdx index 36d55754a2e..baf3c369dd8 100644 --- a/advocacy_docs/security/advisories/index.mdx +++ b/advocacy_docs/security/advisories/index.mdx @@ -5,158 +5,153 @@ iconName: Security hideKBLink: true hideToC: false navigation: -- cve2023xxxxx8 -- cve2023xxxxx7 -- cve2023xxxxx6 -- cve2023xxxxx5 -- cve2023xxxxx4 -- cve2023xxxxx3 -- cve2023xxxxx2 -- cve2023xxxxx1 +- cve202341120 +- cve202341119 +- cve202341118 +- cve202341117 +- cve202341116 +- cve202341115 +- cve202341114 +- cve202341113 - cve202331043 - cve201910128 - cve20074639 --- -!!! Note -Advisories with numbers in the format `CVE-YYYY-XXXXX-n` are submitted and pending full number assignment. -!!! - ## Updated 2023 -
-

CVE-2023-XXXXX-1

+ + + - +Read More... + - - - - - +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It may allow an authenticated user to bypass authorization requirements and access underlying implementation functions. When a superuser has configured file locations using CREATE DIRECTORY, these functions allow users to take a wide range of actions, including read, write, copy, rename, and delete. +
+Read More... + +Read More... + + + +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It allows an authenticated user to to obtain information about whether certain files exist on disk, what errors if any occur when attempting to read them, and some limited information about their contents (regardless of permissions). This can occur when a superuser has configured one or more directories for filesystem access via CREATE DIRECTORY and adopted certain non-default settings for log_line_prefix and log_connections. +
+Read More... + + +
+

CVE-2023-41120

-  Read Advisory -  Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

+  Read Advisory +  Updated: 2023/08/28 +

EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission +

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 contain packages, standalone packages and functions that run SECURITY DEFINER but are inadequately secured against search_path attacks. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It permits an authenticated user to use DBMS_PROFILER to remove all accumulated profiling data on a system-wide basis, regardless of that user's permissions.
-Read More... -
-
-

CVE-2023-XXXXX-2

+

CVE-2023-41119

-  Read Advisory -  Updated: 2023/08/21 +  Read Advisory +  Updated: 2023/08/28

EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser

All EnterpriseDB Postgres Advanced Server (EPAS) versions prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 contain the function _dbms_aq_move_to_exception_queue which may be used to elevate a user’s privileges to superuser. This function accepts the OID of a table, then accesses that table as the superuser using SELECT and DML commands. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contains the function _dbms_aq_move_to_exception_queue that may be used to elevate a user's privileges to superuser. This function accepts the OID of a table, and then accesses that table as the superuser by using SELECT and DML commands.
-Read More... +Read More...
-

CVE-2023-XXXXX-3

+

CVE-2023-41118

-  Read Advisory -  Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() +  Read Advisory +  Updated: 2023/08/2128 +

EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
- +
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 allow an authenticated user to to obtain information about whether certain files exist on disk, what errors if any occur when attempting to read them, and some limited information about their contents regardless of permissions. This can occur when a superuser has configured one or more directories for filesystem access via CREATE DIRECTORY and adopted certain non-default settings for log_line_prefix and log_connections.
-Read More... -
-
-

CVE-2023-XXXXX-4

+

CVE-2023-41117

-  Read Advisory -  Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 +  Read Advisory +  Updated: 2023/08/28 +

EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 may allow an authenticated user to bypass authorization requirements and access underlying implementation functions. When a superuser has configured file locations using CREATE DIRECTORY, these functions allow users to take a wide range of actions, including read, write, copy, rename, and delete. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contain packages, standalone packages, and functions that run SECURITY DEFINER but are inadequately secured against search_path attacks.
-Read More... -
-

CVE-2023-XXXXX-5

+

CVE-2023-41116

-  Read Advisory -  Updated: 2023/08/21 +  Read Advisory +  Updated: 2023/08/28

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) up to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 using DBMS_MVIEW allows an authenticated user to refresh any materialized view, regardless of that user’s permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It allows an authenticated user to refresh any materialized view, regardless of that user's permissions.
-Read More... +Read More...
-

CVE-2023-XXXXX-6

+

CVE-2023-41115

-  Read Advisory -  Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL +  Read Advisory +  Updated: 2023/08/28 +

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) up to 11.21,32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 contain the functions `get_url_as_text` and `get_url_as_bytea`. These functions are publicly executable, thus permitting an authenticated user to read any file from the local filesystem or remote system regardless of that user's permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. When using UTL_ENCODE, an authenticated user can read any large object, regardless of that user's permissions.
-Read More... +Read More...
-

CVE-2023-XXXXX-7

+

CVE-2023-41114

-  Read Advisory +  Read Advisory   Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views +

EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0, using UTL_ENCODE allows an authenticated user to read any large object, regardless of that users permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contains the functions get_url_as_text and get_url_as_bytea that are publicly executable, thus permitting an authenticated user to read any file from the local filesystem or remote system regardless of that user's permissions.
-Read More... +Read More...
-

CVE-2023-XXXXX-8

+

CVE-2023-41113

-  Read Advisory -  Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission +  Read Advisory +  Updated: 2023/08/28 +

EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory()

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 permit an authenticated user to use DBMS_PROFILER to remove all accumulated profiling data on a system-wide basis, regardless of that user’s permissions. -
-Read More... -

CVE-2023-31043

diff --git a/advocacy_docs/security/index.mdx b/advocacy_docs/security/index.mdx index 1780c405865..640abdeecc1 100644 --- a/advocacy_docs/security/index.mdx +++ b/advocacy_docs/security/index.mdx @@ -23,143 +23,145 @@ This policy outlines how EnterpriseDB handles disclosures related to suspected v ## Most Recent Advisories -!!! Note -Advisories with numbers in the format `CVE-YYYY-XXXXX-n` are submitted and pending full number assignment. -!!! - -
-

CVE-2023-XXXXX-1

+ + - +Read More... + - - - - - +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It may allow an authenticated user to bypass authorization requirements and access underlying implementation functions. When a superuser has configured file locations using CREATE DIRECTORY, these functions allow users to take a wide range of actions, including read, write, copy, rename, and delete. +
+Read More... + +Read More... + + + + + + + + + + + + +Read More... + +
+

CVE-2023-41120

-  Read Advisory -  Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

+  Read Advisory +  Updated: 2023/08/28 +

EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission +

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 contain packages, standalone packages and functions that run SECURITY DEFINER but are inadequately secured against search_path attacks. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It permits an authenticated user to use DBMS_PROFILER to remove all accumulated profiling data on a system-wide basis, regardless of that user's permissions.
-Read More... -
-
-

CVE-2023-XXXXX-2

+

CVE-2023-41119

-  Read Advisory -  Updated: 2023/08/21 +  Read Advisory +  Updated: 2023/08/28

EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser

All EnterpriseDB Postgres Advanced Server (EPAS) versions prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 contain the function _dbms_aq_move_to_exception_queue which may be used to elevate a user’s privileges to superuser. This function accepts the OID of a table, then accesses that table as the superuser using SELECT and DML commands. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contains the function _dbms_aq_move_to_exception_queue that may be used to elevate a user's privileges to superuser. This function accepts the OID of a table, and then accesses that table as the superuser by using SELECT and DML commands.
-Read More... +Read More...
-

CVE-2023-XXXXX-3

+

CVE-2023-41118

-  Read Advisory -  Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() +  Read Advisory +  Updated: 2023/08/2128 +

EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
- +
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 allow an authenticated user to to obtain information about whether certain files exist on disk, what errors if any occur when attempting to read them, and some limited information about their contents regardless of permissions. This can occur when a superuser has configured one or more directories for filesystem access via CREATE DIRECTORY and adopted certain non-default settings for log_line_prefix and log_connections.
-Read More... -
-
-

CVE-2023-XXXXX-4

+

CVE-2023-41117

-  Read Advisory -  Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 +  Read Advisory +  Updated: 2023/08/28 +

EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 may allow an authenticated user to bypass authorization requirements and access underlying implementation functions. When a superuser has configured file locations using CREATE DIRECTORY, these functions allow users to take a wide range of actions, including read, write, copy, rename, and delete. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contain packages, standalone packages, and functions that run SECURITY DEFINER but are inadequately secured against search_path attacks.
-Read More... -
-

CVE-2023-XXXXX-5

+

CVE-2023-41116

-  Read Advisory -  Updated: 2023/08/21 +  Read Advisory +  Updated: 2023/08/28

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) up to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 using DBMS_MVIEW allows an authenticated user to refresh any materialized view, regardless of that user’s permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It allows an authenticated user to refresh any materialized view, regardless of that user's permissions.
-Read More... +Read More...
-

CVE-2023-XXXXX-6

+

CVE-2023-41115

-  Read Advisory -  Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL +  Read Advisory +  Updated: 2023/08/28 +

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) up to 11.21,32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 contain the functions `get_url_as_text` and `get_url_as_bytea`. These functions are publicly executable, thus permitting an authenticated user to read any file from the local filesystem or remote system regardless of that user's permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. When using UTL_ENCODE, an authenticated user can read any large object, regardless of that user's permissions.
-Read More... +Read More...
-

CVE-2023-XXXXX-7

+

CVE-2023-41114

-  Read Advisory -  Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views +  Read Advisory +  Updated: 2023/08/28 +

EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0, using UTL_ENCODE allows an authenticated user to read any large object, regardless of that users permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contains the functions get_url_as_text and get_url_as_bytea that are publicly executable, thus permitting an authenticated user to read any file from the local filesystem or remote system regardless of that user's permissions.
-Read More... +Read More...
-

CVE-2023-XXXXX-8

+

CVE-2023-41113

-  Read Advisory +  Read Advisory   Updated: 2023/08/21 -

EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission +

EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory()

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  -All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0 and 15.4.0 permit an authenticated user to use DBMS_PROFILER to remove all accumulated profiling data on a system-wide basis, regardless of that user’s permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It allows an authenticated user to to obtain information about whether certain files exist on disk, what errors if any occur when attempting to read them, and some limited information about their contents (regardless of permissions). This can occur when a superuser has configured one or more directories for filesystem access via CREATE DIRECTORY and adopted certain non-default settings for log_line_prefix and log_connections.
-Read More... -

CVE-2023-31043

From dcf5658fd0c1ff168eccf286347f1235df764c9a Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 28 Aug 2023 06:40:18 -0400 Subject: [PATCH 088/223] Replication Server: fixing links --- .../eprs/7/installing/upgrading_replication_server/index.mdx | 2 +- .../installing/upgrading_replication_server/upgrading_linux.mdx | 2 +- .../upgrading_with_gui_installer.mdx | 2 +- .../upgrading_with_xdb_rpm_package.mdx | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx index 48eb227facf..f0e949a0905 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx @@ -21,6 +21,6 @@ For more details on upgrading Replication Server, see: - [Upgrading from a Replication Server 7.x installation on Linux](upgrading_linux) - [Upgrading with the graphical user interface installer](upgrading_with_gui_installer) -After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it (for Linux) or rename the driver (for Windows). See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. +After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it (for Linux) or rename the driver (for Windows). See [Installing a JDBC driver](../installing_jdbc_driver/) for more information. diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx index 988eaf4f128..5c7febc4aa4 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx @@ -16,5 +16,5 @@ If you have an existing Replication Server 7.x installation on Linux, you can us If you are upgrading from a Replication Server 6.2 installation on Linux, see [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) for details. -After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. +After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](../installing_jdbc_driver/) for more information. diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx index d15969f4d99..fb9f1dc6f0f 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx @@ -47,7 +47,7 @@ You can upgrade to Replication Server 7 using the graphical user interface insta If you don't need to adjust the port numbers, register the publication server and subscription server with the Replication Server console as described in [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). The existing replication systems appear in the replication tree of the Replication Server Console. -After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink (for Linux) to it or rename the driver (for Windows). See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. +After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink (for Linux) to it or rename the driver (for Windows). See [Installing a JDBC driver](../installing_jdbc_driver/) for more information. You are now ready to use Replication Server 7 to create new replication systems and manage existing ones. diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx index 97c6a720728..73387b79b40 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx @@ -183,6 +183,6 @@ If you're using Replication Server 6.2.x that was installed using the Replicatio If you don't need to adjust the port numbers, register the publication server and subscription server with the Replication Server console as described in [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server)). The existing replication systems appear in the replication tree of the Replication Server console. -After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. +After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](../installing_jdbc_driver/) for more information. You are now ready to use Replication Server 7 to create new replication systems and manage existing ones. From d9a6f6e57b9d575d84c449836ae340b3cf5c3e7a Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 28 Aug 2023 10:05:44 -0400 Subject: [PATCH 089/223] Added PGE 15.4 rel notes --- product_docs/docs/pge/15/release_notes/index.mdx | 2 ++ .../docs/pge/15/release_notes/rel_notes15.4.mdx | 14 ++++++++++++++ 2 files changed, 16 insertions(+) create mode 100644 product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx diff --git a/product_docs/docs/pge/15/release_notes/index.mdx b/product_docs/docs/pge/15/release_notes/index.mdx index 0d513be5602..82131a33b20 100644 --- a/product_docs/docs/pge/15/release_notes/index.mdx +++ b/product_docs/docs/pge/15/release_notes/index.mdx @@ -1,6 +1,7 @@ --- title: "Release notes" navigation: + - rel_notes15.4 - rel_notes15.3 - rel_notes15.2 --- @@ -10,6 +11,7 @@ cover what was new in each release. | Version | Release date | | ------------------------ | ------------ | +| [15.4](rel_notes15.4) | 21 Aug 2023 | | [15.3](rel_notes15.3) | 11 May 2023 | | [15.2](rel_notes15.2) | 14 Feb 2023 | diff --git a/product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx b/product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx new file mode 100644 index 00000000000..f26c12e7833 --- /dev/null +++ b/product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx @@ -0,0 +1,14 @@ +--- +title: "EDB Postgres Extended Server version 15.4" +navTitle: Version 15.4 +--- + +New features, enhancements, bug fixes, and other changes in EDB Postgres Extended Server 15.2 include: + +| Type | Description | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Upstream merge | Merged with community PostgreSQL 15.4. See the [PostgreSQL 15 Release Notes](https://www.postgresql.org/docs/15/release-15-4.html) for more information. | +| Bug fix | Fixed a memory leak experienced when using EDB Postgres Distributed (PGD) with Transparent Data Encryption (TDE). [Support issue: #93936] | + + + From 4b1740b5d106923d2861211d8004d4eff82e8850 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 28 Aug 2023 10:06:22 -0400 Subject: [PATCH 090/223] updates to EPAS 15.4 rel notes --- .../epas_rel_notes/epas15_4_0_rel_notes.mdx | 43 ++++++++++--------- 1 file changed, 23 insertions(+), 20 deletions(-) diff --git a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx index 524d5d631c0..9a03d92300c 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx @@ -9,26 +9,29 @@ Once you have upgraded to this version of EDB Postgres Advanced Server, you will #### EDB Postgres Advanced Server 15.4.0 includes the following enhancements and bug fixes: -| Type | Description | Addresses                | -| -------------- | -------------------------------------------------------------------------------------------------------------------------------------| --------------------- | -| Security fix | EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path. | [CVE-2023-XXXXX-1](/security/advisories/cve2023xxxxx1/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser. | [CVE-2023-XXXXX-2](/security/advisories/cve2023xxxxx2/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() | [CVE-2023-XXXXX-3](/security/advisories/cve2023xxxxx3/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass | [CVE-2023-XXXXX-4](/security/advisories/cve2023xxxxx4/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for materialized views | [CVE-2023-XXXXX-5](/security/advisories/cve2023xxxxx5/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL | [CVE-2023-XXXXX-6](/security/advisories/cve2023xxxxx6/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for large objects | [CVE-2023-XXXXX-7](/security/advisories/cve2023xxxxx7/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission | [CVE-2023-XXXXX-8](/security/advisories/cve2023xxxxx8/) | 11+ -| Bug fix | Allowed subtypes in INDEX BY clause of the packaged collection. | #1371 | 11+ -| Bug fix | Fixed %type resolution when pointing to a packaged type field. | #1243 | 11+ -| Bug fix | Profile: Fixed upgrade when `REUSE` constraints were `ENABLED`/`DISABLED`. | #92739 | 11+ -| Bug fix | Set correct collation for packaged cursor parameters. | #92739 | 11+ -| Bug fix | Rolled back autonomous transaction creating pg_temp in case of error. | #91614 | 11+ -| Bug fix | Added checks to ensure required WAL logging in EXCHANGE PARTITION command.| | 13+ -| Bug fix | Dumped/restored the sequences created for GENERATED AS IDENTITY constraint. | #90658 | 14+ -| Bug fix | Skipped updating the last DDL time for the parent table in CREATE INDEX. | #91270 | 14+ -| Bug fix | Removed existing package private procedure or function entries from the edb_last_ddl_time while replacing the package body. | | 14+ -| Bug fix | Fixed libpq to allow multiple PQprepare() calls under the same transaction. | #94735 | 14+ + +| Type | Description | Addresses                | | +| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | --- | +| Upstream merge | Merged with community PostgreSQL 15.4. See the [PostgreSQL 15 Release Notes](https://www.postgresql.org/docs/15/release-15-4.html) for more information. | | | +| Security fix | EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path. | [CVE-2023-XXXXX-1](/security/advisories/cve2023xxxxx1/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser. | [CVE-2023-XXXXX-2](/security/advisories/cve2023xxxxx2/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() | [CVE-2023-XXXXX-3](/security/advisories/cve2023xxxxx3/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass | [CVE-2023-XXXXX-4](/security/advisories/cve2023xxxxx4/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for materialized views | [CVE-2023-XXXXX-5](/security/advisories/cve2023xxxxx5/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL | [CVE-2023-XXXXX-6](/security/advisories/cve2023xxxxx6/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for large objects | [CVE-2023-XXXXX-7](/security/advisories/cve2023xxxxx7/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission | [CVE-2023-XXXXX-8](/security/advisories/cve2023xxxxx8/) | 11+ | +| Bug fix | Allowed subtypes in INDEX BY clause of the packaged collection. | #1371 | 11+ | +| Bug fix | Fixed %type resolution when pointing to a packaged type field. | #1243 | 11+ | +| Bug fix | Profile: Fixed upgrade when `REUSE` constraints were `ENABLED`/`DISABLED`. | #92739 | 11+ | +| Bug fix | Set correct collation for packaged cursor parameters. | #92739 | 11+ | +| Bug fix | Rolled back autonomous transaction creating pg_temp in case of error. | #91614 | 11+ | +| Bug fix | Added checks to ensure required WAL logging in EXCHANGE PARTITION command. | | 13+ | +| Bug fix | Dumped/restored the sequences created for GENERATED AS IDENTITY constraint. | #90658 | 14+ | +| Bug fix | Skipped updating the last DDL time for the parent table in CREATE INDEX. | #91270 | 14+ | +| Bug fix | Removed existing package private procedure or function entries from the edb_last_ddl_time while replacing the package body. | | 14+ | +| Bug fix | Fixed libpq to allow multiple PQprepare() calls under the same transaction. | #94735 | 14+ | +| Bug fix | Fixed a memory leak experienced when using EDB Postgres Distributed (PGD) with Transparent Data Encryption (TDE). | #93936 | | !!! Note Addresses Entries in the Addresses column are either CVE numbers or, if preceded by #, a customer case number. From 259e3f9216a930357227135bca7a1350ebd47020 Mon Sep 17 00:00:00 2001 From: aswright491 <36008570+aswright491@users.noreply.github.com> Date: Mon, 28 Aug 2023 13:35:47 -0400 Subject: [PATCH 091/223] Update index.mdx Added in link to migration handbook -- feel free to tweak any wording. --- product_docs/docs/biganimal/release/migration/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/migration/index.mdx b/product_docs/docs/biganimal/release/migration/index.mdx index b4a94fdd34d..6feb96644c8 100644 --- a/product_docs/docs/biganimal/release/migration/index.mdx +++ b/product_docs/docs/biganimal/release/migration/index.mdx @@ -6,7 +6,7 @@ EDB provides migration tools to bring data from Oracle, PostgresSQL, and EDB Pos ## Migrating from Oracle -[Migration Portal](/migration_portal/latest) provides the details for executing the migration steps using Migration Portal: +Review the EDB [Migration Handbook](/migrating/oracle/) for helpful considerations and information when migrating from Oracle. EDB also provides a tool, [Migration Portal](/migration_portal/latest), which provides the details for executing the migration steps: 1. [Schema extraction](/migration_portal/latest/04_mp_migrating_database/01_mp_schema_extraction/) 2. [Schema assessment](/migration_portal/latest/04_mp_migrating_database/02_mp_schema_assessment/) From 6d2481c825571b7f5ff41cd5bbf26e43bbb163ae Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Mon, 28 Aug 2023 14:49:48 -0400 Subject: [PATCH 092/223] Small changes to pr4517 edbplus --- .../41/02_release_notes/edbplus_41.2_rel_notes.mdx | 2 +- product_docs/docs/edb_plus/41/04_using_edb_plus.mdx | 4 ++-- product_docs/docs/edb_plus/41/06_command_summary.mdx | 8 ++++---- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx index a8f415a1b59..701148a1e35 100644 --- a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx +++ b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx @@ -6,5 +6,5 @@ New features, enhancements, bug fixes, and other changes in EDB\*Plus 41.2.0 inc | Type | Description | | ----------- | -------------------------------------------------------------- | -| Enhancement | The connection string syntax in EDB\*Plus now supports multi-host connectivity. When multiple hosts are specified, you can also use the `targetServerType` connection property and set it to `primary` to ensure that EDB\*Plus always establishes a connection with the active primary EDB Postgres Advanced Server (EPAS) database server. [Support ticket #92553] | +| Enhancement | The connection string syntax in EDB\*Plus now supports multi-host connectivity. When multiple hosts are specified, you can also use the `targetServerType` connection property and set it to `primary` to ensure that EDB\*Plus always establishes a connection with the active primary EDB Postgres Advanced Server database server. [Support ticket #92553] | | Bug fix | Fixed the issue whereby the ECHO command wasn't emitting the SQL statement in the spooled file when using EDB\*Plus in an interactive session. [Support ticket # 83580] | diff --git a/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx b/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx index b6902fe3f4c..561c258e9f3 100644 --- a/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx +++ b/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx @@ -40,7 +40,7 @@ edbplus [ -S[ILENT ] ] [ | /NOLOG ] [ @[. ] ] `port` is the port number receiving connections on the database server. The default is `5444`. !!! Note - If multiple hosts are specified, the driver will try to connect once to each of them in the order specified until the connection succeeds. If none succeed, a normal connection exception is thrown. Including the `targetServerType` connection property and setting it to `primary` ensures that the connection is only made to a primary database server. + If you specify multiple hosts, the driver tries to connect once to each of them in the order specified until the connection succeeds. If none succeed, a normal connection exception is thrown. Including the `targetServerType` connection property and setting it to `primary` ensures that the connection is made only to a primary database server. `dbname` is the name of the database to connect to. The default is `edb`. @@ -50,7 +50,7 @@ edbplus [ -S[ILENT ] ] [ | /NOLOG ] [ @[. ] ] edbplus.sh enterprisedb/password@[fe80::20c:29ff:fe7c:78b2]:5444/edb ``` - The `pg_hba.conf` file for the database server must contain an appropriate entry for the IPv6 connection. The following example shows an entry that allows all addresses: + The `pg_hba.conf` file for the database server must contain an appropriate entry for the IPv6 connection. This example shows an entry that allows all addresses: ```text # TYPE DATABASE USER ADDRESS METHOD diff --git a/product_docs/docs/edb_plus/41/06_command_summary.mdx b/product_docs/docs/edb_plus/41/06_command_summary.mdx index a43cfdfe2d2..10348cfde1c 100644 --- a/product_docs/docs/edb_plus/41/06_command_summary.mdx +++ b/product_docs/docs/edb_plus/41/06_command_summary.mdx @@ -298,9 +298,9 @@ CON[NECT] [/][@{ | } ] Where: - `username` is a database user name with which to connect to the database. + `username` is a database username with which to connect to the database. - `password` is the password associated with the specified user name. If you don't provide a `password` but a password is required for authentication, a search is made for a password file, first in the home directory of the Linux operating system account invoking EDB\*Plus (or in the `%APPDATA%\postgresql\` directory for Windows) and then at the location specified by the `PGPASSFILE` environment variable. The password file is `.pgpass` on Linux hosts and `pgpass.conf` on Windows hosts. The following is an example on a Windows host: + `password` is the password associated with the specified username. If you don't provide a password, but a password is required for authentication, a search is made for a password file. The search looks first in the home directory of the Linux operating system account invoking EDB\*Plus (or in the `%APPDATA%\postgresql\` directory for Windows) and then at the location specified by the `PGPASSFILE` environment variable. The password file is `.pgpass` on Linux hosts and `pgpass.conf` on Windows hosts. The following is an example on a Windows host: ```text C:\Users\Administrator\AppData\Roaming\postgresql\pgpass.conf @@ -323,7 +323,7 @@ Disconnected from EnterpriseDB Database. Connected to EnterpriseDB 14.0.0 (localhost:5445/edb) AS smith ``` -In this session, the connection is changed to user name `enterprisedb`. The host defaults to the `localhost`, the port defaults to `5444` (which isn't the same as the port previously used), and the database defaults to `edb`. +In this session, the connection is changed to the username `enterprisedb`. The host defaults to the localhost, the port defaults to `5444` (which isn't the same as the port previously used), and the database defaults to `edb`. ```sql SQL> CONNECT enterprisedb/password @@ -331,7 +331,7 @@ Disconnected from EnterpriseDB Database. Connected to EnterpriseDB 14.0.0 (localhost:5444/edb) AS enterprisedb ``` -The following example illustrates connectivity for a multi-node cluster (one primary node and two secondary nodes) setup. The given multi-host `connectstring` syntax is used to establish a connection with the active primary database server. In this case, using `CONNECT` command, the connection is established with the primary database node on host `192.168.22.24` at port `5444`. +This example shows connectivity for a multi-node cluster (one primary node and two secondary nodes) setup. The given multi-host `connectstring` syntax is used to establish a connection with the active primary database server. In this case, using `CONNECT` command, the connection is established with the primary database node on host `192.168.22.24` at port `5444`. ```sql SQL> CONNECT enterprisedb/edb@192.168.22.24:5444,192.168.22.25:5445,192.168.22.26:5446/edb?targetServerType=primary From 2dc532d3e2ebe9315ea9e5bb64fa799f7376ae14 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 28 Aug 2023 15:00:59 -0400 Subject: [PATCH 093/223] made MP its own para and added a MTK link --- product_docs/docs/biganimal/release/migration/index.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/biganimal/release/migration/index.mdx b/product_docs/docs/biganimal/release/migration/index.mdx index 6feb96644c8..c3716ecd4df 100644 --- a/product_docs/docs/biganimal/release/migration/index.mdx +++ b/product_docs/docs/biganimal/release/migration/index.mdx @@ -6,14 +6,16 @@ EDB provides migration tools to bring data from Oracle, PostgresSQL, and EDB Pos ## Migrating from Oracle -Review the EDB [Migration Handbook](/migrating/oracle/) for helpful considerations and information when migrating from Oracle. EDB also provides a tool, [Migration Portal](/migration_portal/latest), which provides the details for executing the migration steps: +Review the EDB [Migration Handbook](/migrating/oracle/) for helpful considerations and information when migrating from Oracle. + +EDB also provides a tool, [Migration Portal](/migration_portal/latest), which provides the details for executing the migration steps: 1. [Schema extraction](/migration_portal/latest/04_mp_migrating_database/01_mp_schema_extraction/) 2. [Schema assessment](/migration_portal/latest/04_mp_migrating_database/02_mp_schema_assessment/) 3. [Schema migration](/migration_portal/latest/04_mp_migrating_database/03_mp_schema_migration/) 4. [Data migration](/migration_portal/latest/04_mp_migrating_database/04_mp_data_migration/) -You can also use the Migration Toolkit for the data migration step. This toolkit is a good option for smaller databases. +You can also use the [Migration Toolkit](/migration_toolkit/latest/) for the data migration step. This toolkit is a good option for smaller databases. ## Accessing remote Oracle servers from BigAnimal From 4c3cf97b85a837bd4053042f112b08d161fd4e72 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Mon, 28 Aug 2023 21:21:37 +0000 Subject: [PATCH 094/223] Remove a few conflicting redirects. Most of these I added :) --- .../templates/products/edb-odbc-connector/index.njk | 1 - install_template/templates/products/edb-pgbouncer/base.njk | 2 -- install_template/templates/products/edb-pgbouncer/index.njk | 2 ++ .../templates/products/failover-manager/index.njk | 1 - .../products/postgres-enterprise-manager-server/base.njk | 2 -- .../products/postgres-enterprise-manager-server/index.njk | 6 ++---- .../07_reference/ecpgplus_statements.mdx | 3 --- 7 files changed, 4 insertions(+), 13 deletions(-) diff --git a/install_template/templates/products/edb-odbc-connector/index.njk b/install_template/templates/products/edb-odbc-connector/index.njk index dabf910bef1..f741d70e5bf 100644 --- a/install_template/templates/products/edb-odbc-connector/index.njk +++ b/install_template/templates/products/edb-odbc-connector/index.njk @@ -12,7 +12,6 @@ redirects: - ../03_edb-odbc_overview/01_installing_edb-odbc - /odbc_connector/{{ product.version }}/03_installing_edb_odbc/ - /odbc_connector/{{ product.version }}/03_installing_edb_odbc/01_installing_linux/ - - /odbc_connector/{{ product.version }}/03_installing_edb_odbc/14_installing_windows/ - /odbc_connector/{{ product.version }}/03_installing_edb_odbc/01_installing_linux/07_odbc13_ubuntu20_deb10_x86/ - /odbc_connector/{{ product.version }}/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/12_odbc13_sles12_ppcle/ {% endblock frontmatter %} diff --git a/install_template/templates/products/edb-pgbouncer/base.njk b/install_template/templates/products/edb-pgbouncer/base.njk index 22565551ded..a940018ecc3 100644 --- a/install_template/templates/products/edb-pgbouncer/base.njk +++ b/install_template/templates/products/edb-pgbouncer/base.njk @@ -11,8 +11,6 @@ deployPath: pgbouncer/{{ product.version }}/installing/linux_{{platform.arch}}/pgbouncer_{{deploy.map_platform[platform.name]}}.mdx redirects: - /pgbouncer/{{ product.version }}/01_installation/install_on_linux/{{deploy.expand_arch[platform.arch]}}/pgbouncer_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace(r/_?64/g, "")}}.mdx - - /pgbouncer/{{ product.version }}/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/{{ product.version }}/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ {% endblock frontmatter %} diff --git a/install_template/templates/products/edb-pgbouncer/index.njk b/install_template/templates/products/edb-pgbouncer/index.njk index 77c2b3fd9e5..0e97a334961 100644 --- a/install_template/templates/products/edb-pgbouncer/index.njk +++ b/install_template/templates/products/edb-pgbouncer/index.njk @@ -12,6 +12,8 @@ redirects: - ../03_installing_pgbouncer_on_an_sles_host - ../01_installation - ../01_installation/install_on_linux/ + - /pgbouncer/{{ product.version }}/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ + - /pgbouncer/{{ product.version }}/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ {% endblock frontmatter %} {% block navigation %} - linux_x86_64 diff --git a/install_template/templates/products/failover-manager/index.njk b/install_template/templates/products/failover-manager/index.njk index 5c77253f707..4d64de47777 100644 --- a/install_template/templates/products/failover-manager/index.njk +++ b/install_template/templates/products/failover-manager/index.njk @@ -7,7 +7,6 @@ redirects: - ../efm_user/03_installing_efm - 13_initial_config - /efm/4/03_installing_efm/ - - /efm/4.0/efm_user/02_failover_manager_overview/01_prerequisites/ - /efm/4/03_installing_efm/x86_amd64/08_efm4_deb9_x86/ - /efm/4/03_installing_efm/02_efm4_other_linux8_x86/ - /efm/4/03_installing_efm/04_efm4_centos7_x86/ diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index 1139b0a8bbc..dc748eda2e5 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -14,8 +14,6 @@ redirects: - /pem/{{ product.version }}/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace(r/_?64/g, "")}}/ - /pem/{{ product.version }}/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace(r/_?64/g, "")}}/ - /pem/{{ product.version }}/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace(r/_?64/g, "")}}/ - - /pem/{{ product.version }}/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/{{ product.version }}/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ {% endblock frontmatter %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/index.njk b/install_template/templates/products/postgres-enterprise-manager-server/index.njk index 10fd2405331..9449cb3fd1d 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/index.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/index.njk @@ -12,10 +12,8 @@ redirects: - /pem/{{ product.version if product.version < 9 else "latest" }}/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/ - /pem/{{ product.version if product.version < 9 else "latest" }}/installing_pem_server/ - /pem/{{ product.version if product.version < 9 else "latest" }}/installing_pem_server/pem_server_inst_linux/ -- /pem/{{ product.version if product.version < 9 else "latest" }}/installing_pem_server/pem_server_inst_linux/ -- /pem/{{ product.version if product.version < 9 else "latest" }}/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/ -- /pem/{{ product.version if product.version < 9 else "latest" }}/installing_pem_server/pem_server_inst_windows/ -- /pem/{{ product.version if product.version < 9 else "latest" }}/installing_pem_server/prerequisites_for_installing_pem_server/ +- /pem/{{ product.version }}/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ +- /pem/{{ product.version }}/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ {% endblock frontmatter %} {% block navigation %} diff --git a/product_docs/docs/epas/15/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx index 4e1811f9467..ec4a5dcb04a 100644 --- a/product_docs/docs/epas/15/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx @@ -66,9 +66,6 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.100.html" - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.102.html" - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.101.html" -redirects: - - /epas/latest/ecpgplus_guide/07_reference/ #generated for docs/epas/reorg-role-use-case-mode - - ../../../application_programming/ecpgplus_guide/07_reference/ --- From 83fd5c40bab0a7c53c7e0d4f94a353ad728aaf75 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Mon, 28 Aug 2023 21:22:20 +0000 Subject: [PATCH 095/223] Generate installer files --- product_docs/docs/efm/4/installing/index.mdx | 1 - product_docs/docs/odbc_connector/13/installing/index.mdx | 1 - product_docs/docs/pem/8/installing/index.mdx | 6 ++---- .../docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx | 2 -- .../docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx | 2 -- .../docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx | 2 -- .../docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx | 2 -- .../docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx | 2 -- .../docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx | 2 -- .../docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx | 2 -- .../pem/8/installing/linux_x86_64/pem_other_linux_8.mdx | 2 -- .../pem/8/installing/linux_x86_64/pem_other_linux_9.mdx | 2 -- .../docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx | 2 -- .../docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx | 2 -- .../docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx | 2 -- .../docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx | 2 -- .../docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx | 2 -- .../docs/pem/8/installing/linux_x86_64/pem_ubuntu_18.mdx | 2 -- .../docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx | 2 -- .../docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx | 2 -- product_docs/docs/pem/9/installing/index.mdx | 6 ++---- .../docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx | 2 -- .../docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx | 2 -- .../docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx | 2 -- .../docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx | 2 -- .../docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx | 2 -- .../docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx | 2 -- .../docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx | 2 -- .../pem/9/installing/linux_x86_64/pem_other_linux_8.mdx | 2 -- .../pem/9/installing/linux_x86_64/pem_other_linux_9.mdx | 2 -- .../docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx | 2 -- .../docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx | 2 -- .../docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx | 2 -- .../docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx | 2 -- .../docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx | 2 -- .../docs/pem/9/installing/linux_x86_64/pem_ubuntu_18.mdx | 2 -- .../docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx | 2 -- .../docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx | 2 -- product_docs/docs/pgbouncer/1/installing/index.mdx | 2 ++ .../1/installing/linux_ppc64le/pgbouncer_rhel_8.mdx | 2 -- .../1/installing/linux_ppc64le/pgbouncer_rhel_9.mdx | 2 -- .../1/installing/linux_ppc64le/pgbouncer_sles_12.mdx | 2 -- .../1/installing/linux_ppc64le/pgbouncer_sles_15.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_centos_7.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_debian_10.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_debian_11.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_other_linux_8.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_other_linux_9.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_rhel_7.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_rhel_8.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_rhel_9.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_sles_12.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_sles_15.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_ubuntu_18.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_ubuntu_20.mdx | 2 -- .../1/installing/linux_x86_64/pgbouncer_ubuntu_22.mdx | 2 -- 56 files changed, 6 insertions(+), 112 deletions(-) diff --git a/product_docs/docs/efm/4/installing/index.mdx b/product_docs/docs/efm/4/installing/index.mdx index 69c668c58b8..908d757205f 100644 --- a/product_docs/docs/efm/4/installing/index.mdx +++ b/product_docs/docs/efm/4/installing/index.mdx @@ -11,7 +11,6 @@ redirects: - ../efm_user/03_installing_efm - 13_initial_config - /efm/4/03_installing_efm/ - - /efm/4.0/efm_user/02_failover_manager_overview/01_prerequisites/ - /efm/4/03_installing_efm/x86_amd64/08_efm4_deb9_x86/ - /efm/4/03_installing_efm/02_efm4_other_linux8_x86/ - /efm/4/03_installing_efm/04_efm4_centos7_x86/ diff --git a/product_docs/docs/odbc_connector/13/installing/index.mdx b/product_docs/docs/odbc_connector/13/installing/index.mdx index 46665b52e39..822069c7cad 100644 --- a/product_docs/docs/odbc_connector/13/installing/index.mdx +++ b/product_docs/docs/odbc_connector/13/installing/index.mdx @@ -10,7 +10,6 @@ redirects: - ../03_edb-odbc_overview/01_installing_edb-odbc - /odbc_connector/13/03_installing_edb_odbc/ - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ - - /odbc_connector/13/03_installing_edb_odbc/14_installing_windows/ - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/07_odbc13_ubuntu20_deb10_x86/ - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/12_odbc13_sles12_ppcle/ diff --git a/product_docs/docs/pem/8/installing/index.mdx b/product_docs/docs/pem/8/installing/index.mdx index cc4f62e1ff7..39625ef568d 100644 --- a/product_docs/docs/pem/8/installing/index.mdx +++ b/product_docs/docs/pem/8/installing/index.mdx @@ -11,10 +11,8 @@ redirects: - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/ - /pem/8/installing_pem_server/ - /pem/8/installing_pem_server/pem_server_inst_linux/ - - /pem/8/installing_pem_server/pem_server_inst_linux/ - - /pem/8/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/ - - /pem/8/installing_pem_server/pem_server_inst_windows/ - - /pem/8/installing_pem_server/prerequisites_for_installing_pem_server/ + - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ + - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ navigation: - prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx index 2954fa7420d..b3f840ce754 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel8_ppcle/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel8_ppcle/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel8_ppcle/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx index b5a1c8361af..559b1533294 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel9_ppcle/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel9_ppcle/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel9_ppcle/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx index cb1cc3ecae9..b6dfb9a2131 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_sles12_ppcle/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_sles12_ppcle/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_sles12_ppcle/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- !!! Note diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx index 6b8c7bc75ba..ebfa6a0afe6 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_sles15_ppcle/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_sles15_ppcle/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_sles15_ppcle/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- !!! Note diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx index f86ae70a1fe..e8d93c7f10a 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_centos7_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_centos7_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_centos7_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx index a7e5cdc3343..a0154d4672c 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_deb10_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_deb10_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb10_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx index f8e481ab671..376d1ed8678 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_deb11_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_deb11_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb11_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx index 2543ec0d33f..43009817530 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx @@ -12,8 +12,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_other_linux8_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_other_linux8_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_other_linux8_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx index ac12dfa0eb0..5415e049ae6 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx @@ -12,8 +12,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_other_linux9_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_other_linux9_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_other_linux9_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx index 0dca89ff010..a3376575db7 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel7_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel7_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel7_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx index e2f334a8819..4933c0eb673 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel8_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel8_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel8_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx index 61169163d8c..bc70cc9d94d 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel9_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel9_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel9_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx index b82c9d8dcef..6b81f0c92fb 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_sles12_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_sles12_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_sles12_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- !!! Note diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx index 77f2958477a..a1a8e5d47c4 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_sles15_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_sles15_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- !!! Note diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_18.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_18.mdx index 245a147b1f3..23f710a0f30 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_18.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_18.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_ubuntu18_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_ubuntu18_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu18_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx index c0b149e6835..c483d47fc3a 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_ubuntu20_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_ubuntu20_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu20_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx index 93c484e6d68..ae21bff5cb5 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx @@ -11,8 +11,6 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_ubuntu22_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_ubuntu22_x86/ - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu22_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/index.mdx b/product_docs/docs/pem/9/installing/index.mdx index 102ddf5859b..68168cac232 100644 --- a/product_docs/docs/pem/9/installing/index.mdx +++ b/product_docs/docs/pem/9/installing/index.mdx @@ -11,10 +11,8 @@ redirects: - /pem/latest/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/ - /pem/latest/installing_pem_server/ - /pem/latest/installing_pem_server/pem_server_inst_linux/ - - /pem/latest/installing_pem_server/pem_server_inst_linux/ - - /pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/ - - /pem/latest/installing_pem_server/pem_server_inst_windows/ - - /pem/latest/installing_pem_server/prerequisites_for_installing_pem_server/ + - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ + - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ navigation: - prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx index 15010186495..5bb7291718e 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel8_ppcle/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel8_ppcle/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel8_ppcle/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx index fdb53e2792d..b703600ed07 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel9_ppcle/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel9_ppcle/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel9_ppcle/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx index 611a6053641..be0456cfbdb 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_sles12_ppcle/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_sles12_ppcle/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_sles12_ppcle/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- !!! Note diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx index 1939ad416cb..42298c5aa22 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_sles15_ppcle/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_sles15_ppcle/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_sles15_ppcle/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- !!! Note diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx index db1eaf2e00e..7a9dbc8084a 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_centos7_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_centos7_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_centos7_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx index ee1f6f4cec0..6d503840d49 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_deb10_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_deb10_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb10_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx index dc11f912c93..cd181e97167 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_deb11_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_deb11_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb11_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx index dadd4cc0ccf..0f858ebf69a 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx @@ -12,8 +12,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_other_linux8_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_other_linux8_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_other_linux8_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx index def653b48af..0c84be7ed56 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx @@ -12,8 +12,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_other_linux9_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_other_linux9_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_other_linux9_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx index 493922d9c21..ce5050e7473 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel7_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel7_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel7_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx index ab08f624605..c17e2a189dd 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel8_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel8_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel8_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx index 6632df499df..0c48e0fe3ad 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel9_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel9_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel9_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx index bd839cf13b1..bfeb88058ac 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_sles12_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_sles12_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_sles12_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- !!! Note diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx index c3c5cccf5a9..dd7a7a09612 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_sles15_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_sles15_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- !!! Note diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_18.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_18.mdx index 83e10fc3333..50b2cca834b 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_18.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_18.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_ubuntu18_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_ubuntu18_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu18_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx index 80bf10367c4..94f4d591b49 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_ubuntu20_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_ubuntu20_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu20_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx index b06f1939453..58f86de0312 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx @@ -11,8 +11,6 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_ubuntu22_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_ubuntu22_x86/ - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu22_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/03_pem_server_sles15_x86/ - - /pem/9/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/04_pem_server_sles12_x86/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/index.mdx b/product_docs/docs/pgbouncer/1/installing/index.mdx index 48b3dbc03ec..4583671ac0f 100644 --- a/product_docs/docs/pgbouncer/1/installing/index.mdx +++ b/product_docs/docs/pgbouncer/1/installing/index.mdx @@ -11,6 +11,8 @@ redirects: - ../03_installing_pgbouncer_on_an_sles_host - ../01_installation - ../01_installation/install_on_linux/ + - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ + - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ navigation: - linux_x86_64 diff --git a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_8.mdx b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_8.mdx index fef7c052c73..f5a9b3381b5 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_8.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_8.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on RHEL 8 ppc64le redirects: - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_rhel8_ppcle - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_9.mdx b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_9.mdx index f86856ae73c..2cc997e8224 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_9.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_9.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on RHEL 9 ppc64le redirects: - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_rhel9_ppcle - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_12.mdx b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_12.mdx index ec38db3e14b..3dd802684ac 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_12.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_12.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on SLES 12 ppc64le redirects: - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_sles12_ppcle - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_15.mdx b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_15.mdx index df902a91c31..413a5d3e0b2 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_15.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_15.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on SLES 15 ppc64le redirects: - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_sles15_ppcle - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_centos_7.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_centos_7.mdx index 1e64adf784a..e0f96e36003 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_centos_7.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_centos_7.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on CentOS 7 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_centos7_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_10.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_10.mdx index 09a59ea7efc..a47083850e4 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_10.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_10.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on Debian 10 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_deb10_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_11.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_11.mdx index a4ca6c3f58c..772872c195d 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_11.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_11.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on Debian 11 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_deb11_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_8.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_8.mdx index 0a12fc2e65c..ab517586f63 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_8.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_8.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on AlmaLinux 8 or Rocky Linux 8 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_other_linux8_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_9.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_9.mdx index 821ca7a91c7..394ce1b8825 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_9.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_9.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on AlmaLinux 9 or Rocky Linux 9 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_other_linux9_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_7.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_7.mdx index 6c7b285d8ef..849a32c9176 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_7.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_7.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on RHEL 7 or OL 7 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel7_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_8.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_8.mdx index 6f76c41d65d..5b0672115df 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_8.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_8.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on RHEL 8 or OL 8 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel8_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_9.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_9.mdx index 252b18ce311..dd9da039b93 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_9.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_9.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on RHEL 9 or OL 9 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel9_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_12.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_12.mdx index 09af0f048bf..1a391ebfcda 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_12.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_12.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on SLES 12 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_sles12_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_15.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_15.mdx index 84aff31be51..21bd3c97d2b 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_15.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_15.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on SLES 15 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_sles15_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_18.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_18.mdx index f44aaa397c1..7b5c43a712a 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_18.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_18.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on Ubuntu 18.04 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_ubuntu18_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_20.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_20.mdx index ae0010efaa3..d9be77de9e5 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_20.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_20.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on Ubuntu 20.04 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_ubuntu20_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_22.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_22.mdx index 7ecb661ac78..c080c34c4ec 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_22.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_22.mdx @@ -7,8 +7,6 @@ title: Installing EDB pgBouncer on Ubuntu 22.04 x86_64 redirects: - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_ubuntu22_x86 - - /pgbouncer/1/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host/ - - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/ --- ## Prerequisites From b7e85a91e6846c792886a429708e2c0a02e21619 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Thu, 24 Aug 2023 05:01:09 +0000 Subject: [PATCH 096/223] 2nd attempt to eliminate client-side redirects This time with full rewriting of current version links to /latest/ --- gatsby-node.js | 49 ++++++++++++++++++---------------- src/components/layout.js | 1 + src/components/left-nav.js | 2 +- src/components/link.js | 25 +++++++++++++++--- src/components/prev-next.js | 2 +- src/constants/gatsby-utils.js | 50 +++++++++++++++++++++++------------ src/templates/doc.js | 10 +++---- src/templates/learn-doc.js | 2 ++ 8 files changed, 91 insertions(+), 50 deletions(-) diff --git a/gatsby-node.js b/gatsby-node.js index 23095d76204..f52094a00bc 100644 --- a/gatsby-node.js +++ b/gatsby-node.js @@ -294,29 +294,25 @@ exports.createPages = async ({ actions, graphql, reporter }) => { const { docType } = node.fields; - const isLatest = - docType === "doc" - ? productVersions[node.fields.product][0] === node.fields.version - : false; + const versions = + docType === "doc" ? productVersions[node.fields.product] || [] : []; // all versions for this path. // Null entries for versions that don't exist. Will try to match redirects to avoid this, but won't follow redirect chains // Canonical version is the first non-null in the list, e.g. pathVersions.filter((p) => !!p)[0] - const allPaths = [node.fields.path, ...(node.frontmatter?.redirects || [])]; - const pathVersions = (productVersions[node.fields.product] || []).map( - (v, i) => { - const versionPaths = allPaths.map((p) => replacePathVersion(p, v)); - const match = versionPaths.find((vp) => validPaths.has(vp)); - if (!match) return null; - return i === 0 ? replacePathVersion(match) : match; - }, - ); + const allPaths = [node.fields.path, ...(node.frontmatter.redirects || [])]; + const pathVersions = versions.map((v, i) => { + const versionPaths = allPaths.map((p) => replacePathVersion(p, v)); + const match = versionPaths.find((vp) => validPaths.has(vp)); + if (!match) return null; + return validPaths.get(match); + }); configureRedirects( node.fields.path, node.frontmatter.redirects, actions, - isLatest, + versions, pathVersions, ); @@ -330,7 +326,7 @@ exports.createPages = async ({ actions, graphql, reporter }) => { actions, ); } else if (docType === "advocacy") { - createAdvocacy(navTree, prevNext, node, learn, actions); + createAdvocacy(navTree, prevNext, node, productVersions, learn, actions); } } }; @@ -358,13 +354,13 @@ const createDoc = ( }); } - const isIndexPage = isPathAnIndexPage(doc.fileAbsolutePath); const docsRepoUrl = "https://github.com/EnterpriseDB/docs"; // don't encourage folks to edit on main - set the edit links to develop in production builds const branch = gitData.branch === "main" ? "develop" : gitData.branch; - const fileUrlSegment = - removeTrailingSlash(doc.fields.path) + - (isIndexPage ? "/index.mdx" : ".mdx"); + const isIndexPage = isPathAnIndexPage(doc.fileAbsolutePath); + const fileUrlSegment = doc.fileAbsolutePath + .split("/product_docs/docs") + .slice(1); const githubFileLink = `${docsRepoUrl}/blob/${gitData.sha}/product_docs/docs${fileUrlSegment}`; const githubFileHistoryLink = `${docsRepoUrl}/commits/${gitData.sha}/product_docs/docs${fileUrlSegment}`; const githubEditLink = `${docsRepoUrl}/edit/${branch}/product_docs/docs${fileUrlSegment}`; @@ -385,6 +381,7 @@ const createDoc = ( pagePath: path, navTree, prevNext, + productVersions, versions: productVersions[doc.fields.product], nodeId: doc.id, githubFileLink: githubFileHistoryLink, @@ -418,7 +415,14 @@ const createDoc = ( }); }; -const createAdvocacy = (navTree, prevNext, doc, learn, actions) => { +const createAdvocacy = ( + navTree, + prevNext, + doc, + productVersions, + learn, + actions, +) => { // configure legacy redirects configureLegacyRedirects({ toPath: doc.fields.path, @@ -437,9 +441,7 @@ const createAdvocacy = (navTree, prevNext, doc, learn, actions) => { // don't encourage folks to edit on main - set the edit links to develop in production builds const branch = gitData.branch === "main" ? "develop" : gitData.branch; const isIndexPage = isPathAnIndexPage(doc.fileAbsolutePath); - const fileUrlSegment = - removeTrailingSlash(doc.fields.path) + - (isIndexPage ? "/index.mdx" : ".mdx"); + const fileUrlSegment = doc.fileAbsolutePath.split("/advocacy_docs").slice(1); const githubFileLink = `${advocacyDocsRepoUrl}/blob/${gitData.sha}/advocacy_docs${fileUrlSegment}`; const githubFileHistoryLink = `${advocacyDocsRepoUrl}/commits/${gitData.sha}/advocacy_docs${fileUrlSegment}`; const githubEditLink = `${advocacyDocsRepoUrl}/edit/${branch}/advocacy_docs${fileUrlSegment}`; @@ -458,6 +460,7 @@ const createAdvocacy = (navTree, prevNext, doc, learn, actions) => { pagePath: doc.fields.path, navLinks: navLinks, prevNext, + productVersions, navTree, githubFileLink: githubFileHistoryLink, githubEditLink: githubEditLink, diff --git a/src/components/layout.js b/src/components/layout.js index 6f2cee0e9c3..2ab8d5275ed 100644 --- a/src/components/layout.js +++ b/src/components/layout.js @@ -53,6 +53,7 @@ const Layout = ({ to={href} pageUrl={meta.path} pageIsIndex={meta.isIndexPage} + productVersions={meta.productVersions} {...rest} /> ), diff --git a/src/components/left-nav.js b/src/components/left-nav.js index 4de191470a0..b94ac7be931 100644 --- a/src/components/left-nav.js +++ b/src/components/left-nav.js @@ -87,7 +87,7 @@ const LeftNav = ({ {navTree.items.map((node) => ( diff --git a/src/components/link.js b/src/components/link.js index 8b48064cba6..c1d071d7270 100644 --- a/src/components/link.js +++ b/src/components/link.js @@ -35,7 +35,7 @@ const hasNonMarkdownExtension = (url) => { ); }; -const rewriteUrl = (url, pageUrl, pageIsIndex, pathPrefix) => { +const rewriteUrl = (url, pageUrl, pageIsIndex, productVersions, pathPrefix) => { if (!pageUrl) return forceTrailingSlash(url); // consistent behavior while authoring: base path for relative links @@ -57,10 +57,23 @@ const rewriteUrl = (url, pageUrl, pageIsIndex, pathPrefix) => { let resultHref = result.href.replace(/^loc:/, ""); resultHref = stripPathPrefix(resultHref, pathPrefix); resultHref = stripMarkdownExtension(resultHref); + + // if this looks like a versioned product link that points at the latest version, rewrite to the "latest" path + // this avoids depending on redirects (which won't play well with client-side nav) + const splitPath = resultHref.split("/"); + if ( + productVersions && + productVersions[splitPath[1]] && + productVersions[splitPath[1]][0] === splitPath[2] + ) { + splitPath[2] = "latest"; + resultHref = splitPath.join("/"); + } + return forceTrailingSlash(resultHref); }; -const Link = ({ to, pageUrl, pageIsIndex, ...rest }) => { +const Link = ({ to, pageUrl, pageIsIndex, productVersions, ...rest }) => { const pathPrefix = usePathPrefix(); if ( @@ -74,7 +87,13 @@ const Link = ({ to, pageUrl, pageIsIndex, ...rest }) => { ); } else { - const outputUrl = rewriteUrl(to, pageUrl, pageIsIndex, pathPrefix); + const outputUrl = rewriteUrl( + to, + pageUrl, + pageIsIndex, + productVersions, + pathPrefix, + ); return ; } }; diff --git a/src/components/prev-next.js b/src/components/prev-next.js index ba4fc5dcfcb..02fb7270674 100644 --- a/src/components/prev-next.js +++ b/src/components/prev-next.js @@ -1,7 +1,7 @@ import React from "react"; import { Link } from "./"; -const PrevNext = ({ prevNext, path, depth, depthLimit = 3 }) => { +const PrevNext = ({ prevNext, depth, depthLimit = 3 }) => { let prevLink = prevNext.prev; let nextLink = prevNext.next; if (depth <= depthLimit) prevLink = null; diff --git a/src/constants/gatsby-utils.js b/src/constants/gatsby-utils.js index 115ecb32255..5fd6c525f30 100644 --- a/src/constants/gatsby-utils.js +++ b/src/constants/gatsby-utils.js @@ -255,7 +255,7 @@ const findPrevNextNavNodes = (navTree, currNode) => { }; const preprocessPathsAndRedirects = (nodes, productVersions) => { - const validPaths = new Set(); + const validPaths = new Map(); for (let node of nodes) { const nodePath = node.fields?.path; if (!nodePath) continue; @@ -265,17 +265,32 @@ const preprocessPathsAndRedirects = (nodes, productVersions) => { productVersions[node.fields.product][0] === node.fields.version; const nodePathLatest = isLatest && replacePathVersion(nodePath); - validPaths.add(nodePath); - if (isLatest) validPaths.add(nodePathLatest); + validPaths.set(nodePath, nodePathLatest || nodePath); + if (isLatest) { + validPaths.set(nodePathLatest, nodePathLatest); + // from here on, the "latest" path *is* the canonical path + node.fields.path = nodePathLatest; + } const redirects = node.frontmatter?.redirects; if (!redirects || !redirects.length) continue; const newRedirects = new Set(); const addNewRedirect = (redirect) => { - if (validPaths.has(redirect)) - console.warn(`Redirect ${redirect} for page ${nodePath} matches the path of a page or redirect already added and will be ignored! -::warning file=${node.fileAbsolutePath},title=Overlapping redirect::Redirect matches another redirect or page path, ${redirect}`); + if (validPaths.has(redirect)) { + const existing = validPaths.get(redirect); + const existingIsRedirect = existing !== redirect; + console.warn(`Redirect ${redirect} for page ${nodePath} matches the path of a ${ + existingIsRedirect + ? "redirect added in the page at" + : "page already added" + } ${existing} and will be ignored! +::warning file=${ + node.fileAbsolutePath + },title=Overlapping redirect::Redirect ${redirect} matches another ${ + existingIsRedirect ? "redirect pointing to" : "page at" + }: ${existing}`); + } newRedirects.add(redirect); }; for (let redirect of redirects) { @@ -309,9 +324,10 @@ const preprocessPathsAndRedirects = (nodes, productVersions) => { if (fromPath !== nodePath) addNewRedirect(fromPath); } - for (let redirect of newRedirects) validPaths.add(redirect); + for (let redirect of newRedirects) + validPaths.set(redirect, nodePathLatest || nodePath); - node.frontmatter.redirects = [...newRedirects]; + node.frontmatter.redirects = [...newRedirects.keys()]; } return validPaths; }; @@ -320,21 +336,22 @@ const configureRedirects = ( toPath, redirects, actions, - isLatest, + versions, pathVersions, ) => { + const splitToPath = toPath.split(path.sep); + const isLatest = splitToPath[2] === "latest"; const lastVersionPath = pathVersions.find((p) => !!p); const isLastVersion = toPath === lastVersionPath; // latest version should always redirect to .../latest/... if (isLatest) { actions.createRedirect({ - fromPath: toPath, - toPath: replacePathVersion(toPath), - redirectInBrowser: true, + fromPath: replacePathVersion(toPath, versions[0]), + toPath: toPath, + redirectInBrowser: false, isPermanent: false, force: true, }); - toPath = replacePathVersion(toPath); } // if this path is a dead-end (it does not exist in any newer versions // of the product, and also does not have a matching redirect in any newer versions) @@ -344,14 +361,13 @@ const configureRedirects = ( actions.createRedirect({ fromPath: replacePathVersion(toPath), toPath, - redirectInBrowser: true, + redirectInBrowser: false, isPermanent: false, }); } if (!redirects) return; - const splitToPath = toPath.split(path.sep); for (let fromPath of redirects) { if (!fromPath) continue; if (fromPath !== toPath) { @@ -361,7 +377,7 @@ const configureRedirects = ( actions.createRedirect({ fromPath, toPath, - redirectInBrowser: true, + redirectInBrowser: false, isPermanent, }); } @@ -406,7 +422,7 @@ const configureRedirects = ( actions.createRedirect({ fromPath, toPath, - redirectInBrowser: true, + redirectInBrowser: false, isPermanent: false, }); } diff --git a/src/templates/doc.js b/src/templates/doc.js index 6853d2c3d17..f84e0bc80bd 100644 --- a/src/templates/doc.js +++ b/src/templates/doc.js @@ -222,6 +222,7 @@ const DocTemplate = ({ data, pageContext }) => { const { frontmatter, pagePath, + productVersions, versions, githubFileLink, githubEditLink, @@ -230,7 +231,7 @@ const DocTemplate = ({ data, pageContext }) => { navTree, prevNext, } = pageContext; - const navRoot = findDescendent(navTree, (n) => n.path === path); + const navRoot = findDescendent(navTree, (n) => n.path === pagePath); const versionArray = makeVersionArray( versions, pageContext.pathVersions, @@ -265,7 +266,8 @@ const DocTemplate = ({ data, pageContext }) => { title: title, description: description, path: pagePath, - isIndexPage: isIndexPage, + isIndexPage, + productVersions, canonicalPath: pageContext.pathVersions.filter((p) => !!p)[0], }; @@ -344,9 +346,7 @@ const DocTemplate = ({ data, pageContext }) => { )} {sections && } - {depth > 2 && ( - - )} + {depth > 2 && }