From e78b84c692311b6a3d35473b5d0660f39ad3d8ab Mon Sep 17 00:00:00 2001 From: Stefan Fercot Date: Fri, 9 Jun 2023 14:40:03 +0200 Subject: [PATCH 01/29] add quick-start step numbers and fix old leftovers --- .../patroni/debian11_quick_start.mdx | 10 +++++----- .../patroni/installing_patroni.mdx | 2 +- .../patroni/rhel8_quick_start.mdx | 10 +++++----- advocacy_docs/supported-open-source/patroni/tips.mdx | 2 +- 4 files changed, 12 insertions(+), 12 deletions(-) diff --git a/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx b/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx index 66d8d36739b..309578c3d64 100644 --- a/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx +++ b/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx @@ -9,11 +9,11 @@ Use this quick start to create a highly available demo cluster using EDB Postgre --- -## Etcd +## 1. Etcd See [Installing and configuring etcd](installing_etcd) to install and set up etcd. -## EDB Postgres Advanced or Extended Server +## 2. EDB Postgres Advanced or Extended Server On both `pg-patroni1` and `pg-patroni2` hosts, install your preferred Postgres flavor. See [EDB Postgres Advanced Server](/epas/latest/installing/linux_x86_64/) or [EDB Postgres Extended Server](/pge/latest/installing/linux_x86_64/) for more information about installing these products using the EDB repository. @@ -57,7 +57,7 @@ sudo systemctl disable edb-pge-15.service sudo rm -fr /var/lib/edb-pge/15/data ``` -## Watchdog +## 3. Watchdog Patroni is the component interacting with the watchdog device. Set the permissions of the software watchdog on both `pg-patroni1` and `pg-patroni2` hosts: @@ -70,7 +70,7 @@ sudo modprobe softdog sudo chown $PGUSER:$PGGROUP /dev/watchdog ``` -## Patroni +## 4. Patroni On both `pg-patroni1` and `pg-patroni2` hosts, install Patroni and its dependencies for etcd. See [Installing Patroni](installing_patroni). @@ -224,7 +224,7 @@ sudo systemctl restart edb-as15-pgagent.service sudo systemctl reset-failed ``` -## HAProxy +## 5. HAProxy For the purpose of this example, install HAProxy on both `pg-patroni1` and `pg-patroni2` hosts: diff --git a/advocacy_docs/supported-open-source/patroni/installing_patroni.mdx b/advocacy_docs/supported-open-source/patroni/installing_patroni.mdx index 61cab08cbb4..58f04f6c395 100644 --- a/advocacy_docs/supported-open-source/patroni/installing_patroni.mdx +++ b/advocacy_docs/supported-open-source/patroni/installing_patroni.mdx @@ -9,7 +9,7 @@ tags: Patroni packages are provided through the PGDG `apt` and `yum` repositories. -See [Platform Compatibility](https://www.enterprisedb.com/resources/platform-compatibility#epas) for the supported OS list (only Linux x86-64 (amd64) currently). +See [Platform Compatibility](https://www.enterprisedb.com/resources/platform-compatibility#epas) for the supported OS list (only `Linux x86-64 (amd64)` currently). ### Debian/Ubuntu diff --git a/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx b/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx index f52c2058f43..20cbbe0afba 100644 --- a/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx +++ b/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx @@ -9,11 +9,11 @@ Use this quick start to create a highly available demo cluster using EDB Postgre --- -## Etcd +## 1. Etcd See [Installing and configuring etcd](installing_etcd) to install and set up etcd. -## EDB Postgres Advanced or Extended Server +## 2. EDB Postgres Advanced or Extended Server On both `pg-patroni1` and `pg-patroni2` hosts, install your preferred flavor of Postgres flavor. See [EDB Postgres Advanced Server](/epas/latest/installing/linux_x86_64/) or [EDB Postgres Extended Server](/pge/latest/installing/linux_x86_64/) for more information about installing these products using the EDB repository. @@ -59,7 +59,7 @@ sudo firewall-cmd --quiet --zone=public --add-port=$PGPORT/tcp --permanent sudo firewall-cmd --quiet --reload ``` -## Watchdog +## 3. Watchdog Patroni is the component interacting with the watchdog device. Set the permissions of the software watchdog on both `pg-patroni1` and `pg-patroni2` hosts: @@ -72,7 +72,7 @@ sudo modprobe softdog sudo chown $PGUSER:$PGGROUP /dev/watchdog ``` -## Patroni +## 4. Patroni On both `pg-patroni1` and `pg-patroni2` hosts, install Patroni and its dependencies for etcd. See [Installing Patroni](installing_patroni). @@ -224,7 +224,7 @@ sudo firewall-cmd --quiet --zone=public --add-port=8008/tcp --permanent sudo firewall-cmd --quiet --reload ``` -## HAProxy +## 5. HAProxy The PGDG yum [extras](https://yum.postgresql.org/news/new-repo-extra-packages/) repositories contain haproxy packages. diff --git a/advocacy_docs/supported-open-source/patroni/tips.mdx b/advocacy_docs/supported-open-source/patroni/tips.mdx index 7e7a02f4558..fb5ce9bde2b 100644 --- a/advocacy_docs/supported-open-source/patroni/tips.mdx +++ b/advocacy_docs/supported-open-source/patroni/tips.mdx @@ -17,7 +17,7 @@ __OUTPUT__ f (1 row) ``` -``` +```bash psql "host=srv1,srv2 dbname=postgres user=admin target_session_attrs=read-only" -c "SELECT pg_is_in_recovery();" __OUTPUT__ pg_is_in_recovery From 9434d78e60d05dc78354e94918a7e830e9c82fbd Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Mon, 17 Jul 2023 14:13:56 -0400 Subject: [PATCH 02/29] Some cleanup to the new text --- product_docs/docs/pgd/5/architectures.mdx | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/product_docs/docs/pgd/5/architectures.mdx b/product_docs/docs/pgd/5/architectures.mdx index 4980c1e1b3e..251fdb1b2a5 100644 --- a/product_docs/docs/pgd/5/architectures.mdx +++ b/product_docs/docs/pgd/5/architectures.mdx @@ -144,15 +144,10 @@ Use these criteria to help you to select the appropriate Always On architecture. ## Adding flexibility to the standard architectures -The single location architecture can be deployed in as many locations as desired to provide the data resiliency needed and proximity to applications and users maintaining the data. While EDB Postgres Distributed has a variety of conflict handling approaches available, in general care should be taken to minimize the number of expected collisions if allowing write activity from geographically disparate locations. +You can deploy the single-location architecture in as many locations as you want. Doing so provides the data resiliency needed and proximity to applications and to the users maintaining the data. While EDB Postgres Distributed has a variety of conflict-handling approaches available, in general take care to minimize the number of expected collisions if allowing write activity from geographically disparate locations. -The standard architectures can also be expanded with two additional types of nodes: +You can also expand the standard architectures with two additional types of nodes: -• Subscriber only nodes - -• Logical standbys - -**Subscriber only nodes** can be used to achieve additional read scalability and to have data closer to users when the majority of an application’s workload is read intensive with infrequent writes. They can also be leveraged to publish a subset of the data for reporting, archiving, and analytic needs. - -**Logical standbys** receive replicated data from another node in the PGD cluster but do not participate in the replication mesh or consensus. They contain all the same data as the other PGD data nodes, and can quickly be promoted to a master if one of the data nodes fails to return the cluster to full capacity/consensus. They can be used in environments where network traffic between data centers is a concern; otherwise 3 PGD data nodes per location is always preferred. +- **Subscriber only nodes**, which you can use to achieve additional read scalability and to have data closer to users when the majority of an application’s workload is read intensive with infrequent writes. You can also leverage them to publish a subset of the data for reporting, archiving, and analytic needs. +- **Logical standbys**, which receive replicated data from another node in the PGD cluster but don't participate in the replication mesh or consensus. They contain all the same data as the other PGD data nodes and can quickly be promoted to a master if one of the data nodes fails to return the cluster to full capacity/consensus. You can use them in environments where network traffic between data centers is a concern. Otherwise, three PGD data nodes per location is always preferred. From 8d409e21a318ffa385b9a496a0873a60bdc08df0 Mon Sep 17 00:00:00 2001 From: francoughlin Date: Mon, 17 Jul 2023 16:01:31 -0400 Subject: [PATCH 03/29] EPAS reorg: Phase 2 Reference branch Relocating topics to the Reference branch --- .../building_the_control_file/index.mdx | 305 +---------------- .../02_index_advisor/index.mdx | 1 - .../07_reference.mdx | 1 + ...audit_logging_configuration_parameters.mdx | 1 + .../01_index_advisor_components.mdx | 1 + ...02_summary_of_configuration_parameters.mdx | 1 + .../04_audit_log_file.mdx | 5 +- .../edb_loader_control_file_parameters.mdx | 311 ++++++++++++++++++ .../edb_resource_manager_system_catalogs.mdx | 2 + 9 files changed, 321 insertions(+), 307 deletions(-) rename product_docs/docs/epas/15/{application_programming/ecpgplus_guide => reference/application_programmer_reference}/07_reference.mdx (99%) rename product_docs/docs/epas/15/{epas_security_guide/05_edb_audit_logging => reference/database_administrator_reference}/01_audit_logging_configuration_parameters.mdx (98%) rename product_docs/docs/epas/15/{managing_performance/02_index_advisor => reference/database_administrator_reference}/01_index_advisor_components.mdx (97%) rename product_docs/docs/epas/15/{database_administration/01_configuration_parameters => reference/database_administrator_reference}/02_summary_of_configuration_parameters.mdx (99%) rename product_docs/docs/epas/15/{epas_security_guide/05_edb_audit_logging => reference/database_administrator_reference}/04_audit_log_file.mdx (99%) create mode 100644 product_docs/docs/epas/15/reference/database_administrator_reference/edb_loader_control_file_parameters.mdx rename product_docs/docs/epas/15/{database_administration/10_edb_resource_manager => reference/database_administrator_reference}/edb_resource_manager_system_catalogs.mdx (94%) diff --git a/product_docs/docs/epas/15/database_administration/02_edb_loader/building_the_control_file/index.mdx b/product_docs/docs/epas/15/database_administration/02_edb_loader/building_the_control_file/index.mdx index 6f146088e73..f719a4f54c0 100644 --- a/product_docs/docs/epas/15/database_administration/02_edb_loader/building_the_control_file/index.mdx +++ b/product_docs/docs/epas/15/database_administration/02_edb_loader/building_the_control_file/index.mdx @@ -104,308 +104,5 @@ Specifying one of `INSERT`, `APPEND`, `REPLACE`, or `TRUNCATE` establishes the d If you specify the `FIELDS TERMINATED BY` clause, then you can't specify the `POSITION (start:end)` clause for any `field_def`. Alternatively, if you don't specify the `FIELDS TERMINATED BY` clause, then every `field_def` must contain the `POSITION (start:end)` clause, the `fieldtype(length)` clause, or the `CONSTANT` clause. -## Parameters +For complete descriptions of the parameters available for each clause, see [EDB\*Loader control file parameters](/epas/latest/reference/database_administrator_reference/edb_loader_control_file_parameters/). -`OPTIONS param=value` - - Use the `OPTIONS` clause to specify `param=value` pairs that represent an EDB\*Loader directive. If you specify a parameter in the `OPTIONS` clause and on the command line when `edbldr` is invoked, the command line setting takes effect. - - Specify one or more of the following parameter/value pairs: - -- `DIRECT= { FALSE | TRUE }` - - With `DIRECT` 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 can potentially contain references to rows that were deleted. Direct inserts to load data into replicated tables aren't supported. - - For information on direct path loads see, [Direct path load](/epas/latest/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load/). - -- `ERRORS=error_count` - - `error_count` specifies the number of errors permitted before aborting the EDB\*Loader session. The default is `50`. - -- `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). - - 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. - - By default, `FREEZE` is `FALSE`. - -- `PARALLEL= { FALSE | TRUE }` - - Set `PARALLEL` to `TRUE` to indicate that this EDB\*Loader session is one of a number of concurrent EDB\*Loader sessions participating in a parallel direct path load. The default value of `PARALLEL` is `FALSE`. - - When `PARALLEL` is `TRUE`, you must also set the `DIRECT` parameter to `TRUE`. For more information about parallel direct path loads, see [Parallel direct path load](/epas/latest/database_administration/02_edb_loader/invoking_edb_loader/parallel_direct_path_load). - -- `ROWS=n` - - `n` specifies the number of rows that EDB\*Loader commits before loading the next set of `n` rows. - - If EDB\*Loader encounters an invalid row during a load in which the `ROWS` parameter is specified, those rows committed prior to encountering the error remain in the destination table. - -- `SKIP=skip_count` - - `skip_count` specifies the number of records at the beginning of the input data file to skip before loading begins. The default is `0`. - -- `SKIP_INDEX_MAINTENANCE={ FALSE | TRUE }` - - If `SKIP_INDEX_MAINTENANCE` is `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`. - - !!! Note - During a parallel direct path load, target table indexes aren't updated. They are 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.html). - -`charset` - - Use the `CHARACTERSET` clause to identify the character set encoding of `data_file`, where `charset` is the character set name. This clause is required if the data file encoding differs from the control file encoding. The control file encoding must always be in the encoding of the client where `edbldr` is invoked. - - Examples of `charset` settings are `UTF8`, `SQL_ASCII`, and `SJIS`. - - For more information about client-to-database character-set conversion, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/multibyte.html). - -`data_file` - - File containing the data to load into `target_table`. Each record in the data file corresponds to a row to insert into `target_table`. - - If you don't include an extension in the file name, EDB\*Loader assumes the file has an extension of `.dat`, for example, `mydatafile.dat`. - - !!! Note - If you specify the `DATA` parameter on the command line when invoking `edbldr`, the file given by the command line `DATA` parameter is used instead. - - If you omit the `INFILE` clause and the command line `DATA` parameter, then the data file name is assumed to be the same as the control file name but with the extension `.dat`. - -`stdin` - - Specify `stdin` (all lowercase letters) if you want to use standard input to pipe the data to load directly to EDB\*Loader. This technique is useful for data sources generating a large number of records to load. - -`bad_file` - - A file that receives `data_file` records that can't load due to errors. The bad file is generated for collecting rejected or bad records. - - For EDB Postgres Advanced Server version 12 and later, a bad file is generated only if there are any bad or rejected records. However, if an existing bad file has the same name and location, and no bad records are generated after invoking a new version of `edbldr`, the existing bad file remains intact. - - If you don't include an extension in the file name, EDB\*Loader assumes the file has an extension of `.bad`, for example, `mybadfile.bad`. - - !!! Note - If you specify the `BAD` parameter on the command line when invoking `edbldr`, the file given with the command line `BAD` parameter is used instead. - -`discard_file` - - File that receives input data records that aren't loaded into any table. This input data records are discarded because none of the selection criteria are met for tables with the `WHEN` clause and there are no tables without a `WHEN` clause. All records meet the selection criteria of a table without a `WHEN` clause. - - If you don't include an extension with the file name, EDB\*Loader assumes the file has an extension of `.dsc`, for example, `mydiscardfile.dsc`. - - !!! Note - If you specify the `DISCARD` parameter on the command line when invoking `edbldr`, the file given with the command line `DISCARD` parameter is used instead. - -`{ DISCARDMAX | DISCARDS } max_discard_recs` - - Maximum number of discarded records that the input data records can encounter before terminating the EDB\*Loader session. You can use either keyword `DISCARDMAX` or `DISCARDS` preceding the integer value specified by `max_discard_recs`. - - For example, if `max_discard_recs` is `0`, then the EDB\*Loader session is terminated when a first discarded record is encountered. If `max_discard_recs` is `1`, then the EDB\*Loader session is terminated when a second discarded record is encountered. - - When the EDB\*Loader session is terminated due to exceeding `max_discard_recs`, prior input data records that were loaded into the database are retained. They aren't rolled back. - -`INSERT | APPEND | REPLACE | TRUNCATE` - - Specifies how to load data into the target tables. Specifying one of `INSERT`, `APPEND`, `REPLACE`, or `TRUNCATE` establishes the default action for all tables, overriding the default of `INSERT`. - -- `INSERT` - - Data is loaded into an empty table. EDB\*Loader throws an exception and doesn't load any data if the table isn't initially empty. - - !!! Note - If the table contains rows, you must use the `TRUNCATE` command to empty the table before invoking EDB\*Loader. EDB\*Loader throws an exception if you use the `DELETE` command to empty the table instead of the `TRUNCATE` command. Oracle SQL\*Loader allows you to empty the table by using either the `DELETE` or `TRUNCATE` command. - -- `APPEND` - - Data is added to any existing rows in the table. The table also can be empty initially. - -- `REPLACE` - - The `REPLACE` keyword and `TRUNCATE` keywords are functionally identical. The table is truncated by EDB\*Loader before loading the new data. - - !!! Note - Delete triggers on the table aren't fired as a result of the `REPLACE` operation. - -- `TRUNCATE` - - The table is truncated by EDB\*Loader before loading the new data. Delete triggers on the table aren't fired as a result of the `TRUNCATE` operation. - -`PRESERVE BLANKS` - - The `PRESERVE BLANKS` option works only with the `OPTIONALLY ENCLOSED BY` clause. It retains leading and trailing whitespaces for both delimited and predetermined size fields. - - In case of `NO PRESERVE BLANKS`, if the fields are delimited, then only leading whitespaces are omitted. If any trailing whitespaces are present, they are left intact. In the case of predetermined-sized fields with `NO PRESERVE BLANKS`, the trailing whitespaces are omitted. Any leading whitespaces are left intact. - - !!! Note - If you don't explicitly provide `PRESERVE BLANKS` or `NO PRESERVE BLANKS`, then the behavior defaults to `NO PRESERVE BLANKS`. This option doesn't work for ideographic whitespaces. - -`target_table` - - Name of the table into which to load data. The table name can be schema-qualified (for example, `enterprisedb.emp`). The specified target can't be a view. - -`field_condition` - - Conditional clause taking the following form: - -```text -[ ( ] { (start:end) | column_name } { = | != | <> } 'val' [ ) ] -``` - - This conditional clause is used for the `WHEN` clause, which is part of the `INTO TABLE target_table` clause. It's also used for the `NULLIF` clause, which is part of the field definition denoted as `field_def` in the syntax diagram. - - `start` and `end` are positive integers specifying the column positions in `data_file` that mark the beginning and end of a field to compare with the constant `val`. The first character in each record begins with a `start` value of `1`. - - `column_name` specifies the name assigned to a field definition of the data file as defined by `field_def` in the syntax diagram. - - Using (`start`:`end`) or `column_name` defines the portion of the record in `data_file` to compare with the value specified by `val` to evaluate as either true or false. - - All characters used in the `field_condition` text (particularly in the `val` string) must be valid in the database encoding. For performing data conversion, EDB\*Loader first converts the characters in `val` string to the database encoding and then to the data file encoding. - - In the `WHEN field_condition [ AND field_condition ]` clause, if all such conditions evaluate to `TRUE` for a given record, then EDB\*Loader attempts to insert that record into `target_table`. If the insert operation fails, the record is written to `bad_file`. - - Suppose, for a given record, that none of the `WHEN` clauses evaluate to `TRUE` for all `INTO TABLE` clauses. The record is written to `discard_file` if a discard file was specified for the EDB\*Loader session. - - See the description of the `NULLIF` clause in this parameters list for the effect of `field_condition` on this clause. - -`termstring` - - String of one or more characters that separates each field in `data_file`. The characters can be single byte or multibyte. However, they must be valid in the database encoding. Two consecutive appearances of `termstring` with no intervening character results in the corresponding column being set to null. - -`enclstring` - - String of one or more characters used to enclose a field value in `data_file`. The characters can be single byte or multibyte, However, they must be valid in the database encoding. Use `enclstring` on fields where `termstring` appears as part of the data. - -`delimstring` - - String of one or more characters that separates each record in `data_file`. The characters can be single byte or multibyte. However, they must be valid in the database encoding. Two consecutive appearances of `delimstring` with no intervening character results in no corresponding row being loaded into the table. You must also terminate the last record (that is, the end of the data file) with the `delimstring` characters. Otherwise, the final record isn't loaded into the table. - - !!! Note - The `RECORDS DELIMITED BY 'delimstring'` clause isn't compatible with Oracle databases. - -`TRAILING NULLCOLS` - - If you specify `TRAILING NULLCOLS`, then the columns in the column list for which there's no data in `data_file` for a given record are set to null when the row is inserted. This option applies only to one or more consecutive columns at the end of the column list. - - If fields are omitted at the end of a record and you don't specify `TRAILING NULLCOLS`, EDB\*Loader assumes the record contains formatting errors and writes it to the bad file. - -`column_name` - - Name of a column in `target_table` into which to insert a field value defined by `field_def`. If the field definition includes the `FILLER` or `BOUNDFILLER` clause, then `column_name` isn't required as the name of a column in the table. It can be any identifier name since the `FILLER` and `BOUNDFILLER` clauses prevent loading the field data into a table column. - -`CONSTANT val` - - Specifies a constant that's type-compatible with the column data type to which it's assigned in a field definition. You can use single or double quotes around `val`. If `val` contains white space, then you must use quotation marks around it. - - The use of the `CONSTANT` clause determines the value to assign to a column in each inserted row. No other clause can appear in the same field definition. - - If you use the `TERMINATED BY` clause to delimit the fields in `data_file`, there must be no delimited field in `data_file` corresponding to any field definition with a `CONSTANT` clause. In other words, EDB\*Loader assumes there's no field in `data_file` for any field definition with a `CONSTANT` clause. - -`FILLER` - - Specifies not to load the data in the field defined by the field definition into the associated column if the identifier of the field definition is an actual column name in the table. In this case, the column is set to null. Use of the `FILLER` or `BOUNDFILLER` clause is the only circumstance in which you don't have to identify the field definition with an actual column name. - - Unlike the `BOUNDFILLER` clause, you can't reference an identifier defined with the `FILLER` clause in a SQL expression. See the discussion of the `expr` parameter. - -`BOUNDFILLER` - - Specifies not to load the data in the field defined by the field definition into the associated column if the identifier of the field definition is an actual column name in the table. In this case, the column is set to null. Use of the `FILLER` or `BOUNDFILLER` clause is the only circumstance in which you don't have to identify the field definition with an actual column name. - - Unlike the `FILLER` clause, a SQL expression can reference an identifier defined with the `BOUNDFILLER` clause. See the discussion of the `expr` parameter. - -`POSITION (start:end)` - - Defines the location of the field in a record in a fixed-width field data file. `start` and `end` are positive integers. The first character in the record has a start value of `1`. - -```sql -CHAR [()] | DATE [()] | TIMESTAMP [()] [ "" ] | -INTEGER EXTERNAL [()] | -FLOAT EXTERNAL [()] | DECIMAL EXTERNAL [()] | -ZONED EXTERNAL [()] | ZONED [([,])] -``` - - Field type that describes the format of the data field in `data_file`. - - !!! Note - Specifying a field type is optional for descriptive purposes and has no effect on whether EDB\*Loader successfully inserts the data in the field into the table column. Successful loading depends on the compatibility of the column data type and the field value. For example, a column with data type `NUMBER(7,2)` successfully accepts a field containing `2600`. However, if the field contains a value such as `26XX`, the insertion fails, and the record is written to `bad_file`. - -`ZONED` data is not human readable. `ZONED` data is stored in an internal format where each digit is encoded in a separate nibble/nybble/4-bit field. In each `ZONED` value, the last byte contains a single digit in the high-order 4 bits and the sign in the low-order 4 bits. - -`length` - - Specifies the length of the value to load into the associated column. - - If you specify the `POSITION` (`start`:`end`) clause with a `fieldtype(length)` clause, then the ending position of the field is overridden by the specified `length` value. That is, the length of the value to load into the column is determined by the `length` value beginning at the `start` position and not by the `end` position of the `POSITION` (`start`:`end`) clause. Thus, the value to load into the column might be shorter than the field defined by `POSITION` (`start`:`end`). Or, it might go beyond the end position, depending on the specified `length` size. - - If you specify the `FIELDS TERMINATED BY 'termstring'` clause as part of the `INTO TABLE` clause, and a field definition contains the `fieldtype(length)` clause, then a record is accepted. However, the specified `length` values must be greater than or equal to the field lengths as determined by the `termstring` characters enclosing all such fields of the record. If the specified `length` value is less than a field length as determined by the enclosing `termstring` characters for any such field, then the record is rejected. - - If you don't specify the `FIELDS TERMINATED BY 'termstring'` clause, and you don't include the `POSITION` (`start`:`end`) clause with a field containing the `fieldtype(length)` clause, then the starting position of this field begins with the next character following the ending position of the preceding field. The ending position of the preceding field is either: - - - The end of its `length` value if the preceding field contains the `fieldtype(length)` clause - - Its `end` parameter if the field contains the `POSITION` (`start`:`end`) clause without the `fieldtype(length)` clause - -`precision` - - Use `precision` to specify the length of the `ZONED` value. - - If the `precision` value specified for `ZONED` conflicts with the length calculated by the server based on information provided with the `POSITION` clause, EDB\*Loader uses the value specified for `precision`. - -`scale` - - Specifies the number of digits to the right of the decimal point in a `ZONED` value. - -`datemask` - - Specifies the ordering and abbreviation of the day, month, and year components of a date field. - - !!! Note - If you specify the `DATE` or `TIMESTAMP` field type with a SQL expression for the column, then you must specify `datemask` after `DATE` or `TIMESTAMP` and before the SQL expression. See the discussion of the `expr` parameter. - - When using the `TIMESTAMP` field datatype, if you specify `time_stamp timestamp "yyyymmddhh24miss"`, the `datemask` is converted to the SQL expression. However, in the case of `time_stamp timestamp "select to_timestamp(:time_stamp, 'yyyymmddhh24miss')"`, EDB\*Loader can't differentiate between datemask and the SQL expression. It treats the third field (SQL expression in the example) as datemask and prepares the SQL expression, which isn't valid. Where: - -- `first field` specifies the column name. -- `second field` specifies the datatype. -- `third field` specifies the datemask. - -If you want to provide an SQL expression, then a workaround is to specify the datemask and SQL expression using the `TO_CHAR` function as: - - ```sql - time_stamp timestamp "yyyymmddhh24miss" "to_char(to_timestamp(:time_stamp, 'yyyymmddhh24miss'), 'yyyymmddhh24miss')" - ``` - -`NULLIF field_condition [ AND field_condition ] ...` - - See the description of `field_condition` in this parameter list for the syntax of `field_condition`. - - If all field conditions evaluate to `TRUE`, then the column identified by `column_name` in the field definition is set to null. If any field condition evaluates to `FALSE`, then the column is set to the appropriate value as normally occurs according to the field definition. - -`PRESERVE BLANKS` - - The `PRESERVE BLANKS` option works only with the `OPTIONALLY ENCLOSED BY` clause and retains leading and trailing whitespaces for both delimited and predetermined size fields. - - In case of `NO PRESERVE BLANKS`, if the fields are delimited, then only leading whitespaces are omitted. If any trailing whitespaces are present, they are left intact. In the case of predetermined-sized fields with `NO PRESERVE BLANKS`, the trailing whitespaces are omitted, and any leading whitespaces are left intact. - - !!! Note - If you don't provide `PRESERVE BLANKS` or `NO PRESERVE BLANKS`, then the behavior defaults to `NO PRESERVE BLANKS`. This option doesn't work for ideographic whitespaces. - -`expr` - - A SQL expression returning a scalar value that's type-compatible with the column data type to which it's assigned in a field definition. Use double quotes around `expr`. `expr` can contain a reference to any column in the field list except for fields with the `FILLER` clause. Prefix the column name using a colon (`:`). - - `expr` can also consist of a SQL `SELECT` statement. If you use a `SELECT` statement: - -- Enclose the `SELECT` statement in parentheses, that is, `(SELECT ...)`. -- The select list must consist of one expression following the `SELECT` keyword. -- The result set must not return more than one row. If no rows are returned, then the returned value of the resulting expression is null. - - The following is the syntax for a `SELECT` statement: - - ```sql - "(SELECT [ FROM [ WHERE ] ])" - ``` - - !!! Note - Omitting the `FROM table_list` clause isn't compatible with Oracle databases. If you don't need to specify any tables, using the `FROM DUAL` clause is compatible with Oracle databases. diff --git a/product_docs/docs/epas/15/managing_performance/02_index_advisor/index.mdx b/product_docs/docs/epas/15/managing_performance/02_index_advisor/index.mdx index 6fa7716486b..786bb2c31b5 100644 --- a/product_docs/docs/epas/15/managing_performance/02_index_advisor/index.mdx +++ b/product_docs/docs/epas/15/managing_performance/02_index_advisor/index.mdx @@ -5,7 +5,6 @@ indexCards: simple description: "How to use the Index Advisor utility to help determine the columns to index to improve performance in a given workload" navigation: - index_advisor_overview - - 01_index_advisor_components - 02_index_advisor_configuration - 03_using_index_advisor - 04_reviewing_the_index_advisor_recommendations diff --git a/product_docs/docs/epas/15/application_programming/ecpgplus_guide/07_reference.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/07_reference.mdx similarity index 99% rename from product_docs/docs/epas/15/application_programming/ecpgplus_guide/07_reference.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/07_reference.mdx index e5fbd50ba85..c66bc56205c 100644 --- a/product_docs/docs/epas/15/application_programming/ecpgplus_guide/07_reference.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/07_reference.mdx @@ -68,6 +68,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.101.html" redirects: - ../../../ecpgplus_guide/07_reference #generated for docs/epas/reorg-role-use-case-mode + - ../../../application_programming/ecpgplus_guide/07_reference/ --- diff --git a/product_docs/docs/epas/15/epas_security_guide/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx b/product_docs/docs/epas/15/reference/database_administrator_reference/01_audit_logging_configuration_parameters.mdx similarity index 98% rename from product_docs/docs/epas/15/epas_security_guide/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx rename to product_docs/docs/epas/15/reference/database_administrator_reference/01_audit_logging_configuration_parameters.mdx index 751b338c05a..bf98e3f88bc 100644 --- a/product_docs/docs/epas/15/epas_security_guide/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx +++ b/product_docs/docs/epas/15/reference/database_administrator_reference/01_audit_logging_configuration_parameters.mdx @@ -3,6 +3,7 @@ title: "Audit logging configuration parameters" description: "Describes the configuration parameters you can use to control database auditing" redirects: - ../../../epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/epas_security_guide/05_edb_audit_logging/01_audit_logging_configuration_parameters/ --- Use the following configuration parameters to control database auditing. See [Summary of configuration parameters](/epas/latest/database_administration/01_configuration_parameters/02_summary_of_configuration_parameters/) to determine if a change to the configuration parameter: diff --git a/product_docs/docs/epas/15/managing_performance/02_index_advisor/01_index_advisor_components.mdx b/product_docs/docs/epas/15/reference/database_administrator_reference/01_index_advisor_components.mdx similarity index 97% rename from product_docs/docs/epas/15/managing_performance/02_index_advisor/01_index_advisor_components.mdx rename to product_docs/docs/epas/15/reference/database_administrator_reference/01_index_advisor_components.mdx index 47d990cd5ad..787dd399cf1 100644 --- a/product_docs/docs/epas/15/managing_performance/02_index_advisor/01_index_advisor_components.mdx +++ b/product_docs/docs/epas/15/reference/database_administrator_reference/01_index_advisor_components.mdx @@ -3,6 +3,7 @@ title: "Index Advisor components" description: "Description of the components of the Index Advisor shared library" redirects: - ../../../epas_guide/03_database_administration/02_index_advisor/01_index_advisor_components #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/managing_performance/02_index_advisor/01_index_advisor_components/ --- diff --git a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/02_summary_of_configuration_parameters.mdx b/product_docs/docs/epas/15/reference/database_administrator_reference/02_summary_of_configuration_parameters.mdx similarity index 99% rename from product_docs/docs/epas/15/database_administration/01_configuration_parameters/02_summary_of_configuration_parameters.mdx rename to product_docs/docs/epas/15/reference/database_administrator_reference/02_summary_of_configuration_parameters.mdx index fb82edf108f..951691dc391 100644 --- a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/02_summary_of_configuration_parameters.mdx +++ b/product_docs/docs/epas/15/reference/database_administrator_reference/02_summary_of_configuration_parameters.mdx @@ -7,6 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.010.html" redirects: - ../../../epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters #generated for docs/epas/reorg-role-use-case-mode + - ../../../database_administration/01_configuration_parameters/02_summary_of_configuration_parameters/ --- diff --git a/product_docs/docs/epas/15/epas_security_guide/05_edb_audit_logging/04_audit_log_file.mdx b/product_docs/docs/epas/15/reference/database_administrator_reference/04_audit_log_file.mdx similarity index 99% rename from product_docs/docs/epas/15/epas_security_guide/05_edb_audit_logging/04_audit_log_file.mdx rename to product_docs/docs/epas/15/reference/database_administrator_reference/04_audit_log_file.mdx index 0ef413b5fb7..99ee53e5b97 100644 --- a/product_docs/docs/epas/15/epas_security_guide/05_edb_audit_logging/04_audit_log_file.mdx +++ b/product_docs/docs/epas/15/reference/database_administrator_reference/04_audit_log_file.mdx @@ -1,8 +1,9 @@ --- -title: "Using the Audit log file" -description: "Describes how to generate an audit log file" +title: "Audit log files" +description: "Describes the fields in an audit log file" redirects: - ../../../epas_guide/03_database_administration/05_edb_audit_logging/04_audit_log_file #generated for docs/epas/reorg-role-use-case-mode + - ../../../epas_security_guide/epas_security_guide/05_edb_audit_logging/04_audit_log_file/ --- diff --git a/product_docs/docs/epas/15/reference/database_administrator_reference/edb_loader_control_file_parameters.mdx b/product_docs/docs/epas/15/reference/database_administrator_reference/edb_loader_control_file_parameters.mdx new file mode 100644 index 00000000000..312bf703542 --- /dev/null +++ b/product_docs/docs/epas/15/reference/database_administrator_reference/edb_loader_control_file_parameters.mdx @@ -0,0 +1,311 @@ +--- +title: "EDB*Loader control file parameters" +description: "Describes the parameters for each clause used in the control file" +--- + +Use the following parameters when [building the EDB\*Loader control file](/epas/latest/database_administration/02_edb_loader/building_the_control_file/). + +`OPTIONS param=value` + + Use the `OPTIONS` clause to specify `param=value` pairs that represent an EDB\*Loader directive. If you specify a parameter in the `OPTIONS` clause and on the command line when `edbldr` is invoked, the command line setting takes effect. + + Specify one or more of the following parameter/value pairs: + +- `DIRECT= { FALSE | TRUE }` + + With `DIRECT` 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 can potentially contain references to rows that were deleted. Direct inserts to load data into replicated tables aren't supported. + + For information on direct path loads see, [Direct path load](/epas/latest/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load/). + +- `ERRORS=error_count` + + `error_count` specifies the number of errors permitted before aborting the EDB\*Loader session. The default is `50`. + +- `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). + + 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. + + By default, `FREEZE` is `FALSE`. + +- `PARALLEL= { FALSE | TRUE }` + + Set `PARALLEL` to `TRUE` to indicate that this EDB\*Loader session is one of a number of concurrent EDB\*Loader sessions participating in a parallel direct path load. The default value of `PARALLEL` is `FALSE`. + + When `PARALLEL` is `TRUE`, you must also set the `DIRECT` parameter to `TRUE`. For more information about parallel direct path loads, see [Parallel direct path load](/epas/latest/database_administration/02_edb_loader/invoking_edb_loader/parallel_direct_path_load). + +- `ROWS=n` + + `n` specifies the number of rows that EDB\*Loader commits before loading the next set of `n` rows. + + If EDB\*Loader encounters an invalid row during a load in which the `ROWS` parameter is specified, those rows committed prior to encountering the error remain in the destination table. + +- `SKIP=skip_count` + + `skip_count` specifies the number of records at the beginning of the input data file to skip before loading begins. The default is `0`. + +- `SKIP_INDEX_MAINTENANCE={ FALSE | TRUE }` + + If `SKIP_INDEX_MAINTENANCE` is `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`. + + !!! Note + During a parallel direct path load, target table indexes aren't updated. They are 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.html). + +`charset` + + Use the `CHARACTERSET` clause to identify the character set encoding of `data_file`, where `charset` is the character set name. This clause is required if the data file encoding differs from the control file encoding. The control file encoding must always be in the encoding of the client where `edbldr` is invoked. + + Examples of `charset` settings are `UTF8`, `SQL_ASCII`, and `SJIS`. + + For more information about client-to-database character-set conversion, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/multibyte.html). + +`data_file` + + File containing the data to load into `target_table`. Each record in the data file corresponds to a row to insert into `target_table`. + + If you don't include an extension in the file name, EDB\*Loader assumes the file has an extension of `.dat`, for example, `mydatafile.dat`. + + !!! Note + If you specify the `DATA` parameter on the command line when invoking `edbldr`, the file given by the command line `DATA` parameter is used instead. + + If you omit the `INFILE` clause and the command line `DATA` parameter, then the data file name is assumed to be the same as the control file name but with the extension `.dat`. + +`stdin` + + Specify `stdin` (all lowercase letters) if you want to use standard input to pipe the data to load directly to EDB\*Loader. This technique is useful for data sources generating a large number of records to load. + +`bad_file` + + A file that receives `data_file` records that can't load due to errors. The bad file is generated for collecting rejected or bad records. + + For EDB Postgres Advanced Server version 12 and later, a bad file is generated only if there are any bad or rejected records. However, if an existing bad file has the same name and location, and no bad records are generated after invoking a new version of `edbldr`, the existing bad file remains intact. + + If you don't include an extension in the file name, EDB\*Loader assumes the file has an extension of `.bad`, for example, `mybadfile.bad`. + + !!! Note + If you specify the `BAD` parameter on the command line when invoking `edbldr`, the file given with the command line `BAD` parameter is used instead. + +`discard_file` + + File that receives input data records that aren't loaded into any table. This input data records are discarded because none of the selection criteria are met for tables with the `WHEN` clause and there are no tables without a `WHEN` clause. All records meet the selection criteria of a table without a `WHEN` clause. + + If you don't include an extension with the file name, EDB\*Loader assumes the file has an extension of `.dsc`, for example, `mydiscardfile.dsc`. + + !!! Note + If you specify the `DISCARD` parameter on the command line when invoking `edbldr`, the file given with the command line `DISCARD` parameter is used instead. + +`{ DISCARDMAX | DISCARDS } max_discard_recs` + + Maximum number of discarded records that the input data records can encounter before terminating the EDB\*Loader session. You can use either keyword `DISCARDMAX` or `DISCARDS` preceding the integer value specified by `max_discard_recs`. + + For example, if `max_discard_recs` is `0`, then the EDB\*Loader session is terminated when a first discarded record is encountered. If `max_discard_recs` is `1`, then the EDB\*Loader session is terminated when a second discarded record is encountered. + + When the EDB\*Loader session is terminated due to exceeding `max_discard_recs`, prior input data records that were loaded into the database are retained. They aren't rolled back. + +`INSERT | APPEND | REPLACE | TRUNCATE` + + Specifies how to load data into the target tables. Specifying one of `INSERT`, `APPEND`, `REPLACE`, or `TRUNCATE` establishes the default action for all tables, overriding the default of `INSERT`. + +- `INSERT` + + Data is loaded into an empty table. EDB\*Loader throws an exception and doesn't load any data if the table isn't initially empty. + + !!! Note + If the table contains rows, you must use the `TRUNCATE` command to empty the table before invoking EDB\*Loader. EDB\*Loader throws an exception if you use the `DELETE` command to empty the table instead of the `TRUNCATE` command. Oracle SQL\*Loader allows you to empty the table by using either the `DELETE` or `TRUNCATE` command. + +- `APPEND` + + Data is added to any existing rows in the table. The table also can be empty initially. + +- `REPLACE` + + The `REPLACE` keyword and `TRUNCATE` keywords are functionally identical. The table is truncated by EDB\*Loader before loading the new data. + + !!! Note + Delete triggers on the table aren't fired as a result of the `REPLACE` operation. + +- `TRUNCATE` + + The table is truncated by EDB\*Loader before loading the new data. Delete triggers on the table aren't fired as a result of the `TRUNCATE` operation. + +`PRESERVE BLANKS` + + The `PRESERVE BLANKS` option works only with the `OPTIONALLY ENCLOSED BY` clause. It retains leading and trailing whitespaces for both delimited and predetermined size fields. + + In case of `NO PRESERVE BLANKS`, if the fields are delimited, then only leading whitespaces are omitted. If any trailing whitespaces are present, they are left intact. In the case of predetermined-sized fields with `NO PRESERVE BLANKS`, the trailing whitespaces are omitted. Any leading whitespaces are left intact. + + !!! Note + If you don't explicitly provide `PRESERVE BLANKS` or `NO PRESERVE BLANKS`, then the behavior defaults to `NO PRESERVE BLANKS`. This option doesn't work for ideographic whitespaces. + +`target_table` + + Name of the table into which to load data. The table name can be schema-qualified (for example, `enterprisedb.emp`). The specified target can't be a view. + +`field_condition` + + Conditional clause taking the following form: + +```text +[ ( ] { (start:end) | column_name } { = | != | <> } 'val' [ ) ] +``` + + This conditional clause is used for the `WHEN` clause, which is part of the `INTO TABLE target_table` clause. It's also used for the `NULLIF` clause, which is part of the field definition denoted as `field_def` in the syntax diagram. + + `start` and `end` are positive integers specifying the column positions in `data_file` that mark the beginning and end of a field to compare with the constant `val`. The first character in each record begins with a `start` value of `1`. + + `column_name` specifies the name assigned to a field definition of the data file as defined by `field_def` in the syntax diagram. + + Using (`start`:`end`) or `column_name` defines the portion of the record in `data_file` to compare with the value specified by `val` to evaluate as either true or false. + + All characters used in the `field_condition` text (particularly in the `val` string) must be valid in the database encoding. For performing data conversion, EDB\*Loader first converts the characters in `val` string to the database encoding and then to the data file encoding. + + In the `WHEN field_condition [ AND field_condition ]` clause, if all such conditions evaluate to `TRUE` for a given record, then EDB\*Loader attempts to insert that record into `target_table`. If the insert operation fails, the record is written to `bad_file`. + + Suppose, for a given record, that none of the `WHEN` clauses evaluate to `TRUE` for all `INTO TABLE` clauses. The record is written to `discard_file` if a discard file was specified for the EDB\*Loader session. + + See the description of the `NULLIF` clause in this parameters list for the effect of `field_condition` on this clause. + +`termstring` + + String of one or more characters that separates each field in `data_file`. The characters can be single byte or multibyte. However, they must be valid in the database encoding. Two consecutive appearances of `termstring` with no intervening character results in the corresponding column being set to null. + +`enclstring` + + String of one or more characters used to enclose a field value in `data_file`. The characters can be single byte or multibyte, However, they must be valid in the database encoding. Use `enclstring` on fields where `termstring` appears as part of the data. + +`delimstring` + + String of one or more characters that separates each record in `data_file`. The characters can be single byte or multibyte. However, they must be valid in the database encoding. Two consecutive appearances of `delimstring` with no intervening character results in no corresponding row being loaded into the table. You must also terminate the last record (that is, the end of the data file) with the `delimstring` characters. Otherwise, the final record isn't loaded into the table. + + !!! Note + The `RECORDS DELIMITED BY 'delimstring'` clause isn't compatible with Oracle databases. + +`TRAILING NULLCOLS` + + If you specify `TRAILING NULLCOLS`, then the columns in the column list for which there's no data in `data_file` for a given record are set to null when the row is inserted. This option applies only to one or more consecutive columns at the end of the column list. + + If fields are omitted at the end of a record and you don't specify `TRAILING NULLCOLS`, EDB\*Loader assumes the record contains formatting errors and writes it to the bad file. + +`column_name` + + Name of a column in `target_table` into which to insert a field value defined by `field_def`. If the field definition includes the `FILLER` or `BOUNDFILLER` clause, then `column_name` isn't required as the name of a column in the table. It can be any identifier name since the `FILLER` and `BOUNDFILLER` clauses prevent loading the field data into a table column. + +`CONSTANT val` + + Specifies a constant that's type-compatible with the column data type to which it's assigned in a field definition. You can use single or double quotes around `val`. If `val` contains white space, then you must use quotation marks around it. + + The use of the `CONSTANT` clause determines the value to assign to a column in each inserted row. No other clause can appear in the same field definition. + + If you use the `TERMINATED BY` clause to delimit the fields in `data_file`, there must be no delimited field in `data_file` corresponding to any field definition with a `CONSTANT` clause. In other words, EDB\*Loader assumes there's no field in `data_file` for any field definition with a `CONSTANT` clause. + +`FILLER` + + Specifies not to load the data in the field defined by the field definition into the associated column if the identifier of the field definition is an actual column name in the table. In this case, the column is set to null. Use of the `FILLER` or `BOUNDFILLER` clause is the only circumstance in which you don't have to identify the field definition with an actual column name. + + Unlike the `BOUNDFILLER` clause, you can't reference an identifier defined with the `FILLER` clause in a SQL expression. See the discussion of the `expr` parameter. + +`BOUNDFILLER` + + Specifies not to load the data in the field defined by the field definition into the associated column if the identifier of the field definition is an actual column name in the table. In this case, the column is set to null. Use of the `FILLER` or `BOUNDFILLER` clause is the only circumstance in which you don't have to identify the field definition with an actual column name. + + Unlike the `FILLER` clause, a SQL expression can reference an identifier defined with the `BOUNDFILLER` clause. See the discussion of the `expr` parameter. + +`POSITION (start:end)` + + Defines the location of the field in a record in a fixed-width field data file. `start` and `end` are positive integers. The first character in the record has a start value of `1`. + +```sql +CHAR [()] | DATE [()] | TIMESTAMP [()] [ "" ] | +INTEGER EXTERNAL [()] | +FLOAT EXTERNAL [()] | DECIMAL EXTERNAL [()] | +ZONED EXTERNAL [()] | ZONED [([,])] +``` + + Field type that describes the format of the data field in `data_file`. + + !!! Note + Specifying a field type is optional for descriptive purposes and has no effect on whether EDB\*Loader successfully inserts the data in the field into the table column. Successful loading depends on the compatibility of the column data type and the field value. For example, a column with data type `NUMBER(7,2)` successfully accepts a field containing `2600`. However, if the field contains a value such as `26XX`, the insertion fails, and the record is written to `bad_file`. + +`ZONED` data is not human readable. `ZONED` data is stored in an internal format where each digit is encoded in a separate nibble/nybble/4-bit field. In each `ZONED` value, the last byte contains a single digit in the high-order 4 bits and the sign in the low-order 4 bits. + +`length` + + Specifies the length of the value to load into the associated column. + + If you specify the `POSITION` (`start`:`end`) clause with a `fieldtype(length)` clause, then the ending position of the field is overridden by the specified `length` value. That is, the length of the value to load into the column is determined by the `length` value beginning at the `start` position and not by the `end` position of the `POSITION` (`start`:`end`) clause. Thus, the value to load into the column might be shorter than the field defined by `POSITION` (`start`:`end`). Or, it might go beyond the end position, depending on the specified `length` size. + + If you specify the `FIELDS TERMINATED BY 'termstring'` clause as part of the `INTO TABLE` clause, and a field definition contains the `fieldtype(length)` clause, then a record is accepted. However, the specified `length` values must be greater than or equal to the field lengths as determined by the `termstring` characters enclosing all such fields of the record. If the specified `length` value is less than a field length as determined by the enclosing `termstring` characters for any such field, then the record is rejected. + + If you don't specify the `FIELDS TERMINATED BY 'termstring'` clause, and you don't include the `POSITION` (`start`:`end`) clause with a field containing the `fieldtype(length)` clause, then the starting position of this field begins with the next character following the ending position of the preceding field. The ending position of the preceding field is either: + + - The end of its `length` value if the preceding field contains the `fieldtype(length)` clause + - Its `end` parameter if the field contains the `POSITION` (`start`:`end`) clause without the `fieldtype(length)` clause + +`precision` + + Use `precision` to specify the length of the `ZONED` value. + + If the `precision` value specified for `ZONED` conflicts with the length calculated by the server based on information provided with the `POSITION` clause, EDB\*Loader uses the value specified for `precision`. + +`scale` + + Specifies the number of digits to the right of the decimal point in a `ZONED` value. + +`datemask` + + Specifies the ordering and abbreviation of the day, month, and year components of a date field. + + !!! Note + If you specify the `DATE` or `TIMESTAMP` field type with a SQL expression for the column, then you must specify `datemask` after `DATE` or `TIMESTAMP` and before the SQL expression. See the discussion of the `expr` parameter. + + When using the `TIMESTAMP` field datatype, if you specify `time_stamp timestamp "yyyymmddhh24miss"`, the `datemask` is converted to the SQL expression. However, in the case of `time_stamp timestamp "select to_timestamp(:time_stamp, 'yyyymmddhh24miss')"`, EDB\*Loader can't differentiate between datemask and the SQL expression. It treats the third field (SQL expression in the example) as datemask and prepares the SQL expression, which isn't valid. Where: + +- `first field` specifies the column name. +- `second field` specifies the datatype. +- `third field` specifies the datemask. + +If you want to provide an SQL expression, then a workaround is to specify the datemask and SQL expression using the `TO_CHAR` function as: + + ```sql + time_stamp timestamp "yyyymmddhh24miss" "to_char(to_timestamp(:time_stamp, 'yyyymmddhh24miss'), 'yyyymmddhh24miss')" + ``` + +`NULLIF field_condition [ AND field_condition ] ...` + + See the description of `field_condition` in this parameter list for the syntax of `field_condition`. + + If all field conditions evaluate to `TRUE`, then the column identified by `column_name` in the field definition is set to null. If any field condition evaluates to `FALSE`, then the column is set to the appropriate value as normally occurs according to the field definition. + +`PRESERVE BLANKS` + + The `PRESERVE BLANKS` option works only with the `OPTIONALLY ENCLOSED BY` clause and retains leading and trailing whitespaces for both delimited and predetermined size fields. + + In case of `NO PRESERVE BLANKS`, if the fields are delimited, then only leading whitespaces are omitted. If any trailing whitespaces are present, they are left intact. In the case of predetermined-sized fields with `NO PRESERVE BLANKS`, the trailing whitespaces are omitted, and any leading whitespaces are left intact. + + !!! Note + If you don't provide `PRESERVE BLANKS` or `NO PRESERVE BLANKS`, then the behavior defaults to `NO PRESERVE BLANKS`. This option doesn't work for ideographic whitespaces. + +`expr` + + A SQL expression returning a scalar value that's type-compatible with the column data type to which it's assigned in a field definition. Use double quotes around `expr`. `expr` can contain a reference to any column in the field list except for fields with the `FILLER` clause. Prefix the column name using a colon (`:`). + + `expr` can also consist of a SQL `SELECT` statement. If you use a `SELECT` statement: + +- Enclose the `SELECT` statement in parentheses, that is, `(SELECT ...)`. +- The select list must consist of one expression following the `SELECT` keyword. +- The result set must not return more than one row. If no rows are returned, then the returned value of the resulting expression is null. + + The following is the syntax for a `SELECT` statement: + + ```sql + "(SELECT [ FROM [ WHERE ] ])" + ``` + + !!! Note + Omitting the `FROM table_list` clause isn't compatible with Oracle databases. If you don't need to specify any tables, using the `FROM DUAL` clause is compatible with Oracle databases. + diff --git a/product_docs/docs/epas/15/database_administration/10_edb_resource_manager/edb_resource_manager_system_catalogs.mdx b/product_docs/docs/epas/15/reference/database_administrator_reference/edb_resource_manager_system_catalogs.mdx similarity index 94% rename from product_docs/docs/epas/15/database_administration/10_edb_resource_manager/edb_resource_manager_system_catalogs.mdx rename to product_docs/docs/epas/15/reference/database_administrator_reference/edb_resource_manager_system_catalogs.mdx index fbb3e32661a..1787626a201 100644 --- a/product_docs/docs/epas/15/database_administration/10_edb_resource_manager/edb_resource_manager_system_catalogs.mdx +++ b/product_docs/docs/epas/15/reference/database_administrator_reference/edb_resource_manager_system_catalogs.mdx @@ -1,6 +1,8 @@ --- title: "System catalogs" description: "Describes the system catalogs that store the resource group information used by EDB Resource Manager" +redirects: + - ../../../database_administration/10_edb_resource_manager/edb_resource_manager_system_catalogs/ --- System catalogs store the resource group information used by EDB Resource Manager. From 27f524d377e1ddef4b9f97a71d25c278c1461b59 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 18 Jul 2023 12:34:04 -0400 Subject: [PATCH 04/29] Edits to failover slots content --- .../pg_extensions/pg_failover_slots/index.mdx | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/advocacy_docs/pg_extensions/pg_failover_slots/index.mdx b/advocacy_docs/pg_extensions/pg_failover_slots/index.mdx index 64282135bb0..0653cc7f54f 100644 --- a/advocacy_docs/pg_extensions/pg_failover_slots/index.mdx +++ b/advocacy_docs/pg_extensions/pg_failover_slots/index.mdx @@ -10,13 +10,18 @@ directoryDefaults: product: PG Failover Slots --- -PG Failover Slots (pg_failover_slots) is an extension released as open source software under the PostgreSQL LICENSE. If you have logical replication publications on Postgres databases that are also part of a streaming replication architecture, +PG Failover Slots (pg_failover_slots) is an extension released as open source software under the PostgreSQL License. If you have logical replication publications on Postgres databases that are also part of a streaming replication architecture, PG Failover Slots avoids the need for you to reseed your logical replication tables when a new standby gets promoted to primary. -Since the replication slot used by logical replication is only maintained on the primary node, downstream subscribers don't receive any new changes from the newly promoted primary until the slot is created on the newly promoted primary. Picking up logical replication changes from the newly promoted standby is unsafe because the information that includes which data a subscriber has confirmed receiving and which log data still needs to be retained for the subscriber will have been lost, resulting in an unknown gap in data. PG Failover Slots makes logical replication slots usable across a physical failover using the following features: +Since the replication slot used by logical replication is maintained only on the primary node, downstream subscribers don't receive any new changes from the newly promoted primary until the slot is created on the newly promoted primary. Picking up logical replication changes from the newly promoted standby is unsafe because THE following information will be lost: +- The data a subscriber confirmed receiving +- The log data that still needs to be retained for the subscriber -- Copies any missing replication slots from the primary to the standby -- Removes any slots from the standby that aren't found on the primary -- Periodically synchronizes the position of slots on the standby based on the primary -- Ensures that selected standbys receive data before any of the logical slot walsenders can send data to consumers +The result is in an unknown gap in data. +PG Failover Slots makes logical replication slots usable across a physical failover by: + +- Copying any missing replication slots from the primary to the standby +- Removing any slots from the standby that aren't found on the primary +- Periodically synchronizing the position of slots on the standby based on the primary +- Ensuring that selected standbys receive data before any of the logical slot walsenders can send data to consumers From fa3225443fc975feb1a9561c416d8f452b731c1d Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Tue, 18 Jul 2023 12:57:45 -0400 Subject: [PATCH 05/29] absolute to relative --- product_docs/docs/pem/9/certificates/index.mdx | 14 +++++++------- .../9/certificates/replacing_ssl_certificates.mdx | 2 +- product_docs/docs/pem/9/changing_default_port.mdx | 4 ++-- ...e_pem_server_to_use_kerberos_authentication.mdx | 2 +- ...e_pem_server_to_use_windows_kerberos_server.mdx | 2 +- product_docs/docs/pem/9/considerations/index.mdx | 2 +- ...em_server_and_apache_web_server_preferences.mdx | 8 ++++---- .../pem/9/considerations/pem_pgbouncer/index.mdx | 2 +- .../apache_httpd_security_configuration.mdx | 4 ++-- .../pem_application_configuration.mdx | 6 +++--- .../configuring_the_pem_server_on_linux.mdx | 2 +- .../docs/pem/9/installing/prerequisites.mdx | 2 +- product_docs/docs/pem/9/monitoring_BDR_nodes.mdx | 2 +- .../pem_remote_monitoring.mdx | 4 ++-- product_docs/docs/pem/9/pem_architecture.mdx | 4 ++-- product_docs/docs/pem/9/pem_query_tool.mdx | 2 +- product_docs/docs/pem/9/pem_web_interface.mdx | 10 +++++----- .../tuning_performance/performance_diagnostic.mdx | 2 +- .../docs/pem/9/upgrading/moving_pem_server.mdx | 2 +- 19 files changed, 38 insertions(+), 38 deletions(-) diff --git a/product_docs/docs/pem/9/certificates/index.mdx b/product_docs/docs/pem/9/certificates/index.mdx index 38a9c95f589..1f4aa889d99 100644 --- a/product_docs/docs/pem/9/certificates/index.mdx +++ b/product_docs/docs/pem/9/certificates/index.mdx @@ -49,11 +49,11 @@ You can replace the PEM self-signed SSL certificates and keys with the trusted C ### How PEM self-signed SSL certificates work -The PEM server configuration script generates self-signed SSL certificate and key files for the PEM backend database server. The backend database server uses these certificates and keys to authenticate and encrypt the agent connections. Each certificate has an expiry date. Regenerate the certificates when they near expiration. For more information, see [Regenerating server self-signed SSL certificates](/pem/latest/certificates/replacing_ssl_certificates). +The PEM server configuration script generates self-signed SSL certificate and key files for the PEM backend database server. The backend database server uses these certificates and keys to authenticate and encrypt the agent connections. Each certificate has an expiry date. Regenerate the certificates when they near expiration. For more information, see [Regenerating server self-signed SSL certificates](/replacing_ssl_certificates). -The PEM agent connects to the PEM backend database server using the libpq interface, acting as a client of the backend database server. The agent self-signed SSL certificates and keys get generated during [agent registration](/pem/latest/registering_agent). PEM agent establishes the connection with the PEM backend database server using the self-signed SSL certificate and key files. +The PEM agent connects to the PEM backend database server using the libpq interface, acting as a client of the backend database server. The agent self-signed SSL certificates and keys get generated during [agent registration](../registering_agent). PEM agent establishes the connection with the PEM backend database server using the self-signed SSL certificate and key files. -Each agent has a unique identifier, and the agent certificates and keys have the corresponding identifier. Each certificate has an expiry date. Regenerate the certificates when they near expiration. For more information, see [Regenerating agent self-signed SSL certificates](/pem/latest/certificates/regenerating_agent_certificates). +Each agent has a unique identifier, and the agent certificates and keys have the corresponding identifier. Each certificate has an expiry date. Regenerate the certificates when they near expiration. For more information, see [Regenerating agent self-signed SSL certificates](/regenerating_agent_certificates). If required, you can use the same certificate for all agents rather than one certificate per agent. For more information, see [Generate common agent certificate and key pair](/pem/lates/certificates/#generate-a-common-agent-certificate-and-key-pair). @@ -178,7 +178,7 @@ Create a user, generate an agent certificate and key pair, and use them for all Replace the PEM self-signed SSL certificates and keys with certificates and keys signed by a trusted CA. -After obtaining the trusted CA certificates and keys, replace the [server](/pem/latest/certificates/#replace-the-self-signed-server-ssl-certificates-with-the-certificates-signed-by-the-trusted-ca) and [agent](/pem/latest/certificates/#replace-the-self-signed-agent-ssl-certificates-with-the-certificates-signed-by-the-trusted-ca) certificates and keys. +After obtaining the trusted CA certificates and keys, replace the [server](#replace-the-self-signed-server-ssl-certificates-with-the-certificates-signed-by-the-trusted-ca) and [agent](#replace-the-self-signed-agent-ssl-certificates-with-the-certificates-signed-by-the-trusted-ca) certificates and keys. ### Replace the self-signed server SSL certificates with the certificates signed by the trusted CA @@ -244,7 +244,7 @@ After obtaining the trusted CA certificates and keys, replace the [server](/pem/ !!! Note Don't restart the PEM server now. If you restart the PEM server, all the registered agents will stop working. -1. Replace each PEM agent SSL certificates with the trusted CA certificates. For more information, see these [instructions](/pem/latest/certificates/#replace-the-self-signed-agent-ssl-certificates-with-the-certificates-signed-by-the-trusted-ca). +1. Replace each PEM agent SSL certificates with the trusted CA certificates. For more information, see these [instructions](#replace-the-self-signed-agent-ssl-certificates-with-the-certificates-signed-by-the-trusted-ca). 1. Restart the PEM server. @@ -285,7 +285,7 @@ Replace the self-signed agent SSL certificates only after replacing the self-sig !!! Note If you prefer to use a single certificate for all PEM agents rather than one per agent, create a common Postgres user - and supply this username in place of `ID`. See [Generate a common agent certificate and key pair](/pem/latest/certificates/#generate-a-common-agent-certificate-and-key-pair). + and supply this username in place of `ID`. See [Generate a common agent certificate and key pair](#generate-a-common-agent-certificate-and-key-pair). 1. Ask your CA to sign the CSR and generate the agent certificate for you. @@ -361,7 +361,7 @@ Where: - `` is the ID of the agent you're testing, as defined in the file `/usr/edb/pem/agent/etc/agent.cfg`. !!! Note -If you used the instructions in [Generate a common agent certificate and key pair](/pem/latest/certificates/#generate-a-common-agent-certificate-and-key-pair) +If you used the instructions in [Generate a common agent certificate and key pair](#generate-a-common-agent-certificate-and-key-pair) you must set `PGUSER` to the common agent username. !!! diff --git a/product_docs/docs/pem/9/certificates/replacing_ssl_certificates.mdx b/product_docs/docs/pem/9/certificates/replacing_ssl_certificates.mdx index 7aaca767554..219ec212578 100644 --- a/product_docs/docs/pem/9/certificates/replacing_ssl_certificates.mdx +++ b/product_docs/docs/pem/9/certificates/replacing_ssl_certificates.mdx @@ -126,5 +126,5 @@ To replace the self-signed SSL certificates: Restarting the backend database server restarts the PEM server. -1. Regenerate each PEM agent's self-signed SSL certificates. For more information, see [Regenerating agent SSL certificates](/pem/latest/certificates/regenerating_agent_certificates). +1. Regenerate each PEM agent's self-signed SSL certificates. For more information, see [Regenerating agent SSL certificates](regenerating_agent_certificates). diff --git a/product_docs/docs/pem/9/changing_default_port.mdx b/product_docs/docs/pem/9/changing_default_port.mdx index 056b3c820e9..cbbb6f419bd 100644 --- a/product_docs/docs/pem/9/changing_default_port.mdx +++ b/product_docs/docs/pem/9/changing_default_port.mdx @@ -35,7 +35,7 @@ By default, the 8443 port is assigned for the web services at the time of config sudo systemctl restart httpd ``` -You can now access the PEM web interface using your port. For more details, see [Accessing the web interface](/pem/latest/pem_web_interface/). +You can now access the PEM web interface using your port. For more details, see [Accessing the web interface](pem_web_interface). ## For Debian and Ubuntu @@ -51,4 +51,4 @@ You can now access the PEM web interface using your port. For more details, see sudo systemctl restart apache2 ``` -You can now access the PEM web interface using your port. For more details, see [Accessing the web interface](/pem/latest/pem_web_interface/). +You can now access the PEM web interface using your port. For more details, see [Accessing the web interface](pem_web_interface). diff --git a/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx b/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx index 5c5587f7b34..2c54a98aa69 100644 --- a/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx +++ b/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx @@ -17,7 +17,7 @@ For example, if the realm on Kerberos server is `edbpem.org`, then you can set t ## 1. Install Kerberos, the PEM server, and the PEM backend database -Install Kerberos on the machine that functions as the authentication server. Install the PEM server on a separate machine. For more information, see [Installing the PEM Server](/pem/latest/installing/). +Install Kerberos on the machine that functions as the authentication server. Install the PEM server on a separate machine. For more information, see [Installing the PEM Server](../../installing/). Install the PEM backend database (Postgres/EDB Postgres Advanced Server) on the same machine as the PEM server or on a different one. For more information, see the Installation steps on [EDB Docs website](https://www.enterprisedb.com/docs). diff --git a/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx b/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx index 6f8abeca6e7..1fd3e75a9be 100644 --- a/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx +++ b/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx @@ -19,7 +19,7 @@ Perform the following installations: - Install Active Directory on the Windows server (domain controller) that functions as the authentication server. Also, configure the Active Directory domain services to use Kerberos authentication, and then start it. -- Install the PEM server on a separate Linux machine. For more information, see [Installing the PEM server](/pem/latest/installing/). +- Install the PEM server on a separate Linux machine. For more information, see [Installing the PEM server](../../installing/). - Install the PEM backend database (Postgres/EDB Postgres Advanced Server) on the same Linux machine as the PEM server or a different one. For more information, see the installation steps on the [EDB Docs website](https://www.enterprisedb.com/docs). diff --git a/product_docs/docs/pem/9/considerations/index.mdx b/product_docs/docs/pem/9/considerations/index.mdx index c9d3c870f64..257a4bf71fd 100644 --- a/product_docs/docs/pem/9/considerations/index.mdx +++ b/product_docs/docs/pem/9/considerations/index.mdx @@ -13,7 +13,7 @@ There are a number of things to consider before deploying Postgres Enterprise Ma | Considerations | Implementation instructions | | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | -| Is a standalone server sufficient or do you need a high availability architecture? | [Installing the server](/pem/latest/installing/) or [Deploying high availability](setup_ha_using_efm/) | +| Is a standalone server sufficient or do you need a high availability architecture? | [Installing the server](../installing/) or [Deploying high availability](setup_ha_using_efm/) | | Do you need to implement connection pooling? | [Deploying connection pooling](pem_pgbouncer/) | | What type of authentication to use? | [Authentication options](authentication_options/) | | What actions should you take to avoid security vulnerabilities? | [Securing your deployment](pem_security_best_practices/) | diff --git a/product_docs/docs/pem/9/considerations/installing_pem_server_and_apache_web_server_preferences.mdx b/product_docs/docs/pem/9/considerations/installing_pem_server_and_apache_web_server_preferences.mdx index 61e98ad83ec..ba8f509a190 100644 --- a/product_docs/docs/pem/9/considerations/installing_pem_server_and_apache_web_server_preferences.mdx +++ b/product_docs/docs/pem/9/considerations/installing_pem_server_and_apache_web_server_preferences.mdx @@ -13,19 +13,19 @@ During the PEM server installation, you can specify your hosting preferences for ## PEM server and Apache web server on separate hosts -1. Install the PEM server on both the hosts. See [Installing the PEM server](/pem/latest/installing/). +1. Install the PEM server on both the hosts. See [Installing the PEM server](../installing/). 2. Configure the PEM server host by selecting the **Database** option on the first host. 3. Configure an Apache web server by selecting the **Web Services** option on the second host. -For more information about configuring a PEM server, see [Configuring the PEM server on Linux platforms](/pem/latest/installing/configuring_the_pem_server_on_linux/). +For more information about configuring a PEM server, see [Configuring the PEM server on Linux platforms](../installing/configuring_the_pem_server_on_linux/). !!! Note For production environments, best practice is to have the PEM server and Apache web server on separate hosts. ## PEM server and Apache web server on the same host -1. Install the PEM server. See [Installing the PEM server](/pem/latest/installing/). -2. Run the configuration script. Select the **Web Services and Database** option to install the PEM server and Apache web server on the same host. See [Configuring the PEM server on Linux](/pem/latest/installing/configuring_the_pem_server_on_linux/). +1. Install the PEM server. See [Installing the PEM server](../installing/). +2. Run the configuration script. Select the **Web Services and Database** option to install the PEM server and Apache web server on the same host. See [Configuring the PEM server on Linux](../installing/configuring_the_pem_server_on_linux/). !!! Note For nonproduction environments, best practice is to have the PEM server and Apache web server on same hosts. diff --git a/product_docs/docs/pem/9/considerations/pem_pgbouncer/index.mdx b/product_docs/docs/pem/9/considerations/pem_pgbouncer/index.mdx index a3a0bb0d6dc..3daf0667359 100644 --- a/product_docs/docs/pem/9/considerations/pem_pgbouncer/index.mdx +++ b/product_docs/docs/pem/9/considerations/pem_pgbouncer/index.mdx @@ -22,4 +22,4 @@ You can use pgBouncer as a connection pooler for limiting the number of connecti - Configuring pgBouncer provides detailed information about configuring pgBouncer to make it work with the PEM database server. - Configuring the PEM agent provides detailed information about configuring a PEM agent to connect to pgBouncer. -For detailed information about using the PEM web interface, see the [Accessing the web interface ](/pem/latest/pem_web_interface). \ No newline at end of file +For detailed information about using the PEM web interface, see the [Accessing the web interface ](../pem_web_interface). \ No newline at end of file diff --git a/product_docs/docs/pem/9/considerations/pem_security_best_practices/apache_httpd_security_configuration.mdx b/product_docs/docs/pem/9/considerations/pem_security_best_practices/apache_httpd_security_configuration.mdx index 7071b278b25..3fcbda35914 100644 --- a/product_docs/docs/pem/9/considerations/pem_security_best_practices/apache_httpd_security_configuration.mdx +++ b/product_docs/docs/pem/9/considerations/pem_security_best_practices/apache_httpd_security_configuration.mdx @@ -213,7 +213,7 @@ By default, PEM sets `X-XSS-Protection to "1; mode=block"` in the application co To apply the changes, restart the Apache service. -For detailed information on the `config.py` file, see [Managing configuration settings](/pem/latest/managing_configuration_settings/). +For detailed information on the `config.py` file, see [Managing configuration settings](../../managing_configuration_settings/). ### Cookie security @@ -242,4 +242,4 @@ Cookies are small packets of data that a server sends to your browser to store c To apply the changes, restart the Apache service. - For detailed information on `config.py` file, see [Managing Configuration Settings](/pem/latest/managing_configuration_settings/). + For detailed information on `config.py` file, see [Managing Configuration Settings](../../managing_configuration_settings/). diff --git a/product_docs/docs/pem/9/considerations/pem_security_best_practices/pem_application_configuration.mdx b/product_docs/docs/pem/9/considerations/pem_security_best_practices/pem_application_configuration.mdx index 7bb37ba4e48..8f5bd8897ed 100644 --- a/product_docs/docs/pem/9/considerations/pem_security_best_practices/pem_application_configuration.mdx +++ b/product_docs/docs/pem/9/considerations/pem_security_best_practices/pem_application_configuration.mdx @@ -24,7 +24,7 @@ USER_INACTIVITY_TIMEOUT = 900 To apply the changes, restart the Apache service. -For detailed information on the `config.py` file, see [Managing Configuration Settings](/pem/latest/managing_configuration_settings/). +For detailed information on the `config.py` file, see [Managing Configuration Settings](../../managing_configuration_settings/). ## RestAPI header customization @@ -82,7 +82,7 @@ CREATE ROLE user_sql_profiler WITH LOGIN NOSUPERUSER NOCREATEDB NOCREATEROLE INH GRANT pem_user, pem_comp_sqlprofiler TO user_sql_profiler; ``` -For detailed information on roles, see [PEM Roles](/pem/latest/managing_pem_server/#using-pem-predefined-roles-to-manage-access-to-pem-functionality). +For detailed information on roles, see [PEM Roles](../../managing_pem_server/#using-pem-predefined-roles-to-manage-access-to-pem-functionality). ## SQL/Protect plugin @@ -95,7 +95,7 @@ Attackers can perpetrate SQL injection attacks with several different techniques !!! Note This plugin works only on the EDB Postgres Advanced Server server, so this is useful only when your PEM database is hosted on the EDB Postgres Advanced Server server. -For detailed information about the SQL Profiler plugin, see [SQL Profiler](/pem/latest/profiling_workloads/). +For detailed information about the SQL Profiler plugin, see [SQL Profiler](../../profiling_workloads/). ## Password management 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 7deed55fd08..370ef1e2387 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 @@ -58,4 +58,4 @@ After configuring the PEM server, you can access the PEM web interface in your b https://:8443/pem ``` -By default, the web services listen on port 8443. To change the port, see [Changing the default port](/pem/latest/changing_default_port). +By default, the web services listen on port 8443. To change the port, see [Changing the default port](../changing_default_port). diff --git a/product_docs/docs/pem/9/installing/prerequisites.mdx b/product_docs/docs/pem/9/installing/prerequisites.mdx index 26b1ec90678..b27ac53b8da 100644 --- a/product_docs/docs/pem/9/installing/prerequisites.mdx +++ b/product_docs/docs/pem/9/installing/prerequisites.mdx @@ -13,7 +13,7 @@ To install a Postgres Enterprise Manager server on Linux, you may need to perfor - To allow the new superuser to connect using password authentication, add a line `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication. - - If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). + - If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](../managing_database_server/#modifying-the-pg_hbaconf-file). - If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). diff --git a/product_docs/docs/pem/9/monitoring_BDR_nodes.mdx b/product_docs/docs/pem/9/monitoring_BDR_nodes.mdx index 6fa753553b3..128c0c3d17c 100644 --- a/product_docs/docs/pem/9/monitoring_BDR_nodes.mdx +++ b/product_docs/docs/pem/9/monitoring_BDR_nodes.mdx @@ -7,7 +7,7 @@ EDB Postgres Distributed provides multi-master replication and data distribution You can configure PEM to display status information about one or more EDB Postgres Distributed database nodes using dashboards in PEM version 8.1.0 and EDB Postgres Distributed version 3.7.9 and later. -To configure PEM to monitor EDB Postgres Distributed database nodes, use the PEM web client to create a server definition. Use the tabs on the [New Server Registration](/pem/latest/registering_database_server/#manually-registering-a-database-server) dialog box to specify general connection properties for the EDB Postgres Distributed database node with the following exceptions: +To configure PEM to monitor EDB Postgres Distributed database nodes, use the PEM web client to create a server definition. Use the tabs on the [New Server Registration](registering_database_server/#manually-registering-a-database-server) dialog box to specify general connection properties for the EDB Postgres Distributed database node with the following exceptions: - Specify the EDB Postgres Distributed-enabled database name in the **Database** field of the **PEM Agent** tab. diff --git a/product_docs/docs/pem/9/monitoring_performance/pem_remote_monitoring.mdx b/product_docs/docs/pem/9/monitoring_performance/pem_remote_monitoring.mdx index ec5b38684a3..bf23e8f6c81 100644 --- a/product_docs/docs/pem/9/monitoring_performance/pem_remote_monitoring.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/pem_remote_monitoring.mdx @@ -11,8 +11,8 @@ To remotely monitor a Postgres cluster with PEM, you must register the cluster w The following scenarios require remote monitoring using PEM: -- [Postgres cluster running on AWS RDS](/pem/latest/registering_database_server/#registering-postgres-clusters-on-aws) -- [Postgres cluster running on BigAnimal](../../../biganimal/latest/using_cluster/05_monitoring_and_logging/) +- [Postgres cluster running on AWS RDS](../../registering_database_server/#registering-postgres-clusters-on-aws) +- [Postgres cluster running on BigAnimal](/biganimal/latest/using_cluster/05_monitoring_and_logging/) PEM remote monitoring supports: diff --git a/product_docs/docs/pem/9/pem_architecture.mdx b/product_docs/docs/pem/9/pem_architecture.mdx index 90d2dd3a855..22dac966da5 100644 --- a/product_docs/docs/pem/9/pem_architecture.mdx +++ b/product_docs/docs/pem/9/pem_architecture.mdx @@ -89,13 +89,13 @@ Once configured, each agent collects statistics and other information on the hos - Table access statistics - Table and index sizes -For a list of PEM probes, see [Probes](/pem/latest/monitoring_performance/probes/). +For a list of PEM probes, see [Probes](monitoring_performance/probes/). By default, the PEM agent bound to the database server collects the OS/database monitoring statistics and also runs any scheduled tasks/jobs for that particular database server, storing data in the `pem` database on the PEM server. The alert processing, SNMP/SMTP spoolers, and Nagios spooler data is stored in the `pem` database on the PEM server and is then processed by the PEM agent on the PEM host by default. However, you can enable processing by other PEM Agents by adjusting the SNMP/SMTP and Nagios parameters of the PEM agents. -For more information about these parameters, see [Server configuration](/pem/latest/managing_pem_server/#server-configuration-parameters---reference). +For more information about these parameters, see [Server configuration](managing_pem_server/#server-configuration-parameters---reference). ### PEM web client diff --git a/product_docs/docs/pem/9/pem_query_tool.mdx b/product_docs/docs/pem/9/pem_query_tool.mdx index 6d50f99e1fb..02635bdb9a4 100644 --- a/product_docs/docs/pem/9/pem_query_tool.mdx +++ b/product_docs/docs/pem/9/pem_query_tool.mdx @@ -16,7 +16,7 @@ You can access the Query tool by selecting **Tools > Query tool** or through the - Issue ad hoc SQL queries. - Execute arbitrary SQL commands. -- Edit the result set of a SELECT query if it's [updatable](/pem/latest/pem_query_tool/). +- Edit the result set of a SELECT query if it's [updatable](#data-output-tab). - Configure and display current connection and transaction status. - Save the data displayed in the output panel to a CSV file. - Review the execution plan of a SQL statement in either text, graphical, or table format (similar to ). diff --git a/product_docs/docs/pem/9/pem_web_interface.mdx b/product_docs/docs/pem/9/pem_web_interface.mdx index 6065d07937c..a9acc238663 100644 --- a/product_docs/docs/pem/9/pem_web_interface.mdx +++ b/product_docs/docs/pem/9/pem_web_interface.mdx @@ -85,7 +85,7 @@ Context menu options can include one or more of the following selections: | **Backup Server** | Open the [Backup Server](#tools-menu) dialog box to back up a server. | | **Connect Server** | Establish a connection with the selected server. | | **Create** | Access a context menu that provides context-sensitive selections. Your selection opens a Create dialog box for creating a new object. | -| **CREATE Script** | Open the [Query tool](/pem/latest/pem_query_tool/) to edit or view the CREATE script. | +| **CREATE Script** | Open the [Query tool](pem_query_tool) to edit or view the CREATE script. | | **Dashboards** | Select for quick access to PEM dashboards. | | **Delete/Drop** | Delete the currently selected object from the server. | | **Disconnect Database** | Terminate a database connection. | @@ -107,7 +107,7 @@ The context-sensitive menus associated with Tables and nested Table nodes provid | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | **Import/Export** | Open the Import/Export dialog box to import data to or export data from the selected table. | | **Reset Statistics** | Reset statistics for the selected table. | -| **Scripts** | Open the [Query tool](/pem/latest/pem_query_tool/) to edit or view the selected script from the flyout menu. | +| **Scripts** | Open the [Query tool](pem_query_tool) to edit or view the selected script from the flyout menu. | | **Truncate** | Remove all rows from a table. | | **Truncate Cascade** | Remove all rows from a table and its child tables. | | **View First 100 Rows** | Access the data grid that displays the first 100 rows of the selected table. | @@ -121,8 +121,8 @@ The main panel of the PEM client contains a collection of tabs that display info The **Dashboard** tab is context sensitive. When you navigate to the **Dashboard** tab from a server group or the PEM Agents node, the EDB Postgres Welcome window opens, where you can: -- Select the **Add New Server** icon to open the [Create - Server dialog box](/pem/latest/registering_database_server/#manually-registering-a-database-server) to define a connection to a server. -- Select the **Configure PEM** icon to open the [Server Configuration dialog box](/pem/latest/managing_pem_server/#server-configuration) and modify server parameters. +- Select the **Add New Server** icon to open the [Create - Server dialog box](registering_database_server/#manually-registering-a-database-server) to define a connection to a server. +- Select the **Configure PEM** icon to open the [Server Configuration dialog box](managing_pem_server/#server-configuration) and modify server parameters. - Select the **Getting Started** icon to open a new tab, displaying the PEM Getting Started section at the EnterpriseDB website. - Select the **EDB Website** icon to navigate to the home page of the EnterpriseDB website. The EnterpriseDB website features news about upcoming events and other projects. - Select the **PostgreSQL Website** icon to navigate to the PostgreSQL project website. The PostgreSQL site features news about recent releases and other project information. @@ -187,7 +187,7 @@ The **Dependents** tab displays a table of objects that depend on the object cur - The **Name** field specifies the identifying name for the dependent object. - The **Restriction** field describes the dependency relationship between the currently selected object and the parent. -Navigate to the **Monitoring** tab to access information presented on [PEM dashboards](/pem/latest/monitoring_performance/dashboards/). Dashboards display statistical information about the objects monitored by the PEM server. +Navigate to the **Monitoring** tab to access information presented on [PEM dashboards](monitoring_performance/dashboards/). Dashboards display statistical information about the objects monitored by the PEM server. PEM opens additional tabs when you access PEM functionality through the Management or Tools dialog boxes. Right-click the current tab and select from a context menu that allows you to customize the display for your working style: diff --git a/product_docs/docs/pem/9/tuning_performance/performance_diagnostic.mdx b/product_docs/docs/pem/9/tuning_performance/performance_diagnostic.mdx index b6c80ec2c2b..4859597386d 100644 --- a/product_docs/docs/pem/9/tuning_performance/performance_diagnostic.mdx +++ b/product_docs/docs/pem/9/tuning_performance/performance_diagnostic.mdx @@ -43,7 +43,7 @@ To analyze the wait states data on multiple levels, narrow down the data you sel CREATE EXTENSION edb_wait_states; ``` -- If you want to access the Performance Diagnostic dashboard as a user without superuser privileges, specific [roles](/pem/latest/managing_pem_server/#using-pem-predefined-roles-to-manage-access-to-pem-functionality) must be granted to the user based on the server to which the user is connected or logged into: +- If you want to access the Performance Diagnostic dashboard as a user without superuser privileges, specific [roles](../../managing_pem_server/#using-pem-predefined-roles-to-manage-access-to-pem-functionality) must be granted to the user based on the server to which the user is connected or logged into: - Grant `pem_comp_performance_diagnostic` role to the user (`test1` in this example), who is logged into the PEM server. diff --git a/product_docs/docs/pem/9/upgrading/moving_pem_server.mdx b/product_docs/docs/pem/9/upgrading/moving_pem_server.mdx index 9279cba1928..76457242f7a 100644 --- a/product_docs/docs/pem/9/upgrading/moving_pem_server.mdx +++ b/product_docs/docs/pem/9/upgrading/moving_pem_server.mdx @@ -20,7 +20,7 @@ Before starting the server migration, make sure that the firewalls between the s The backend database of the target server can have a different version or type from the backend database of the source. If the new PEM server doesn't reside on the same type of backend database as the original server, you must ensure that the same version of the sslutils extension is installed on the new server host. The version of sslutils that's distributed with the PEM installers is freely available for download from the [EDB website](https://www.enterprisedb.com/downloads/modified-gpl-source-code). - For information about installing the PEM server or the sslutils extension, see the [PEM installation steps](/pem/latest/). + For information about installing the PEM server or the sslutils extension, see the [PEM installation steps](../installing). 2. Drop existing schemas from the new PEM server. From a0b187994717f235226137f335bd7fa6a5a584ce Mon Sep 17 00:00:00 2001 From: francoughlin Date: Tue, 18 Jul 2023 14:54:21 -0400 Subject: [PATCH 06/29] Moving content to reference branch Relocating topics from application programming branches to the Reference branch --- .../15/application_programming/epas_compat_spl/index.mdx | 2 ++ .../01_basic_spl_elements/02_case_sensitivity.mdx | 1 + .../01_basic_spl_elements/03_identifiers.mdx | 1 + .../01_basic_spl_elements/04_qualifiers.mdx | 1 + .../01_basic_spl_elements/05_constants.mdx | 1 + .../06_user_defined_pl_sql_subtypes.mdx | 1 + .../01_basic_spl_elements/07_character.mdx | 1 + .../01_basic_spl_elements/index.mdx | 1 + .../04_basic_statements/01_assignment.mdx | 1 + .../04_basic_statements/02_delete.mdx | 1 + .../04_basic_statements/03_insert.mdx | 1 + .../04_basic_statements/04_null.mdx | 1 + .../05_using_the_returning_into_clause.mdx | 3 ++- .../04_basic_statements/06_select_into.mdx | 1 + .../04_basic_statements/07_update.mdx | 1 + .../08_obtaining_the_result_status.mdx | 1 + .../04_basic_statements/index.mdx | 1 + .../stored_procedural_language_reference/index.mdx | 8 ++++++++ 18 files changed, 27 insertions(+), 1 deletion(-) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/01_basic_spl_elements/02_case_sensitivity.mdx (90%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/01_basic_spl_elements/03_identifiers.mdx (87%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/01_basic_spl_elements/04_qualifiers.mdx (96%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/01_basic_spl_elements/05_constants.mdx (89%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/01_basic_spl_elements/06_user_defined_pl_sql_subtypes.mdx (98%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/01_basic_spl_elements/07_character.mdx (88%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/01_basic_spl_elements/index.mdx (91%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/04_basic_statements/01_assignment.mdx (93%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/04_basic_statements/02_delete.mdx (95%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/04_basic_statements/03_insert.mdx (97%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/04_basic_statements/04_null.mdx (90%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/04_basic_statements/05_using_the_returning_into_clause.mdx (97%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/04_basic_statements/06_select_into.mdx (97%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/04_basic_statements/07_update.mdx (96%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/04_basic_statements/08_obtaining_the_result_status.mdx (93%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/04_basic_statements/index.mdx (92%) create mode 100644 product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/index.mdx diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/index.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/index.mdx index c2a3a4e08a1..d1c30b9d7d6 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/index.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/index.mdx @@ -15,5 +15,7 @@ EDB Postgres Advanced Server's stored procedural language (SPL) is a highly prod - The use of reusable code - Ease of use +For reference information about the SPL program types, programming statements, control structures, collection types, and collection methods, see [Stored procedural language (SPL) reference](/epas/latest/reference/stored_procedural_language_reference/). + diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/02_case_sensitivity.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/02_case_sensitivity.mdx similarity index 90% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/02_case_sensitivity.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/02_case_sensitivity.mdx index f6eb6583930..4b55946a199 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/02_case_sensitivity.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/02_case_sensitivity.mdx @@ -2,6 +2,7 @@ title: "Case sensitivity" redirects: - ../../../../epas_compat_spl/01_basic_spl_elements/02_case_sensitivity #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/02_case_sensitivity/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/03_identifiers.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/03_identifiers.mdx similarity index 87% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/03_identifiers.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/03_identifiers.mdx index 274ab007ad2..5f9a45c54b6 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/03_identifiers.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/03_identifiers.mdx @@ -2,6 +2,7 @@ title: "Identifiers" redirects: - ../../../../epas_compat_spl/01_basic_spl_elements/03_identifiers #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/03_identifiers/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/04_qualifiers.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/04_qualifiers.mdx similarity index 96% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/04_qualifiers.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/04_qualifiers.mdx index 1a8df6ff6ff..1d023e02939 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/04_qualifiers.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/04_qualifiers.mdx @@ -2,6 +2,7 @@ title: "Qualifiers" redirects: - ../../../../epas_compat_spl/01_basic_spl_elements/04_qualifiers #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/04_qualifiers/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/05_constants.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/05_constants.mdx similarity index 89% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/05_constants.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/05_constants.mdx index 7c1d52562fa..ae454cc0ee1 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/05_constants.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/05_constants.mdx @@ -5,6 +5,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.041.html" redirects: - ../../../../epas_compat_spl/01_basic_spl_elements/05_constants #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/05_constants/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/06_user_defined_pl_sql_subtypes.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/06_user_defined_pl_sql_subtypes.mdx similarity index 98% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/06_user_defined_pl_sql_subtypes.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/06_user_defined_pl_sql_subtypes.mdx index 2f3166d7403..25519f19f86 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/06_user_defined_pl_sql_subtypes.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/06_user_defined_pl_sql_subtypes.mdx @@ -6,6 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.142.html" redirects: - ../../../../epas_compat_spl/01_basic_spl_elements/06_user_defined_pl_sql_subtypes #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/06_user_defined_pl_sql_subtypes/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/07_character.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/07_character.mdx similarity index 88% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/07_character.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/07_character.mdx index dad6f09125d..4a74441d664 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/07_character.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/07_character.mdx @@ -2,6 +2,7 @@ title: "Character set" redirects: - ../../../../epas_compat_spl/01_basic_spl_elements/07_character #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/07_character/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/index.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/index.mdx similarity index 91% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/index.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/index.mdx index 3257af6cca8..f094cfdfd97 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/01_basic_spl_elements/index.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/index.mdx @@ -7,6 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.141.html" redirects: - ../../../epas_compat_spl/01_basic_spl_elements #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/01_assignment.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/01_assignment.mdx similarity index 93% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/01_assignment.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/01_assignment.mdx index 2a6144a652f..a970275632c 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/01_assignment.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/01_assignment.mdx @@ -2,6 +2,7 @@ title: "Assignment" redirects: - ../../../../epas_compat_spl/04_basic_statements/01_assignment #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/01_assignment/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/02_delete.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/02_delete.mdx similarity index 95% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/02_delete.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/02_delete.mdx index d1a5c506a1b..21afb630e1f 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/02_delete.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/02_delete.mdx @@ -2,6 +2,7 @@ title: "DELETE" redirects: - ../../../../epas_compat_spl/04_basic_statements/02_delete #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/02_delete/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/03_insert.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert.mdx similarity index 97% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/03_insert.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert.mdx index 79fbd89767c..366af5bad02 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/03_insert.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert.mdx @@ -2,6 +2,7 @@ title: "INSERT" redirects: - ../../../../epas_compat_spl/04_basic_statements/03_insert #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/03_insert/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/04_null.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/04_null.mdx similarity index 90% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/04_null.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/04_null.mdx index 4959f47c7e4..07c6f104a24 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/04_null.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/04_null.mdx @@ -2,6 +2,7 @@ title: "NULL" redirects: - ../../../../epas_compat_spl/04_basic_statements/04_null #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/04_null/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/05_using_the_returning_into_clause.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause.mdx similarity index 97% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/05_using_the_returning_into_clause.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause.mdx index ed7743b5723..5d3c80c27bb 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/05_using_the_returning_into_clause.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause.mdx @@ -1,7 +1,8 @@ --- -title: "Using the RETURNING INTO clause" +title: "RETURNING INTO" redirects: - ../../../../epas_compat_spl/04_basic_statements/05_using_the_returning_into_clause #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/05_using_the_returning_into_clause/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/06_select_into.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into.mdx similarity index 97% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/06_select_into.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into.mdx index 2c773bf4515..d7f22ffa36a 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/06_select_into.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into.mdx @@ -2,6 +2,7 @@ title: "SELECT INTO" redirects: - ../../../../epas_compat_spl/04_basic_statements/06_select_into #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/06_select_into/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/07_update.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/07_update.mdx similarity index 96% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/07_update.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/07_update.mdx index d16e40f60e5..22c9091aca4 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/07_update.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/07_update.mdx @@ -2,6 +2,7 @@ title: "UPDATE" redirects: - ../../../../epas_compat_spl/04_basic_statements/07_update #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/07_update/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/08_obtaining_the_result_status.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/08_obtaining_the_result_status.mdx similarity index 93% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/08_obtaining_the_result_status.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/08_obtaining_the_result_status.mdx index a453619b35e..52a025ccca9 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/08_obtaining_the_result_status.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/08_obtaining_the_result_status.mdx @@ -2,6 +2,7 @@ title: "Obtaining the result status" redirects: - ../../../../epas_compat_spl/04_basic_statements/08_obtaining_the_result_status #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/08_obtaining_the_result_status/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/index.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/index.mdx similarity index 92% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/index.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/index.mdx index eee0d309665..d0a02cc1758 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/04_basic_statements/index.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/index.mdx @@ -7,6 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.155.html" redirects: - ../../../epas_compat_spl/04_basic_statements #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/ --- diff --git a/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/index.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/index.mdx new file mode 100644 index 00000000000..9ef7783a817 --- /dev/null +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/index.mdx @@ -0,0 +1,8 @@ +--- +navTitle: SPL reference +title: "Stored procedural language (SPL) reference" +indexCards: simple +description: "Provides reference content about SPL procedures, functions, triggers, and packages" +--- + +EDB Postgres Advanced Server's stored procedural language (SPL) is a highly productive, procedural programming language for writing custom procedures, functions, triggers, and packages for EDB Postgres Advanced Server. \ No newline at end of file From 13f0b65cb5705d9a4274a6364ffa364e98c2a290 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Wed, 19 Jul 2023 10:27:21 -0400 Subject: [PATCH 07/29] fixed broken link --- product_docs/docs/pem/9/considerations/pem_pgbouncer/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/considerations/pem_pgbouncer/index.mdx b/product_docs/docs/pem/9/considerations/pem_pgbouncer/index.mdx index 3daf0667359..8a962aabf53 100644 --- a/product_docs/docs/pem/9/considerations/pem_pgbouncer/index.mdx +++ b/product_docs/docs/pem/9/considerations/pem_pgbouncer/index.mdx @@ -22,4 +22,4 @@ You can use pgBouncer as a connection pooler for limiting the number of connecti - Configuring pgBouncer provides detailed information about configuring pgBouncer to make it work with the PEM database server. - Configuring the PEM agent provides detailed information about configuring a PEM agent to connect to pgBouncer. -For detailed information about using the PEM web interface, see the [Accessing the web interface ](../pem_web_interface). \ No newline at end of file +For detailed information about using the PEM web interface, see the [Accessing the web interface ](../../pem_web_interface). \ No newline at end of file From ea02285827402b27c58f6fd14d6a8c85e699dffb Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 20 Jul 2023 10:23:22 -0400 Subject: [PATCH 08/29] typo in link --- product_docs/docs/pem/9/certificates/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/certificates/index.mdx b/product_docs/docs/pem/9/certificates/index.mdx index 1f4aa889d99..baaa04c71c8 100644 --- a/product_docs/docs/pem/9/certificates/index.mdx +++ b/product_docs/docs/pem/9/certificates/index.mdx @@ -55,7 +55,7 @@ The PEM agent connects to the PEM backend database server using the libpq interf Each agent has a unique identifier, and the agent certificates and keys have the corresponding identifier. Each certificate has an expiry date. Regenerate the certificates when they near expiration. For more information, see [Regenerating agent self-signed SSL certificates](/regenerating_agent_certificates). -If required, you can use the same certificate for all agents rather than one certificate per agent. For more information, see [Generate common agent certificate and key pair](/pem/lates/certificates/#generate-a-common-agent-certificate-and-key-pair). +If required, you can use the same certificate for all agents rather than one certificate per agent. For more information, see [Generate common agent certificate and key pair](#generate-a-common-agent-certificate-and-key-pair). For more information on using the SSL certificates to connect in Postgres, see [Securing TCP/IP connections with SSL](https://www.postgresql.org/docs/current/ssl-tcp.html). From 0e7859136193d7400af0ba95f751b1d419aa13cd Mon Sep 17 00:00:00 2001 From: francoughlin Date: Thu, 20 Jul 2023 13:39:07 -0400 Subject: [PATCH 09/29] Additional reference-based content moved to Reference branch Relocating topics from Application programming and Working with oracle data branches to the Reference branch --- .../ecpgplus_guide/03_using_embedded_sql.mdx | 2 +- .../05_building_executing_dynamic_sql_statements.mdx | 4 ++-- .../09_program_security/03_database_object_privileges.mdx | 2 +- .../10_collections/01_associative_arrays.mdx | 2 +- .../epas_compat_spl/10_collections/02_nested_tables.mdx | 8 ++++---- .../epas_compat_spl/10_collections/03_varrays.mdx | 6 +++--- .../epas_compat_spl/10_collections/about_collections.mdx | 2 +- .../epas_compat_spl/10_collections/index.mdx | 2 +- .../01_select_bulk_collect.mdx | 2 +- .../04_returning_bulk_collect.mdx | 2 +- .../15/application_programming/epas_compat_spl/index.mdx | 2 +- .../attribute_descriptions.mdx | 6 +++--- .../01_configuration_parameters/index.mdx | 2 +- .../05_edb_audit_logging/08_audit_log_archiving.mdx | 2 +- .../application_programmer_reference/07_reference.mdx | 4 ++-- .../04_basic_statements/02_delete.mdx | 2 +- .../04_basic_statements/03_insert.mdx | 2 +- .../05_using_the_returning_into_clause.mdx | 2 +- .../04_basic_statements/06_select_into.mdx | 2 +- .../04_basic_statements/07_update.mdx | 2 +- .../05_control_structures/01_if_statement/01_if_then.mdx | 1 + .../01_if_statement/02_if_then_else.mdx | 1 + .../01_if_statement/03_if_then_else_if.mdx | 1 + .../01_if_statement/04_if_then_elseif_else.mdx | 1 + .../05_control_structures/01_if_statement/index.mdx | 1 + .../05_control_structures/02_return_statement.mdx | 1 + .../05_control_structures/03_goto_statement.mdx | 1 + .../04_case_expression/01_selector_case_expression.mdx | 1 + .../04_case_expression/02_searched_case_expression.mdx | 1 + .../05_control_structures/04_case_expression/index.mdx | 1 + .../05_case_statement/01_selector_case_statement.mdx | 1 + .../05_case_statement/02_searched_case_statement.mdx | 1 + .../05_control_structures/05_case_statement/index.mdx | 1 + .../05_control_structures/06_loops/01_loop.mdx | 1 + .../05_control_structures/06_loops/02_exit.mdx | 1 + .../05_control_structures/06_loops/03_continue.mdx | 1 + .../05_control_structures/06_loops/04_while.mdx | 1 + .../06_loops/05_for_integer_variant.mdx | 3 ++- .../05_control_structures/06_loops/index.mdx | 1 + .../05_control_structures/07_exception_handling.mdx | 1 + .../05_control_structures/08_user_defined_exceptions.mdx | 1 + .../05_control_structures/09_pragma_exception_init.mdx | 1 + .../05_control_structures/10_raise_application_error.mdx | 3 ++- .../05_control_structures/index.mdx | 1 + .../11_collection_methods/01_count.mdx | 1 + .../11_collection_methods/02_deletes.mdx | 1 + .../11_collection_methods/03_exists.mdx | 1 + .../11_collection_methods/04_extend.mdx | 1 + .../11_collection_methods/05_first.mdx | 1 + .../11_collection_methods/06_last.mdx | 1 + .../11_collection_methods/07_limit.mdx | 1 + .../11_collection_methods/08_next.mdx | 1 + .../11_collection_methods/09_prior.mdx | 1 + .../11_collection_methods/10_trim.mdx | 1 + .../11_collection_methods/index.mdx | 1 + .../17_advanced_server_keywords.mdx | 1 + .../01_audit_logging_configuration_parameters.mdx | 6 +++--- .../01_dblink_ora_connect.mdx | 1 + .../02_dblink_ora_status.mdx | 1 + .../03_dblink_ora_disconnect.mdx | 1 + .../04_dblink_ora_record.mdx | 1 + .../05_dblink_ora_call.mdx | 1 + .../06_dblink_ora_exec.mdx | 1 + .../07_dblink_ora_copy.mdx | 1 + .../01_dblink_ora_functions_and_procedures/index.mdx | 1 + .../02_enhanced_compatibility_features.mdx | 2 +- 66 files changed, 79 insertions(+), 35 deletions(-) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/01_if_statement/01_if_then.mdx (92%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/01_if_statement/02_if_then_else.mdx (93%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/01_if_statement/03_if_then_else_if.mdx (96%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/01_if_statement/04_if_then_elseif_else.mdx (94%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/01_if_statement/index.mdx (84%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/02_return_statement.mdx (93%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/03_goto_statement.mdx (96%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/04_case_expression/01_selector_case_expression.mdx (96%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/04_case_expression/02_searched_case_expression.mdx (95%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/04_case_expression/index.mdx (91%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/05_case_statement/01_selector_case_statement.mdx (96%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/05_case_statement/02_searched_case_statement.mdx (96%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/05_case_statement/index.mdx (91%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/06_loops/01_loop.mdx (79%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/06_loops/02_exit.mdx (91%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/06_loops/03_continue.mdx (93%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/06_loops/04_while.mdx (92%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/06_loops/05_for_integer_variant.mdx (90%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/06_loops/index.mdx (90%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/07_exception_handling.mdx (98%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/08_user_defined_exceptions.mdx (97%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/09_pragma_exception_init.mdx (97%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/10_raise_application_error.mdx (92%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/05_control_structures/index.mdx (92%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/11_collection_methods/01_count.mdx (92%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/11_collection_methods/02_deletes.mdx (96%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/11_collection_methods/03_exists.mdx (93%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/11_collection_methods/04_extend.mdx (97%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/11_collection_methods/05_first.mdx (90%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/11_collection_methods/06_last.mdx (90%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/11_collection_methods/07_limit.mdx (90%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/11_collection_methods/08_next.mdx (93%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/11_collection_methods/09_prior.mdx (93%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/11_collection_methods/10_trim.mdx (95%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/11_collection_methods/index.mdx (92%) rename product_docs/docs/epas/15/{application_programming/epas_compat_spl => reference/application_programmer_reference/stored_procedural_language_reference}/17_advanced_server_keywords.mdx (99%) rename product_docs/docs/epas/15/{working_with_oracle_data/06_dblink_ora => reference/oracle_compatibility_reference}/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect.mdx (94%) rename product_docs/docs/epas/15/{working_with_oracle_data/06_dblink_ora => reference/oracle_compatibility_reference}/01_dblink_ora_functions_and_procedures/02_dblink_ora_status.mdx (82%) rename product_docs/docs/epas/15/{working_with_oracle_data/06_dblink_ora => reference/oracle_compatibility_reference}/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect.mdx (80%) rename product_docs/docs/epas/15/{working_with_oracle_data/06_dblink_ora => reference/oracle_compatibility_reference}/01_dblink_ora_functions_and_procedures/04_dblink_ora_record.mdx (84%) rename product_docs/docs/epas/15/{working_with_oracle_data/06_dblink_ora => reference/oracle_compatibility_reference}/01_dblink_ora_functions_and_procedures/05_dblink_ora_call.mdx (86%) rename product_docs/docs/epas/15/{working_with_oracle_data/06_dblink_ora => reference/oracle_compatibility_reference}/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec.mdx (84%) rename product_docs/docs/epas/15/{working_with_oracle_data/06_dblink_ora => reference/oracle_compatibility_reference}/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy.mdx (92%) rename product_docs/docs/epas/15/{working_with_oracle_data/06_dblink_ora => reference/oracle_compatibility_reference}/01_dblink_ora_functions_and_procedures/index.mdx (92%) diff --git a/product_docs/docs/epas/15/application_programming/ecpgplus_guide/03_using_embedded_sql.mdx b/product_docs/docs/epas/15/application_programming/ecpgplus_guide/03_using_embedded_sql.mdx index 606774105fe..7bd55410dbf 100644 --- a/product_docs/docs/epas/15/application_programming/ecpgplus_guide/03_using_embedded_sql.mdx +++ b/product_docs/docs/epas/15/application_programming/ecpgplus_guide/03_using_embedded_sql.mdx @@ -86,7 +86,7 @@ EXEC SQL END DECLARE SECTION; If you plan to precompile the code in `PROC` mode, you can omit the `BEGIN DECLARE…END DECLARE` section. For more information about declaring host variables, see [Declaring host variables](#declaring-host-variables). -The data type associated with each variable in the declaration section is a C data type. Data passed between the server and the client application must share a compatible data type. For more information about data types, see the [Supported C data types](07_reference/#supported-c-data-types). +The data type associated with each variable in the declaration section is a C data type. Data passed between the server and the client application must share a compatible data type. For more information about data types, see the [Supported C data types](/epas/latest/reference/application_programmer_reference/07_reference/). The next statement tells the server how to handle an error: diff --git a/product_docs/docs/epas/15/application_programming/ecpgplus_guide/05_building_executing_dynamic_sql_statements.mdx b/product_docs/docs/epas/15/application_programming/ecpgplus_guide/05_building_executing_dynamic_sql_statements.mdx index 7c60e142479..8716ed36b2f 100644 --- a/product_docs/docs/epas/15/application_programming/ecpgplus_guide/05_building_executing_dynamic_sql_statements.mdx +++ b/product_docs/docs/epas/15/application_programming/ecpgplus_guide/05_building_executing_dynamic_sql_statements.mdx @@ -598,7 +598,7 @@ Next, the program calls the `sqlald()` function to allocate the memory required When you allocate an `SQLDA` descriptor, you specify the maximum number of columns you expect to find in the result set (for `SELECT`-list descriptors) or the maximum number of parameters you expect to find the dynamic query text (for bind-variable descriptors). In this case, we specify that we expect no more than 20 columns and 20 parameters. You must also specify a maximum length for each column or parameter name and each indicator variable name. In this case, we expect names to be no more than 64 bytes long. -See [SQLDA structure](07_reference/#sqlda_structure) for a complete description of the `SQLDA` structure. +See [SQLDA structure](/epas/latest/reference/application_programmer_reference/07_reference/) for a complete description of the `SQLDA` structure. ```c params = sqlald(20, 64, 64); @@ -708,7 +708,7 @@ for (col = 0; col < results->F; col++) int null_permitted, length; ``` -To decode the type code found in `results->T`, the program invokes the `sqlnul()` function (see the description of the `T` member of the SQLDA structure in the [The SQLDA structure](07_reference/#sqlda_structure)). This call to `sqlnul()` modifies `results->T[col]` to contain only the type code (the nullability flag is copied to `null_permitted`). This step is needed because the `DESCRIBE SELECT LIST` statement encodes the type of each column and the nullability of each column into the `T` array. +To decode the type code found in `results->T`, the program invokes the `sqlnul()` function (see the description of the `T` member of the SQLDA structure in the [The SQLDA structure](/epas/latest/reference/application_programmer_reference/07_reference/)). This call to `sqlnul()` modifies `results->T[col]` to contain only the type code (the nullability flag is copied to `null_permitted`). This step is needed because the `DESCRIBE SELECT LIST` statement encodes the type of each column and the nullability of each column into the `T` array. ```c sqlnul(&results->T[col], diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx index b492181ecb3..609fc7be3ec 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx @@ -6,4 +6,4 @@ redirects: -Once an SPL program begins execution, any attempt to access a database object from the program results in a check. This check ensures that the current user is authorized to perform the intended action against the referenced object. Privileges on database objects are added and removed using the `GRANT` and `REVOKE` commands. If the current user attempts unauthorized access on a database object, then the program throws an exception. See [Exception handling](../../05_control_structures/07_exception_handling/#exception_handling). +Once an SPL program begins execution, any attempt to access a database object from the program results in a check. This check ensures that the current user is authorized to perform the intended action against the referenced object. Privileges on database objects are added and removed using the `GRANT` and `REVOKE` commands. If the current user attempts unauthorized access on a database object, then the program throws an exception. See [Exception handling](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/07_exception_handling/#exception_handling). diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/01_associative_arrays.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/01_associative_arrays.mdx index f43da412b89..cd8ff88a2e6 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/01_associative_arrays.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/01_associative_arrays.mdx @@ -1,5 +1,5 @@ --- -title: "Associative arrays" +title: "Using associative arrays" redirects: - ../../../../epas_compat_spl/10_collections/01_associative_arrays #generated for docs/epas/reorg-role-use-case-mode --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx index 0ef34001d16..23d733f805d 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx @@ -1,5 +1,5 @@ --- -title: "Nested tables" +title: "Working with nested tables" redirects: - ../../../../epas_compat_spl/10_collections/02_nested_tables #generated for docs/epas/reorg-role-use-case-mode --- @@ -11,7 +11,7 @@ A *nested table* is a type of collection that associates a positive integer with - You must define a *nested table type*. After that, you can declare *nested table variables* of that nested table type. Data manipulation occurs using the nested table variable, also known simply as a table. - When you declare a nested table variable, the nested table doesn't yet exist. It is a null collection. You must initialize the null table with a *constructor*. You can also initialize the table by using an assignment statement where the right-hand side of the assignment is an initialized table of the same type. **Note:** Initialization of a nested table is mandatory in Oracle but optional in SPL. - The key is a positive integer. -- The constructor establishes the number of elements in the table. The `EXTEND` method adds elements to the table. For details, see [Collection methods](../11_collection_methods/#collection_methods). **Note:** Using the constructor to establish the number of elements in the table and using the `EXTEND` method to add elements to the table are mandatory in Oracle but optional in SPL. +- The constructor establishes the number of elements in the table. The `EXTEND` method adds elements to the table. For details, see [Collection methods](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/#collection_methods). **Note:** Using the constructor to establish the number of elements in the table and using the `EXTEND` method to add elements to the table are mandatory in Oracle but optional in SPL. - The table can be sparse. There can be gaps in assigning values to keys. - An attempt to reference a table element beyond its initialized or extended size results in a `SUBSCRIPT_BEYOND_COUNT` exception. @@ -58,7 +58,7 @@ Where: `expr1, expr2, …` are expressions that are type-compatible with the element type of the table. If you specify `NULL`, the corresponding element is set to null. If the parameter list is empty, then an empty nested table is returned, which means the table has no elements. If the table is defined from an object type, then `exprn` must return an object of that object type. The object can be the return value of a function or the object type’s constructor. Or the object can be an element of another nested table of the same type. -If you apply a collection method other than `EXISTS` to an uninitialized nested table, a `COLLECTION_IS_NULL` exception is thrown. For details, see [Collection methods](../11_collection_methods/#collection_methods). +If you apply a collection method other than `EXISTS` to an uninitialized nested table, a `COLLECTION_IS_NULL` exception is thrown. For details, see [Collection methods](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/#collection_methods). This example shows a constructor for a nested table: @@ -144,7 +144,7 @@ BEGIN END; ``` -An empty table with the constructor `emp_tbl_typ()` is created as the first statement in the executable section of the anonymous block. The `EXTEND` collection method is then used to add an element to the table for each employee returned from the result set. See [Extend](../11_collection_methods/04_extend/#extend). +An empty table with the constructor `emp_tbl_typ()` is created as the first statement in the executable section of the anonymous block. The `EXTEND` collection method is then used to add an element to the table for each employee returned from the result set. See [Extend](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/04_extend/#extend). The following is the output: diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/03_varrays.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/03_varrays.mdx index 1424b54a108..5ba039ef6c9 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/03_varrays.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/03_varrays.mdx @@ -1,5 +1,5 @@ --- -title: "Varrays" +title: "Using varrays" redirects: - ../../../../epas_compat_spl/10_collections/03_varrays #generated for docs/epas/reorg-role-use-case-mode --- @@ -13,7 +13,7 @@ A varray has the following characteristics: - You must define a *varray type* with a maximum size limit. After you define the varray type, you can declare *varray variables* of that varray type. Data manipulation occurs using the varray variable, also known simply as a varray. The number of elements in the varray can't exceed the maximum size limit set in the varray type definition. - When you declare a varray variable, the varray at first is a null collection. You must initialize the null varray with a *constructor*. You can also initialize the varray by using an assignment statement where the right-hand side of the assignment is an initialized varray of the same type. - The key is a positive integer. -- The constructor sets the number of elements in the varray, which must not exceed the maximum size limit. The `EXTEND` method can add elements to the varray up to the maximum size limit. For details, see [Collection methods](../11_collection_methods/#collection_methods). +- The constructor sets the number of elements in the varray, which must not exceed the maximum size limit. The `EXTEND` method can add elements to the varray up to the maximum size limit. For details, see [Collection methods](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/#collection_methods). - Unlike a nested table, a varray cannot be sparse. There are no gaps when assigning values to keys. - An attempt to reference a varray element beyond its initialized or extended size but within the maximum size limit results in a `SUBSCRIPT_BEYOND_COUNT` exception. - An attempt to reference a varray element beyond the maximum size limit or extend a varray beyond the maximum size limit results in a `SUBSCRIPT_OUTSIDE_LIMIT` exception. @@ -60,7 +60,7 @@ Where: `expr1, expr2, …` are expressions that are type-compatible with the element type of the varray. If you specify `NULL`, the corresponding element is set to null. If the parameter list is empty, then an empty varray is returned, which means there are no elements in the varray. If the varray is defined from an object type, then `exprn` must return an object of that object type. The object can be the return value of a function or the return value of the object type’s constructor. The object can also be an element of another varray of the same varray type. -If you apply a collection method other than `EXISTS` to an uninitialized varray, a `COLLECTION_IS_NULL` exception is thrown. For details, see [Collection methods](../11_collection_methods/#collection_methods). +If you apply a collection method other than `EXISTS` to an uninitialized varray, a `COLLECTION_IS_NULL` exception is thrown. For details, see [Collection methods](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/#collection_methods). The following is an example of a constructor for a varray: 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 3542da4996b..d5a36eceae6 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 @@ -1,5 +1,5 @@ --- -title: "About collections" +title: "Using collections" --- The most commonly known type of collection is an array. In EDB Postgres Advanced Server, the supported collection types are: diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/index.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/index.mdx index a1f121ef17d..6f943b18fa8 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/index.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/index.mdx @@ -1,5 +1,5 @@ --- -title: "Collection types" +title: "Working with collection types" indexCards: simple navigation: - about_collections diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect.mdx index 8218019b76a..9cb69b60e7a 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect.mdx @@ -6,7 +6,7 @@ redirects: -The following shows the syntax for the `BULK COLLECT` clause with the `SELECT INTO` statement. For details on the `SELECT INTO` statement, see [SELECT INTO](../../04_basic_statements/06_select_into/#select_into). +The following shows the syntax for the `BULK COLLECT` clause with the `SELECT INTO` statement. For details on the `SELECT INTO` statement, see [SELECT INTO](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into/#select_into). ```sql SELECT BULK COLLECT INTO diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/04_returning_bulk_collect.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/04_returning_bulk_collect.mdx index 3ea67265e44..9b9f73e348d 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/04_returning_bulk_collect.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/04_returning_bulk_collect.mdx @@ -14,7 +14,7 @@ You can add `BULK COLLECT` to the `RETURNING INTO` clause of a `DELETE`, `INSERT BULK COLLECT INTO [, ...]; ``` -For information on the `RETURNING INTO` clause, see [Using the RETURNING INTO clause](../../04_basic_statements/05_using_the_returning_into_clause/#using_the_returning_into_clause). `insert`, `update`, and `delete` are the same as the `INSERT`, `UPDATE`, and `DELETE` commands described in [INSERT](../../04_basic_statements/03_insert/#insert), [UPDATE](../../04_basic_statements/07_update/#update), and [DELETE](../../04_basic_statements/02_delete/#delete). +For information on the `RETURNING INTO` clause, see [Using the RETURNING INTO clause](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause/#using_the_returning_into_clause). `insert`, `update`, and `delete` are the same as the `INSERT`, `UPDATE`, and `DELETE` commands described in [INSERT](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert/#insert), [UPDATE](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/), and [DELETE](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/). If you specify a single collection, then `collection` can be a collection of a single field, or it can be a collection of a record type. If you specify more than one collection, then each `collection` must consist of a single field. The expressions following the `RETURNING` keyword must match all fields in the target collections in number, order, and type-compatibility. Specifying `*` returns all columns in the affected table. diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/index.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/index.mdx index d1c30b9d7d6..a6ff1ae036f 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/index.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/index.mdx @@ -15,7 +15,7 @@ EDB Postgres Advanced Server's stored procedural language (SPL) is a highly prod - The use of reusable code - Ease of use -For reference information about the SPL program types, programming statements, control structures, collection types, and collection methods, see [Stored procedural language (SPL) reference](/epas/latest/reference/stored_procedural_language_reference/). +For reference information about the SPL program types, programming statements, control structures, collection types, and collection methods, see [Stored procedural language (SPL) reference](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/). diff --git a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/attribute_descriptions.mdx b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/attribute_descriptions.mdx index 5a5be1d9e0a..e8134d5a41c 100644 --- a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/attribute_descriptions.mdx +++ b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/attribute_descriptions.mdx @@ -11,6 +11,6 @@ The description of each group of parameters includes this list of attributes: - **Minimum scope of effect.** Smallest scope for which a distinct setting can be made. Generally, the minimal scope of a distinct setting is either: - The entire cluster, meaning the setting is the same for all databases in the cluster and its sessions - `per session`, which means the setting might vary by role, database, or individual session. - This attribute has the same meaning as the `Scope of effect` column in the table of [Summary of configuration parameters](../02_summary_of_configuration_parameters/#summary_of_configuration_parameters). -- **When value changes take effect.** Least invasive action required to activate a change to a parameter’s value. All parameter setting changes made in the configuration file can be put into effect by restarting the database server. However, certain parameters require a database server `restart`. Some parameter setting changes can be put into effect with a `reload` of the configuration file without stopping the database server. Finally, other parameter setting changes can be put into effect with some client-side action whose result is `immediate`. This attribute has the same meaning as the `When takes effect` column in the table of [Summary of configuration parameters](../02_summary_of_configuration_parameters/#summary_of_configuration_parameters). -- **Required authorization to activate.** The type of user authorization to activate a change to a parameter’s setting. If a database server restart or a configuration file reload is required, then the user must be an EDB Postgres Advanced Server service account (`enterprisedb` or `postgres`, depending on the EDB Postgres Advanced Server compatibility installation mode). This attribute has the same meaning as the `Authorized user` column in the table of [Summary of configuration parameters](../02_summary_of_configuration_parameters/#summary_of_configuration_parameters). + This attribute has the same meaning as the `Scope of effect` column in the table of [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/). +- **When value changes take effect.** Least invasive action required to activate a change to a parameter’s value. All parameter setting changes made in the configuration file can be put into effect by restarting the database server. However, certain parameters require a database server `restart`. Some parameter setting changes can be put into effect with a `reload` of the configuration file without stopping the database server. Finally, other parameter setting changes can be put into effect with some client-side action whose result is `immediate`. This attribute has the same meaning as the `When takes effect` column in the table of [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/). +- **Required authorization to activate.** The type of user authorization to activate a change to a parameter’s setting. If a database server restart or a configuration file reload is required, then the user must be an EDB Postgres Advanced Server service account (`enterprisedb` or `postgres`, depending on the EDB Postgres Advanced Server compatibility installation mode). This attribute has the same meaning as the `Authorized user` column in the table of [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/). 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 200ba61ea26..23195c61b14 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](02_summary_of_configuration_parameters/#summary_of_configuration_parameters). +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/). 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/epas_security_guide/05_edb_audit_logging/08_audit_log_archiving.mdx b/product_docs/docs/epas/15/epas_security_guide/05_edb_audit_logging/08_audit_log_archiving.mdx index 4fe056839cd..9f51a389b16 100644 --- a/product_docs/docs/epas/15/epas_security_guide/05_edb_audit_logging/08_audit_log_archiving.mdx +++ b/product_docs/docs/epas/15/epas_security_guide/05_edb_audit_logging/08_audit_log_archiving.mdx @@ -7,7 +7,7 @@ redirects: -EDB audit log archiving enables database administrators to control the space consumed by the audit log directory and helps manage the audit log files. The Audit Archiver is responsible for the compression, execution, and expiration of log files with `edb_audit_archiver_filename_prefix` present in the audit directory. The `edb_audit_archiver_timeout` parameter triggers the compression or expiration of audit log files at an appropriate time. For more information about audit archiving configuration parameters, see [Audit logging configuration parameters](01_audit_logging_configuration_parameters). +EDB audit log archiving enables database administrators to control the space consumed by the audit log directory and helps manage the audit log files. The Audit Archiver is responsible for the compression, execution, and expiration of log files with `edb_audit_archiver_filename_prefix` present in the audit directory. The `edb_audit_archiver_timeout` parameter triggers the compression or expiration of audit log files at an appropriate time. For more information about audit archiving configuration parameters, see [Audit logging configuration parameters](/epas/latest/reference/database_administrator_reference/01_audit_logging_configuration_parameters/). The audit archiver helps to: diff --git a/product_docs/docs/epas/15/reference/application_programmer_reference/07_reference.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/07_reference.mdx index c66bc56205c..2fdfe549cc7 100644 --- a/product_docs/docs/epas/15/reference/application_programmer_reference/07_reference.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/07_reference.mdx @@ -315,7 +315,7 @@ struct SQLDA - For a `SELECT`-list descriptor, `V` points to an array of values returned by a `FETCH` statement. Each member in the array corresponds to a column in the result set. - For a bind descriptor, `V` points to an array of parameter values. You must populate the values in this array before opening a cursor that uses the descriptor. -Your application must allocate the space required to hold each value. See [displayResultSet](05_building_executing_dynamic_sql_statements/#executing_query_with_unknown_number_of_variables) for an example of how to allocate space for `SELECT`-list values. +Your application must allocate the space required to hold each value. See [displayResultSet](/epas/latest/application_programming/ecpgplus_guide/05_building_executing_dynamic_sql_statements/#executing_query_with_unknown_number_of_variables) for an example of how to allocate space for `SELECT`-list values. `L - length of each data value` @@ -405,7 +405,7 @@ You can embed any EDB Postgres Advanced Server SQL statement in a C program. Eac EXEC SQL ; ``` -Where `sql_command_body` represents a standard SQL statement. You can use a host variable anywhere that the SQL statement expects a value expression. For more information about substituting host variables for value expressions, see [Declaring host variables](03_using_embedded_sql/#declaring-host-variables). +Where `sql_command_body` represents a standard SQL statement. You can use a host variable anywhere that the SQL statement expects a value expression. For more information about substituting host variables for value expressions, see [Declaring host variables](/epas/latest/application_programming/ecpgplus_guide/03_using_embedded_sql/#declaring-host-variables). ECPGPlus extends the PostgreSQL server-side syntax for some statements. Syntax differences are noted in the reference information that follows. For a complete reference to the supported syntax of other SQL commands, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-commands.html). diff --git a/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/02_delete.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/02_delete.mdx index 21afb630e1f..141d5c191f0 100644 --- a/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/02_delete.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/02_delete.mdx @@ -44,4 +44,4 @@ __OUTPUT__ ``` !!! Note - You can include the `DELETE` command in a `FORALL` statement. A `FORALL` statement allows a single `DELETE` command to delete multiple rows from values supplied in one or more collections. See [Using the FORALL statement](../12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information. + You can include the `DELETE` command in a `FORALL` statement. A `FORALL` statement allows a single `DELETE` command to delete multiple rows from values supplied in one or more collections. See [Using the FORALL statement](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information. diff --git a/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert.mdx index 366af5bad02..b0ee23a34a0 100644 --- a/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert.mdx @@ -81,4 +81,4 @@ __OUTPUT__ ``` !!! Note - You can include the `INSERT` command in a `FORALL` statement. A `FORALL` statement allows a single `INSERT` command to insert multiple rows from values supplied in one or more collections. See [Using the FORALL statement](../12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information. + You can include the `INSERT` command in a `FORALL` statement. A `FORALL` statement allows a single `INSERT` command to insert multiple rows from values supplied in one or more collections. See [Using the FORALL statement](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information. diff --git a/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause.mdx index 5d3c80c27bb..2cb406c7e71 100644 --- a/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause.mdx @@ -28,7 +28,7 @@ The following is the syntax: If the `INSERT`, `UPDATE`, or `DELETE` command returns a result set with more than one row, then an exception is thrown with `SQLCODE 01422, query returned more than one row`. If no rows are in the result set, then the variables following the `INTO` keyword are set to null. !!! Note - A variation of `RETURNING INTO` using the `BULK COLLECT` clause allows a result set of more than one row that's returned into a collection. See [Using the BULK COLLECT clause](../12_working_with_collections/04_using_the_bulk_collect_clause/#using_the_bulk_collect_clause) for more information. + A variation of `RETURNING INTO` using the `BULK COLLECT` clause allows a result set of more than one row that's returned into a collection. See [Using the BULK COLLECT clause](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/#using_the_bulk_collect_clause) for more information. This example modifies the `emp_comp_update` procedure introduced in [UPDATE](07_update/#update). It adds the `RETURNING INTO` clause: diff --git a/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into.mdx index d7f22ffa36a..657067f3cef 100644 --- a/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into.mdx @@ -31,7 +31,7 @@ If the query returns zero rows, null values are assigned to the targets. If the !!! Note - In either case, where no row is returned or more than one row is returned, SPL throws an exception. - - There is a variation of `SELECT INTO` using the `BULK COLLECT` clause that allows a result set of more than one row that's returned into a collection. See [SELECT BULK COLLECT](../12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect/#select_bulk_collect) for more information. + - There is a variation of `SELECT INTO` using the `BULK COLLECT` clause that allows a result set of more than one row that's returned into a collection. See [SELECT BULK COLLECT](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect/#select_bulk_collect) for more information. You can use the `WHEN NO_DATA_FOUND` clause in an `EXCEPTION` block to determine whether the assignment was successful, that is, at least one row was returned by the query. diff --git a/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/07_update.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/07_update.mdx index 22c9091aca4..ca3f637715c 100644 --- a/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/07_update.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/07_update.mdx @@ -51,4 +51,4 @@ empno | ename | job | mgr | hiredate | sal | comm | deptno ``` !!! Note - You can include the `UPDATE` command in a `FORALL` statement. A `FORALL` statement allows a single `UPDATE` command to update multiple rows from values supplied in one or more collections. See [Using the FORALL statement](../12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information. + You can include the `UPDATE` command in a `FORALL` statement. A `FORALL` statement allows a single `UPDATE` command to update multiple rows from values supplied in one or more collections. See [Using the FORALL statement](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information. diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/01_if_then.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/01_if_then.mdx similarity index 92% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/01_if_then.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/01_if_then.mdx index 3fd72c047c4..4468bbf3f74 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/01_if_then.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/01_if_then.mdx @@ -2,6 +2,7 @@ title: "IF-THEN" redirects: - ../../../../../epas_compat_spl/05_control_structures/01_if_statement/01_if_then #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/01_if_statement/01_if_then/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/02_if_then_else.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/02_if_then_else.mdx similarity index 93% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/02_if_then_else.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/02_if_then_else.mdx index d7bb9f8689a..5ee62ea97e4 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/02_if_then_else.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/02_if_then_else.mdx @@ -2,6 +2,7 @@ title: "IF-THEN-ELSE" redirects: - ../../../../../epas_compat_spl/05_control_structures/01_if_statement/02_if_then_else #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/01_if_statement/02_if_then_else/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/03_if_then_else_if.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/03_if_then_else_if.mdx similarity index 96% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/03_if_then_else_if.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/03_if_then_else_if.mdx index d277d17231c..ccf38fbbc9b 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/03_if_then_else_if.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/03_if_then_else_if.mdx @@ -2,6 +2,7 @@ title: "IF-THEN-ELSE IF" redirects: - ../../../../../epas_compat_spl/05_control_structures/01_if_statement/03_if_then_else_if #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/01_if_statement/03_if_then_else_if/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/04_if_then_elseif_else.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/04_if_then_elseif_else.mdx similarity index 94% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/04_if_then_elseif_else.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/04_if_then_elseif_else.mdx index 9646c563e25..e5bf0d03a83 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/04_if_then_elseif_else.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/04_if_then_elseif_else.mdx @@ -2,6 +2,7 @@ title: "IF-THEN-ELSIF-ELSE" redirects: - ../../../../../epas_compat_spl/05_control_structures/01_if_statement/04_if_then_elseif_else #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/01_if_statement/04_if_then_elseif_else/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/index.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/index.mdx similarity index 84% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/index.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/index.mdx index 97f5c54df05..468097d33c9 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/01_if_statement/index.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/index.mdx @@ -2,6 +2,7 @@ title: "IF statement" redirects: - ../../../../epas_compat_spl/05_control_structures/01_if_statement #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/01_if_statement/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/02_return_statement.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/02_return_statement.mdx similarity index 93% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/02_return_statement.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/02_return_statement.mdx index 5fb5c010ac1..0b335965b41 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/02_return_statement.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/02_return_statement.mdx @@ -6,6 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.157.html" redirects: - ../../../../epas_compat_spl/05_control_structures/02_return_statement #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/02_return_statement/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/03_goto_statement.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/03_goto_statement.mdx similarity index 96% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/03_goto_statement.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/03_goto_statement.mdx index 4e3ac716fab..81b2766836d 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/03_goto_statement.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/03_goto_statement.mdx @@ -6,6 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.158.html" redirects: - ../../../../epas_compat_spl/05_control_structures/03_goto_statement #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/03_goto_statement/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/04_case_expression/01_selector_case_expression.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/01_selector_case_expression.mdx similarity index 96% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/04_case_expression/01_selector_case_expression.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/01_selector_case_expression.mdx index 52adc59698d..c1f39c76639 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/04_case_expression/01_selector_case_expression.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/01_selector_case_expression.mdx @@ -2,6 +2,7 @@ title: "Selector CASE expression" redirects: - ../../../../../epas_compat_spl/05_control_structures/04_case_expression/01_selector_case_expression #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/05_case_statement/01_selector_case_statement/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/04_case_expression/02_searched_case_expression.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/02_searched_case_expression.mdx similarity index 95% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/04_case_expression/02_searched_case_expression.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/02_searched_case_expression.mdx index b3f71bd685a..8da63e6ea9a 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/04_case_expression/02_searched_case_expression.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/02_searched_case_expression.mdx @@ -2,6 +2,7 @@ title: "Searched CASE expression" redirects: - ../../../../../epas_compat_spl/05_control_structures/04_case_expression/02_searched_case_expression #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/05_case_statement/02_searched_case_statement/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/04_case_expression/index.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/index.mdx similarity index 91% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/04_case_expression/index.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/index.mdx index 46e302b0ef0..d93a6aea8e1 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/04_case_expression/index.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/index.mdx @@ -6,6 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.159.html" redirects: - ../../../../epas_compat_spl/05_control_structures/04_case_expression #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/05_case_statement/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/05_case_statement/01_selector_case_statement.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/01_selector_case_statement.mdx similarity index 96% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/05_case_statement/01_selector_case_statement.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/01_selector_case_statement.mdx index 3e0b4e93f99..774da050b4c 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/05_case_statement/01_selector_case_statement.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/01_selector_case_statement.mdx @@ -2,6 +2,7 @@ title: "Selector CASE statement" redirects: - ../../../../../epas_compat_spl/05_control_structures/05_case_statement/01_selector_case_statement #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/05_case_statement/01_selector_case_statement/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/05_case_statement/02_searched_case_statement.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/02_searched_case_statement.mdx similarity index 96% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/05_case_statement/02_searched_case_statement.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/02_searched_case_statement.mdx index 0212fdbf67b..997039ea989 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/05_case_statement/02_searched_case_statement.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/02_searched_case_statement.mdx @@ -2,6 +2,7 @@ title: "Searched CASE statement" redirects: - ../../../../../epas_compat_spl/05_control_structures/05_case_statement/02_searched_case_statement #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/05_case_statement/02_searched_case_statement/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/05_case_statement/index.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/index.mdx similarity index 91% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/05_case_statement/index.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/index.mdx index 5e0104f5927..d4afd25b072 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/05_case_statement/index.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/index.mdx @@ -6,6 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.160.html" redirects: - ../../../../epas_compat_spl/05_control_structures/05_case_statement #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/05_case_statement/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/01_loop.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/01_loop.mdx similarity index 79% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/01_loop.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/01_loop.mdx index 5122b34636e..328c737ebfe 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/01_loop.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/01_loop.mdx @@ -2,6 +2,7 @@ title: "LOOP" redirects: - ../../../../../epas_compat_spl/05_control_structures/06_loops/01_loop #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/01_loop/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/02_exit.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/02_exit.mdx similarity index 91% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/02_exit.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/02_exit.mdx index cddfdf02075..8e37993fc59 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/02_exit.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/02_exit.mdx @@ -2,6 +2,7 @@ title: "EXIT" redirects: - ../../../../../epas_compat_spl/05_control_structures/06_loops/02_exit #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/02_exit/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/03_continue.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/03_continue.mdx similarity index 93% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/03_continue.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/03_continue.mdx index 1f464dec2eb..8d981c6eec7 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/03_continue.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/03_continue.mdx @@ -2,6 +2,7 @@ title: "CONTINUE" redirects: - ../../../../../epas_compat_spl/05_control_structures/06_loops/03_continue #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/03_continue/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/04_while.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/04_while.mdx similarity index 92% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/04_while.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/04_while.mdx index ffd67d6fad8..e98928ba740 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/04_while.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/04_while.mdx @@ -2,6 +2,7 @@ title: "WHILE" redirects: - ../../../../../epas_compat_spl/05_control_structures/06_loops/04_while #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/04_while/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/05_for_integer_variant.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/05_for_integer_variant.mdx similarity index 90% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/05_for_integer_variant.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/05_for_integer_variant.mdx index 085ca2965d3..f7fb2ebaa0f 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/05_for_integer_variant.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/05_for_integer_variant.mdx @@ -2,6 +2,7 @@ title: "FOR (integer variant)" redirects: - ../../../../../epas_compat_spl/05_control_structures/06_loops/05_for_integer_variant #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/05_for_integer_variant/ --- @@ -57,4 +58,4 @@ END; This example has no output as the loop body never executes. !!! Note - SPL also supports cursor `FOR` loops. See [Cursor FOR loop](../../08_static_cursors/07_cursor_for_loop/#cursor_for_loop). + SPL also supports cursor `FOR` loops. See [Cursor FOR loop](/epas/latest/application_programming/epas_compat_spl/08_static_cursors/07_cursor_for_loop/). diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/index.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/index.mdx similarity index 90% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/index.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/index.mdx index 80bf2776a47..afc37afbc96 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/06_loops/index.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/index.mdx @@ -6,6 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.161.html" redirects: - ../../../../epas_compat_spl/05_control_structures/06_loops #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/07_exception_handling.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/07_exception_handling.mdx similarity index 98% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/07_exception_handling.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/07_exception_handling.mdx index 0d1f7fc01df..101ae9b4e0d 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/07_exception_handling.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/07_exception_handling.mdx @@ -6,6 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.162.html" redirects: - ../../../../epas_compat_spl/05_control_structures/07_exception_handling #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/07_exception_handling/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/08_user_defined_exceptions.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/08_user_defined_exceptions.mdx similarity index 97% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/08_user_defined_exceptions.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/08_user_defined_exceptions.mdx index 669a70bbcfb..4f164cf318d 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/08_user_defined_exceptions.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/08_user_defined_exceptions.mdx @@ -6,6 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.163.html" redirects: - ../../../../epas_compat_spl/05_control_structures/08_user_defined_exceptions #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/08_user_defined_exceptions/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/09_pragma_exception_init.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/09_pragma_exception_init.mdx similarity index 97% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/09_pragma_exception_init.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/09_pragma_exception_init.mdx index 301b6805d43..db10dc31ad4 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/09_pragma_exception_init.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/09_pragma_exception_init.mdx @@ -6,6 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.164.html" redirects: - ../../../../epas_compat_spl/05_control_structures/09_pragma_exception_init #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/09_pragma_exception_init/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/10_raise_application_error.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/10_raise_application_error.mdx similarity index 92% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/10_raise_application_error.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/10_raise_application_error.mdx index e3d2d0211a7..ff23c775524 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/10_raise_application_error.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/10_raise_application_error.mdx @@ -6,6 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.165.html" redirects: - ../../../../epas_compat_spl/05_control_structures/10_raise_application_error #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/10_raise_application_error/ --- @@ -24,7 +25,7 @@ Where: `message` is a string literal or expression returned in a variable named `SQLERRM`. -For more information on the `SQLCODE` and `SQLERRM` variables, see [Errors and messages](../12_working_with_collections/05_errors_and_messages/#errors_and_messages). +For more information on the `SQLCODE` and `SQLERRM` variables, see [Errors and messages](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/05_errors_and_messages/). This example uses the `RAISE_APPLICATION_ERROR` procedure to display a different code and message depending on the information missing from an employee: diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/index.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/index.mdx similarity index 92% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/index.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/index.mdx index aefbcd94260..8038e97bef3 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/05_control_structures/index.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/index.mdx @@ -7,6 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.156.html" redirects: - ../../../epas_compat_spl/05_control_structures #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/05_control_structures/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/01_count.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/01_count.mdx similarity index 92% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/01_count.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/01_count.mdx index eb09cdc6e7a..cce0ec8da2d 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/01_count.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/01_count.mdx @@ -2,6 +2,7 @@ title: "COUNT" redirects: - ../../../../epas_compat_spl/11_collection_methods/01_count #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/01_count/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/02_deletes.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/02_deletes.mdx similarity index 96% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/02_deletes.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/02_deletes.mdx index 0b7d220a93a..552475c9003 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/02_deletes.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/02_deletes.mdx @@ -2,6 +2,7 @@ title: "DELETE" redirects: - ../../../../epas_compat_spl/11_collection_methods/02_deletes #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/02_deletes/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/03_exists.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/03_exists.mdx similarity index 93% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/03_exists.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/03_exists.mdx index 92e6ce2c9b2..d6c41017b4b 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/03_exists.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/03_exists.mdx @@ -2,6 +2,7 @@ title: "EXISTS" redirects: - ../../../../epas_compat_spl/11_collection_methods/03_exists #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/03_exists/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/04_extend.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/04_extend.mdx similarity index 97% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/04_extend.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/04_extend.mdx index 82dd7cca613..b4ab1f5fcda 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/04_extend.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/04_extend.mdx @@ -2,6 +2,7 @@ title: "EXTEND" redirects: - ../../../../epas_compat_spl/11_collection_methods/04_extend #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/04_extend/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/05_first.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/05_first.mdx similarity index 90% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/05_first.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/05_first.mdx index 10947e0e407..a4be2019ec8 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/05_first.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/05_first.mdx @@ -2,6 +2,7 @@ title: "FIRST" redirects: - ../../../../epas_compat_spl/11_collection_methods/05_first #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/05_first/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/06_last.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/06_last.mdx similarity index 90% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/06_last.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/06_last.mdx index c781ee68651..7d8c9f8b4e3 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/06_last.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/06_last.mdx @@ -2,6 +2,7 @@ title: "LAST" redirects: - ../../../../epas_compat_spl/11_collection_methods/06_last #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/06_last/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/07_limit.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/07_limit.mdx similarity index 90% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/07_limit.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/07_limit.mdx index f452bd80d96..2fd2a491597 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/07_limit.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/07_limit.mdx @@ -2,6 +2,7 @@ title: "LIMIT" redirects: - ../../../../epas_compat_spl/11_collection_methods/07_limit #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/07_limit/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/08_next.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/08_next.mdx similarity index 93% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/08_next.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/08_next.mdx index c2ce273c7a7..ab72a735015 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/08_next.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/08_next.mdx @@ -2,6 +2,7 @@ title: "NEXT" redirects: - ../../../../epas_compat_spl/11_collection_methods/08_next #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/08_next/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/09_prior.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/09_prior.mdx similarity index 93% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/09_prior.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/09_prior.mdx index 4669683baff..8ebc125d01a 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/09_prior.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/09_prior.mdx @@ -2,6 +2,7 @@ title: "PRIOR" redirects: - ../../../../epas_compat_spl/11_collection_methods/09_prior #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/09_prior/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/10_trim.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/10_trim.mdx similarity index 95% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/10_trim.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/10_trim.mdx index d428b9016d9..3334f60580a 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/10_trim.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/10_trim.mdx @@ -2,6 +2,7 @@ title: "TRIM" redirects: - ../../../../epas_compat_spl/11_collection_methods/10_trim #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/10_trim/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/index.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/index.mdx similarity index 92% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/index.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/index.mdx index 9b15e3b3b87..192cf6c11ec 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/11_collection_methods/index.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/index.mdx @@ -7,6 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.173.html" redirects: - ../../../epas_compat_spl/11_collection_methods #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/ --- diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/17_advanced_server_keywords.mdx b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/17_advanced_server_keywords.mdx similarity index 99% rename from product_docs/docs/epas/15/application_programming/epas_compat_spl/17_advanced_server_keywords.mdx rename to product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/17_advanced_server_keywords.mdx index 2b429355f37..0dbc5fd0500 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/17_advanced_server_keywords.mdx +++ b/product_docs/docs/epas/15/reference/application_programmer_reference/stored_procedural_language_reference/17_advanced_server_keywords.mdx @@ -6,6 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.264.html" redirects: - ../../../epas_guide/17_advanced_server_keywords #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/application_programming/epas_compat_spl/17_advanced_server_keywords/ --- diff --git a/product_docs/docs/epas/15/reference/database_administrator_reference/01_audit_logging_configuration_parameters.mdx b/product_docs/docs/epas/15/reference/database_administrator_reference/01_audit_logging_configuration_parameters.mdx index bf98e3f88bc..a8511b4e6a3 100644 --- a/product_docs/docs/epas/15/reference/database_administrator_reference/01_audit_logging_configuration_parameters.mdx +++ b/product_docs/docs/epas/15/reference/database_administrator_reference/01_audit_logging_configuration_parameters.mdx @@ -6,7 +6,7 @@ redirects: - /epas/latest/epas_security_guide/05_edb_audit_logging/01_audit_logging_configuration_parameters/ --- -Use the following configuration parameters to control database auditing. See [Summary of configuration parameters](/epas/latest/database_administration/01_configuration_parameters/02_summary_of_configuration_parameters/) to determine if a change to the configuration parameter: +Use the following configuration parameters to control database auditing. See [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/) to determine if a change to the configuration parameter: - Takes effect immediately - Requires reloading the configuration @@ -103,7 +103,7 @@ If the parameter is set to `-1`, compression of the log file on a size basis doe `edb_audit_statement` - Specifies auditing of different categories of SQL statements. You can specify various combinations of the following values: `none`, `dml`, `insert`, `update`, `delete`, `truncate`, `select`, `error`, `rollback`, `ddl`, `create`, `drop`, `alter`, `grant`, `revoke`, `set`, `all`, and `{ select | update | delete | insert }@groupname`. The default is `ddl` and `error`. See [Selecting SQL statements to audit](02_selecting_sql_statements_to_audit/#selecting_sql_statements_to_audit) for information about setting this parameter. + Specifies auditing of different categories of SQL statements. You can specify various combinations of the following values: `none`, `dml`, `insert`, `update`, `delete`, `truncate`, `select`, `error`, `rollback`, `ddl`, `create`, `drop`, `alter`, `grant`, `revoke`, `set`, `all`, and `{ select | update | delete | insert }@groupname`. The default is `ddl` and `error`. See [Selecting SQL statements to audit](/epas/latest/epas_security_guide/05_edb_audit_logging/02_selecting_sql_statements_to_audit/) for information about setting this parameter. `edb_audit_tag` @@ -123,4 +123,4 @@ If the parameter is set to `-1`, compression of the log file on a size basis doe In recent Linux versions, syslog was replaced with `rsyslog`, and the configuration file is in `/etc/rsyslog.conf`. !!! Note - EDB Postgres Advanced Server allows administrative users associated with administrative privileges to audit statements by any user, group, or role. By auditing specific users, you can minimize the number of audit records generated. For information, see the examples under [Selecting SQL statements to audit](02_selecting_sql_statements_to_audit/#ddl-and-dcl-statements). + EDB Postgres Advanced Server allows administrative users associated with administrative privileges to audit statements by any user, group, or role. By auditing specific users, you can minimize the number of audit records generated. For information, see the examples under [Selecting SQL statements to audit](/epas/latest/epas_security_guide/05_edb_audit_logging/02_selecting_sql_statements_to_audit/). diff --git a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect.mdx similarity index 94% rename from product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect.mdx rename to product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect.mdx index 51f70114c8b..232b8af7c8e 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect.mdx @@ -2,6 +2,7 @@ title: "dblink_ora_connect()" redirects: - ../../../../epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect/ --- diff --git a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/02_dblink_ora_status.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/02_dblink_ora_status.mdx similarity index 82% rename from product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/02_dblink_ora_status.mdx rename to product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/02_dblink_ora_status.mdx index 17dc376f5f6..fb469211180 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/02_dblink_ora_status.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/02_dblink_ora_status.mdx @@ -2,6 +2,7 @@ title: "dblink_ora_status()" redirects: - ../../../../epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/02_dblink_ora_status #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/02_dblink_ora_status/ --- diff --git a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect.mdx similarity index 80% rename from product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect.mdx rename to product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect.mdx index d1103c0dc0b..03a1183ec79 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect.mdx @@ -2,6 +2,7 @@ title: "dblink_ora_disconnect()" redirects: - ../../../../epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect/ --- diff --git a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/04_dblink_ora_record.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/04_dblink_ora_record.mdx similarity index 84% rename from product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/04_dblink_ora_record.mdx rename to product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/04_dblink_ora_record.mdx index cf99b039fe4..0534e8c01f6 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/04_dblink_ora_record.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/04_dblink_ora_record.mdx @@ -2,6 +2,7 @@ title: "dblink_ora_record()" redirects: - ../../../../epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/04_dblink_ora_record #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/04_dblink_ora_record/ --- diff --git a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/05_dblink_ora_call.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/05_dblink_ora_call.mdx similarity index 86% rename from product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/05_dblink_ora_call.mdx rename to product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/05_dblink_ora_call.mdx index 9917e4a6520..8bdf5898c87 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/05_dblink_ora_call.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/05_dblink_ora_call.mdx @@ -2,6 +2,7 @@ title: "dblink_ora_call()" redirects: - ../../../../epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/05_dblink_ora_call #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/05_dblink_ora_call/ --- diff --git a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec.mdx similarity index 84% rename from product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec.mdx rename to product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec.mdx index cd712f2da3a..84d6d108189 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec.mdx @@ -2,6 +2,7 @@ title: "dblink_ora_exec()" redirects: - ../../../../epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec/ --- diff --git a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy.mdx similarity index 92% rename from product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy.mdx rename to product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy.mdx index 3c117658cd2..e98bffa4d95 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy.mdx @@ -2,6 +2,7 @@ title: "dblink_ora_copy()" redirects: - ../../../../epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy/ --- diff --git a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/index.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/index.mdx similarity index 92% rename from product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/index.mdx rename to product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/index.mdx index a89fa142d82..b50e02d9d56 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/index.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/index.mdx @@ -8,6 +8,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.354.html" redirects: - ../../../epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/ --- diff --git a/product_docs/docs/epas/15/working_with_oracle_data/02_enhanced_compatibility_features.mdx b/product_docs/docs/epas/15/working_with_oracle_data/02_enhanced_compatibility_features.mdx index 76b0fca9de8..22ee96922d2 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/02_enhanced_compatibility_features.mdx +++ b/product_docs/docs/epas/15/working_with_oracle_data/02_enhanced_compatibility_features.mdx @@ -31,7 +31,7 @@ You can install EDB Postgres Advanced Server in several ways to take advantage o - Use the `INITDBOPTS` variable in the EDB Postgres Advanced Server service configuration file to specify `--redwood-like` before initializing your cluster. - When invoking `initdb` to initialize your cluster compatible with Oracle mode, include the `--redwood-like` or `--no-redwood-compat` option to initialize your cluster in Oracle non-compatible mode. -See [Configuration parameters compatible with Oracle databases](/epas/latest/database_administration/01_configuration_parameters/02_summary_of_configuration_parameters/) and [Managing an EDB Postgres Advanced Server installation](/epas/latest/installing/linux_install_details/managing_an_advanced_server_installation/) for more information about the installation options supported by the EDB Postgres Advanced Server installers. +See [Configuration parameters compatible with Oracle databases](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/) and [Managing an EDB Postgres Advanced Server installation](/epas/latest/installing/linux_install_details/managing_an_advanced_server_installation/) for more information about the installation options supported by the EDB Postgres Advanced Server installers. ## Stored procedural language From a0cb119e356eb183d618ef536b54a17333e60790 Mon Sep 17 00:00:00 2001 From: Stefan Fercot Date: Mon, 24 Jul 2023 09:04:08 +0200 Subject: [PATCH 10/29] add postgresql.bin_name.postgres setting --- .../supported-open-source/patroni/debian11_quick_start.mdx | 6 +++++- .../supported-open-source/patroni/rhel8_quick_start.mdx | 6 +++++- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx b/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx index 66d8d36739b..3df7660a5ec 100644 --- a/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx +++ b/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx @@ -27,6 +27,7 @@ export PGUSER=enterprisedb export PGGROUP=enterprisedb export PGDATA="/var/lib/edb-as/15/main" export PGBIN="/usr/lib/edb-as/15/bin" +export PGBINNAME="edb-postgres" export PGSOCKET="/var/run/edb-as" ``` @@ -38,6 +39,7 @@ export PGUSER=postgres export PGGROUP=postgres export PGDATA="/var/lib/edb-pge/15/data" export PGBIN="/usr/lib/edb-pge/15/bin" +export PGBINNAME="postgres" export PGSOCKET="/var/run/edb-pge" ``` @@ -134,6 +136,8 @@ postgresql: connect_address: "$MY_IP:$PGPORT" data_dir: $PGDATA bin_dir: $PGBIN + bin_name: + postgres: $PGBINNAME pgpass: /tmp/pgpass0 authentication: replication: @@ -167,7 +171,7 @@ EOF `$MY_IP` and `$MY_NAME` are specific to the local host. Otherwise, the `patroni.yml` configuration is the same on all Patroni nodes. -Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. Create a symbolic link to let Patroni find that binary: +Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. Before Patroni [version `3.0.3`](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), remove the `bin_name` setting from the configuration and create a symbolic link to let Patroni find that binary: ```bash sudo ln -s /usr/lib/edb-as/15/bin/edb-postgres /usr/lib/edb-as/15/bin/postgres diff --git a/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx b/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx index f52c2058f43..c8dbb6e403b 100644 --- a/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx +++ b/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx @@ -27,6 +27,7 @@ export PGUSER=enterprisedb export PGGROUP=enterprisedb export PGDATA="/var/lib/edb/as15/data" export PGBIN="/usr/edb/as15/bin" +export PGBINNAME="edb-postgres" export PGSOCKET="/var/run/edb/as15" ``` @@ -38,6 +39,7 @@ export PGUSER=postgres export PGGROUP=postgres export PGDATA="/var/lib/edb-pge/15/data" export PGBIN="/usr/edb/pge15/bin" +export PGBINNAME="postgres" export PGSOCKET="/var/run/edb-pge" ``` @@ -136,6 +138,8 @@ postgresql: connect_address: "$MY_IP:$PGPORT" data_dir: $PGDATA bin_dir: $PGBIN + bin_name: + postgres: $PGBINNAME pgpass: /tmp/pgpass0 authentication: replication: @@ -169,7 +173,7 @@ EOF `$MY_IP` and `$MY_NAME` are specific to the local host. Otherwise, the `patroni.yml` configuration is the same on all Patroni nodes. -Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. Create a symbolic link to let Patroni find that binary: +Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. Before Patroni [version `3.0.3`](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), remove the `bin_name` setting from the configuration and create a symbolic link to let Patroni find that binary: ```bash sudo ln -s /usr/edb/as15/bin/edb-postgres /usr/edb/as15/bin/postgres From 56d3c9f3dd85f3cfa64dfba34c7f49d041381156 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Mon, 24 Jul 2023 12:47:57 -0400 Subject: [PATCH 11/29] Edits to PR4456 removed future tense --- product_docs/docs/migration_portal/4/known_issues_notes.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/migration_portal/4/known_issues_notes.mdx b/product_docs/docs/migration_portal/4/known_issues_notes.mdx index 748cd45f7e1..91e84ab36cd 100644 --- a/product_docs/docs/migration_portal/4/known_issues_notes.mdx +++ b/product_docs/docs/migration_portal/4/known_issues_notes.mdx @@ -27,7 +27,7 @@ Migration Portal recommends the `.SQL` output file be in the UTF-8 encoding form ### ALTER statements -Except for ALTER TABLE and ALTER TRIGGER, Migration Portal does not process any other ALTER statements in the DDL. +Except for ALTER TABLE and ALTER TRIGGER, Migration Portal doesn't process any other ALTER statements in the DDL. ### Users, roles, profiles, and grants @@ -37,7 +37,7 @@ The Migration Portal now supports assessing and migrating the Oracle users for t Since the grants are currently attached to the user and role objects, if one or more objects that the user is being granted a permission on fails, the user object itself fails assessment. To resolve this issue, any grant statements on failed objects can be commented out either using a SQL single line comment (`--`) for individual statements or a SQL multi-line comment (`/* */`) for consecutive grant statements and then a reassessment of the object can be performed. After the failed object corresponding to the failed grant statements have been repaired, the previously failing grant statement can be uncommented and the user object reassessed. -Granting the RESOURCE role is equivalent to granting the CREATE and USAGE privileges on a schema that shares the same name as the grantee. If you want to grant the RESOURCE role, you need to first create a schema with the same name as the user or role. Otherwise, you will get a "Schema does not exist" error. +Granting the RESOURCE role is equivalent to granting the CREATE and USAGE privileges on a schema that shares the same name as the grantee. If you want to grant the RESOURCE role, you need to first create a schema with the same name as the user or role. Otherwise, a "Schema does not exist" error occurs. #### Privileges From e47a70e370cdae259b1b564d2607509042abe193 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Mon, 24 Jul 2023 12:54:19 -0400 Subject: [PATCH 12/29] Edits to PR4472 Added hyphen for compound adjective --- .../docs/biganimal/release/overview/02_high_availability.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx index 010ee3e6023..5000710e345 100644 --- a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx +++ b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx @@ -73,7 +73,7 @@ The following is the possible node configuration for one region: 2 data nodes + 1 local witness node ![2 data + 1 local witness](images/extreme-high-availability-single-region.png) -If you're looking for a true active-active solution that protects against regional failures, select a three region configuration. The following is the possible configurations for three regions: +If you're looking for a true active-active solution that protects against regional failures, select a three-region configuration. The following is the possible configurations for three regions: 3 data nodes + 3 data nodes, 1 witness group in a different region ![3 data nodes + 3 data nodes, 1 witness group in a different region ](images/extreme-high-availability-3-regions.png) From 4e13f2b1a2e4f4f6ed68ea09ed4e013de0cd2d58 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Mon, 24 Jul 2023 13:28:21 -0400 Subject: [PATCH 13/29] Edits to PR4191 --- .../gcp_policy_definitions.mdx | 2 +- .../02_connecting_to_your_cloud/connecting_aws.mdx | 4 ++-- .../02_connecting_to_your_cloud/connecting_gcp.mdx | 10 +++++----- .../creating_a_cluster/01_cluster_networking.mdx | 4 ++-- .../preparing_cloud_account/preparing_gcp/index.mdx | 1 + .../preparing_gcp/understanding_quotas_in_gcp.mdx | 8 ++++---- .../release/overview/03a_region_support/index.mdx | 12 ++++++------ 7 files changed, 21 insertions(+), 20 deletions(-) diff --git a/product_docs/docs/biganimal/release/administering_cluster/customizing_compliance/gcp_policy_definitions.mdx b/product_docs/docs/biganimal/release/administering_cluster/customizing_compliance/gcp_policy_definitions.mdx index 78fa4a797a6..027784df202 100644 --- a/product_docs/docs/biganimal/release/administering_cluster/customizing_compliance/gcp_policy_definitions.mdx +++ b/product_docs/docs/biganimal/release/administering_cluster/customizing_compliance/gcp_policy_definitions.mdx @@ -3,7 +3,7 @@ title: "Customizing Google Cloud compliance policies" description: "Customize Google Cloud compliance configuration settings to match BigAnimal's resource configurations" --- -Google Cloud uses Assured Workloads and Organization Policies to ensure compliance rules are respected. Assured Workloads monitoring scans your environment in real time and provides alerts whenever organization policy changes violate the defined compliance posture. The monitoring dashboard shows which policy is being violated and provides instructions on how to resolve the finding. +Google Cloud uses Assured Workloads and the Organization Policy Service to ensure compliance rules are respected. Assured Workloads monitoring scans your environment in real time and provides alerts whenever organization policy changes violate the defined compliance posture. The monitoring dashboard shows which policy is being violated and provides instructions on how to resolve the finding. For more information, see: - [Overview of Assured Workloads](https://cloud.google.com/assured-workloads/docs/overview) diff --git a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/connecting_aws.mdx b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/connecting_aws.mdx index 56d340fd062..34bf2b9abd0 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/connecting_aws.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/connecting_aws.mdx @@ -14,11 +14,11 @@ Before connecting your cloud, make sure that you're assigned the following AWS m ## Connecting your cloud !!! tip - If you're using Cloud Shell, add the `./` prefix to the `biganimal` command (`./biganimal`). + If you're using CloudShell, add the `./` prefix to the `biganimal` command (`./biganimal`). To connect your cloud: -1. Open the AWS Cloud Shell in your browser. +1. Open AWS CloudShell in your browser. 1. Create a BigAnimal CLI credential: diff --git a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/connecting_gcp.mdx b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/connecting_gcp.mdx index 6f2ebf65e95..9df54d4c450 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/connecting_gcp.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/connecting_gcp.mdx @@ -12,7 +12,7 @@ Ensure you have at least the following combined roles: - roles/resourcemanager.projectIamAdmin - roles/compute.viewer -Or an equivalent single role such as: +Alternatively, you can have an equivalent single role, such as: - roles/owner ## Connecting your cloud @@ -22,7 +22,7 @@ Or an equivalent single role such as: To connect your cloud: -1. Open the Google Cloud Shell in your browser. +1. Open Google Cloud Shell in your browser. 1. Create a BigAnimal CLI credential: @@ -37,14 +37,14 @@ To connect your cloud: ``` The command checks for cloud account readiness and displays the results. -1. If the following readiness checks aren't met for your cloud service provider, see [Configure your Google Cloud account](/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/#configure-your-google-cloud-account) to manually configure your cloud: +1. If the following cloud readiness checks pass for your cloud service provider, your cloud account is successfully set up: - Is the Google Cloud CLI configured to access your Google Cloud account? - Is the limit on the number of vCPUs and network load balancers (NLBs) in your region enough for your clusters? - If the cloud readiness checks pass, your cloud account is successfully set up. - + If the readiness checks aren't met, see [Configure your Google Cloud account](/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/#configure-your-google-cloud-account) to manually configure your cloud. + 1. Connect your cloud account to BigAnimal: ```shell diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/01_cluster_networking.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/01_cluster_networking.mdx index 4430f682033..192ffebfc0f 100644 --- a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/01_cluster_networking.mdx +++ b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/01_cluster_networking.mdx @@ -42,7 +42,7 @@ Because the load balancer IP address used in AWS is dynamic, make sure that your ### Google load balancer in Google Cloud -BigAnimal creates a new load balancer using the Premium Network Service Tier for each cluster and tags it using an unique identifier. The corresponding frontend forwarding rule uses the same unique identifier and includes the cluster ID in the following format: +BigAnimal creates a new load balancer using the Premium Network Service Tier for each cluster and tags it using a unique identifier. The corresponding front-end forwarding rule uses the same unique identifier and includes the cluster ID in the following format: ``` {"kubernetes.io/service-name":"default/-"} @@ -50,4 +50,4 @@ BigAnimal creates a new load balancer using the Premium Network Service Tier for An example is `{"kubernetes.io/service-name":"default/p-8jz4kedbiy-rw-external-lb"}`. -Because the load balancer IP address used in Google Cloud is dynamic, make sure that your application uses the correct DNS name to access the network load balancer of a particular cluster. To be able to access it, make sure you are using the FQDN that BigAnimal provides in the Cluster Overview or Connect page. +Because the load balancer IP address used in Google Cloud is dynamic, make sure that your application uses the correct DNS name to access the network load balancer of a particular cluster. To be able to access it, make sure you're using the FQDN that BigAnimal provides in the Cluster Overview or Connect page. diff --git a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx index 9e9d9bca5f3..00b29153297 100644 --- a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx @@ -120,6 +120,7 @@ The script displays the following output: ####################### # Overall Suggestions # ####################### + ``` Make sure the GCP Project ID is the one that you want to use for BigAnimal. Make sure the GCP account has rights to create custom roles, service accounts, keys, and assign project grants. diff --git a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/understanding_quotas_in_gcp.mdx b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/understanding_quotas_in_gcp.mdx index f58474d6fe8..f956cdcf329 100644 --- a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/understanding_quotas_in_gcp.mdx +++ b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/understanding_quotas_in_gcp.mdx @@ -7,7 +7,7 @@ Follow these BigAnimal requirements and recommended resource limits in Google Cl ## vCPU limits Any time a new VM is deployed in Google Cloud, the vCPUs for the VMs must not exceed the total vCPU limits for the region. -The number of cores required by the database cluster depends on the instance type and cluster type of the clusters. For example, if you create cluster with the Standard E2 instance type, you can calculate the number of E2 cores required for your cluster based on the following: +The number of cores required by the database cluster depends on the instance type and cluster type of the clusters. For example, if you create a cluster with the standard E2 instance type, you can calculate the number of E2 cores required for your cluster based on the following: - A virtual machine instance of type e2-standard-{N} uses {N} cores. For example, an instance of type e2-standard-32 uses 32 e2-standard cores. @@ -22,8 +22,8 @@ BigAnimal requires an additional four n2-standard virtual machine cores per regi ## Recommended limits BigAnimal recommends the following per region when requesting virtual machine resource limit increases: -Total Regional vCPUs: minimum of 50 per designated region +- Total Regional vCPUs: minimum of 50 per designated region -n2-standard vCPUs: minimum of 12 per designated region +- n2-standard vCPUs: minimum of 12 per designated region -Other machine family vCPUs: depending on the instance type, cluster type, and number of clusters. \ No newline at end of file +- Other machine family vCPUs: depends on the instance type, cluster type, and number of clusters. \ No newline at end of file diff --git a/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx b/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx index 888a15e72fa..fe5c687e101 100644 --- a/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx +++ b/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx @@ -12,11 +12,11 @@ See [Country and geographical region reference](country_reference) for informati When using your own cloud account, to successfully deploy a cluster, you must activate the region to prepare its cloud infrastructure. See [Activating regions](/biganimal/latest/getting_started/activating_regions) for more information. !!! Tip - You can select a cloud region for deploying your cluster even if it is not yet *Active*. However, your cluster creation request is added to a queue, and the cluster is created only after you activate the region. + You can select a cloud region for deploying your cluster even if it isn't yet active. However, your cluster creation request is added to a queue, and the cluster is created only after you activate the region. ### Azure regions -When using Azure, you can create clusters in the following regions: +When using Azure, you can create clusters in the following regions. #### North America (NA) @@ -59,7 +59,7 @@ When using Azure, you can create clusters in the following regions: ### AWS regions -When using AWS, you can create clusters in the following regions: +When using AWS, you can create clusters in the following regions. #### North America (NA) @@ -92,7 +92,7 @@ When using AWS, you can create clusters in the following regions: ### Google Cloud regions -When using Google Cloud, you can create clusters in the following regions: +When using Google Cloud, you can create clusters in the following regions. #### North America (NA) @@ -154,7 +154,7 @@ When using Google Cloud, you can create clusters in the following regions: ### AWS regions -When using AWS and BigAnimal's cloud account, you can create clusters in the following regions: +When using AWS and BigAnimal's cloud account, you can create clusters in the following regions. #### North America (NA) @@ -181,7 +181,7 @@ When using AWS and BigAnimal's cloud account, you can create clusters in the fol ### Google Cloud regions -When using Google Cloud and BigAnimal's cloud account, you can create clusters in the following regions: +When using Google Cloud and BigAnimal's cloud account, you can create clusters in the following regions. #### North America (NA) From 4e9e31e593332148eed7b67fac774cccfc218107 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Mon, 24 Jul 2023 13:31:05 -0400 Subject: [PATCH 14/29] Update gcp_policy_definitions.mdx --- .../customizing_compliance/gcp_policy_definitions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/administering_cluster/customizing_compliance/gcp_policy_definitions.mdx b/product_docs/docs/biganimal/release/administering_cluster/customizing_compliance/gcp_policy_definitions.mdx index 027784df202..bdf2a77d256 100644 --- a/product_docs/docs/biganimal/release/administering_cluster/customizing_compliance/gcp_policy_definitions.mdx +++ b/product_docs/docs/biganimal/release/administering_cluster/customizing_compliance/gcp_policy_definitions.mdx @@ -3,7 +3,7 @@ title: "Customizing Google Cloud compliance policies" description: "Customize Google Cloud compliance configuration settings to match BigAnimal's resource configurations" --- -Google Cloud uses Assured Workloads and the Organization Policy Service to ensure compliance rules are respected. Assured Workloads monitoring scans your environment in real time and provides alerts whenever organization policy changes violate the defined compliance posture. The monitoring dashboard shows which policy is being violated and provides instructions on how to resolve the finding. +Google Cloud uses Assured Workloads and the Organization Policy Service to ensure compliance rules are respected. Assured Workloads monitoring scans your environment in real time and provides alerts whenever organization policy changes violate the defined compliance posture. The monitoring dashboard shows which policy is being violated and provides instructions for resolving the finding. For more information, see: - [Overview of Assured Workloads](https://cloud.google.com/assured-workloads/docs/overview) From fd519c48907dbc7eeb08af38d13595fb9daa9c72 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Mon, 24 Jul 2023 13:36:22 -0400 Subject: [PATCH 15/29] Missed edit from first round --- .../preparing_cloud_account/preparing_gcp/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx index 00b29153297..67fd9394e58 100644 --- a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx @@ -17,7 +17,7 @@ Ensure you have at least the following combined roles: - roles/resourcemanager.projectIamAdmin - roles/compute.viewer -Or an equivalent single role such as: +Alternatively, you can have an equivalent single role, such as: - roles/owner ## Required APIs and services From e507e98c4172332addf86d8bcbdf607af9c0b329 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Mon, 24 Jul 2023 13:43:24 -0400 Subject: [PATCH 16/29] fixed typo --- .../02_connecting_your_cluster/02_connecting_from_aws/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/index.mdx index 4eb5574583d..9d902ef6c21 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/index.mdx @@ -14,7 +14,7 @@ The way you create a private endpoint differs when you're using your own AWS acc ## Using BigAnimal's cloud account -When using BigAnimal's cloud account, you provide BigAnimal with your AWS account ID when creating a cluster (see [Networking](/biganimal/latest/getting_started/creating_a_cluster/network-logs--telemetry-section)). BigAnimal, in turn, provides you with a AWS service name, which you can use to connect to your cluster privately. +When using BigAnimal's cloud account, you provide BigAnimal with your AWS account ID when creating a cluster (see [Networking](/biganimal/latest/getting_started/creating_a_cluster/network-logs--telemetry-section)). BigAnimal, in turn, provides you with an AWS service name, which you can use to connect to your cluster privately. 1. When creating your cluster, on the **Cluster Settings** tab, in the **Network** section: 1. Select **Private**. From 89de0fbf38b0e65985821016ea83c3e366d08b62 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 18 Jul 2023 11:19:41 -0400 Subject: [PATCH 17/29] edits to new Health check content --- product_docs/docs/pgd/3.7/harp/02_overview.mdx | 6 +++--- .../docs/pgd/3.7/harp/04_configuration.mdx | 18 +++++++++--------- .../docs/pgd/4/harp/04_configuration.mdx | 18 +++++++++--------- product_docs/docs/pgd/4/harp/index.mdx | 6 +++--- 4 files changed, 24 insertions(+), 24 deletions(-) diff --git a/product_docs/docs/pgd/3.7/harp/02_overview.mdx b/product_docs/docs/pgd/3.7/harp/02_overview.mdx index 177d184e1b0..80c6d066cbe 100644 --- a/product_docs/docs/pgd/3.7/harp/02_overview.mdx +++ b/product_docs/docs/pgd/3.7/harp/02_overview.mdx @@ -230,7 +230,7 @@ data centers as well. ### Health check -HARP provides the following HTTP(S) health check API endpoints. These APIs are `GET` requests and do not require a request body. See [Configurations](04_configuration#health-check-api-settings) for more details about enabling and configuring this. +HARP provides the following HTTP(S) health check API endpoints. These APIs are `GET` requests and don't require a request body. See [Configurations](04_configuration#health-check-api-settings) for more details about enabling and configuring this. ``` GET /health/is-ready @@ -239,11 +239,11 @@ GET /health/is-live #### Readiness -Readiness endpoint is available for `harp-proxy` only. On receiving valid 'GET' request, the proxy checks if it can successfully route connections to the current write leader. If the check returns successfully then API gives a response with a body containing `true` and a HTTP status code `200 (OK)`. Otherwise, it returns a body containing `false` with the HTTP status code `500 (Internal Server Error)`. +Readiness endpoint is available only for `harp-proxy`. On receiving a valid `'GET'` request, the proxy checks if it can successfully route connections to the current write leader. If the check returns successfully, then the API gives a response with a body containing `true` and a HTTP status code `200 (OK)`. Otherwise, it returns a body containing `false` with the HTTP status code `500 (Internal Server Error)`. #### Liveness -Liveness check either return `true` with HTTP status code `200 (OK)` or an error but never `false`. This is because the HTTP server listening for request is automatically stopped if the corresponding HARP service fails to start or exists. This API endpoint is available for `harp-manager` and `harp-proxy` services. +Liveness checks return either `true` with HTTP status code `200 (OK)` or an error. They never return `false` because the HTTP server listening for requests is stopped if the corresponding HARP service fails to start or exists. This API endpoint is available for `harp-manager` and `harp-proxy` services. ### BDR 3.7 compatibility diff --git a/product_docs/docs/pgd/3.7/harp/04_configuration.mdx b/product_docs/docs/pgd/3.7/harp/04_configuration.mdx index e93b3cfb8bf..5ef619d0112 100644 --- a/product_docs/docs/pgd/3.7/harp/04_configuration.mdx +++ b/product_docs/docs/pgd/3.7/harp/04_configuration.mdx @@ -121,24 +121,24 @@ dcs: ### Health check API settings -HARP provides [HTTP(S) health check APIs](02_overview#health-check). Add the below settings only if health check APIs are required. Specify all elements under a section named `http` with these multiple +HARP provides [HTTP(S) health check APIs](02_overview#health-check). Add the following settings only if health check APIs are required. Specify all elements under a section named `http` with these multiple supplementary entries: -- **`enable`**: Set `true` to enable HTTP(S) health check APIs. Defaults to `false`. +- **`enable`**: Set to `true` to enable HTTP(S) health check APIs. Defaults to `false`. -- **`host`**: Host name of HTTP(S) API server. Typically same as hostname of HARP service as it's running within the HARP service. Defaults to `0.0.0.0`. +- **`host`**: Host name of HTTP(S) API server. Typically the same as the hostname of the HARP service as it's running within the HARP service. Defaults to `0.0.0.0`. -- **`port`**: Port number of HTTP(S) server. Defaults to `8080`. +- **`port`**: Port number of HTTP(S) server. Defaults to `8080`. -- **`probes.timeout`**: Timeout value for the API endpoints. Defaults to `10s`. +- **`probes.timeout`**: Timeout value for the API endpoints. Defaults to `10s`. -- **`secure`**: Enable HTTPS. Defaults to `false`. +- **`secure`**: Enable HTTPS. Defaults to `false`. -The following `http` settings apply and are mandatory if `secure: true` is set. +The following `http` settings apply and are mandatory if `secure: true` is set: -- **`cert_file`**: HTTP server SSL certificate file. Mandatory if `secure` set to `true`. +- **`cert_file`**: HTTP server SSL certificate file. Mandatory if `secure` is set to `true`. -- **`key_file`**: HTTP server SSL key file. Mandatory if `secure` set to `true`. +- **`key_file`**: HTTP server SSL key file. Mandatory if `secure` is set to `true`. #### Example diff --git a/product_docs/docs/pgd/4/harp/04_configuration.mdx b/product_docs/docs/pgd/4/harp/04_configuration.mdx index 9c3f0c05761..23c2e4bd5e2 100644 --- a/product_docs/docs/pgd/4/harp/04_configuration.mdx +++ b/product_docs/docs/pgd/4/harp/04_configuration.mdx @@ -125,24 +125,24 @@ dcs: ### Health check API settings -HARP provides [HTTP(S) health check APIs](./#health-check). Add the below settings only if health check APIs are required. Specify all elements under a section named `http` with these multiple +HARP provides [HTTP(S) health check APIs](./#health-check). Add the following settings only if health check APIs are required. Specify all elements under a section named `http` with these multiple supplementary entries: -- **`enable`**: Set `true` to enable HTTP(S) health check APIs. Defaults to `false`. +- **`enable`**: Set to `true` to enable HTTP(S) health check APIs. Defaults to `false`. -- **`host`**: Host name of HTTP(S) API server. Typically same as hostname of HARP service as it's running within the HARP service. Defaults to `0.0.0.0`. +- **`host`**: Host name of HTTP(S) API server. Typically the same as the hostname of the HARP service as it's running within the HARP service. Defaults to `0.0.0.0`. -- **`port`**: Port number of HTTP(S) server. Defaults to `8080`. +- **`port`**: Port number of HTTP(S) server. Defaults to `8080`. -- **`probes.timeout`**: Timeout value for the API endpoints. Defaults to `10s`. +- **`probes.timeout`**: Timeout value for the API endpoints. Defaults to `10s`. -- **`secure`**: Enable HTTPS. Defaults to `false`. +- **`secure`**: Enable HTTPS. Defaults to `false`. -The following `http` settings apply and are mandatory if `secure: true` is set. +The following `http` settings apply and are mandatory if `secure: true` is set: -- **`cert_file`**: HTTP server SSL certificate file. Mandatory if `secure` set to `true`. +- **`cert_file`**: HTTP server SSL certificate file. Mandatory if `secure` is set to `true`. -- **`key_file`**: HTTP server SSL key file. Mandatory if `secure` set to `true`. +- **`key_file`**: HTTP server SSL key file. Mandatory if `secure` is set to `true`. #### Example diff --git a/product_docs/docs/pgd/4/harp/index.mdx b/product_docs/docs/pgd/4/harp/index.mdx index 174299186a1..f59aa3d2348 100644 --- a/product_docs/docs/pgd/4/harp/index.mdx +++ b/product_docs/docs/pgd/4/harp/index.mdx @@ -244,7 +244,7 @@ data centers as well. ### Health check -HARP provides the following HTTP(S) health check API endpoints. These APIs are `GET` requests and do not require a request body. See [Configurations](04_configuration#health-check-api-settings) for more details about enabling and configuring this. +HARP provides the following HTTP(S) health check API endpoints. These APIs are `GET` requests and don't require a request body. See [Configurations](04_configuration#health-check-api-settings) for more details about enabling and configuring this. ``` GET /health/is-ready @@ -253,8 +253,8 @@ GET /health/is-live #### Readiness -Readiness endpoint is available for `harp-proxy` only. On receiving valid 'GET' request, the proxy checks if it can successfully route connections to the current write leader. If the check returns successfully then API gives a response with a body containing `true` and a HTTP status code `200 (OK)`. Otherwise, it returns a body containing `false` with the HTTP status code `500 (Internal Server Error)`. +Readiness endpoint is available only for `harp-proxy`. On receiving a valid `'GET'` request, the proxy checks if it can successfully route connections to the current write leader. If the check returns successfully, then the API gives a response with a body containing `true` and a HTTP status code `200 (OK)`. Otherwise, it returns a body containing `false` with the HTTP status code `500 (Internal Server Error)`. #### Liveness -Liveness check either return `true` with HTTP status code `200 (OK)` or an error but never `false`. This is because the HTTP server listening for request is automatically stopped if the corresponding HARP service fails to start or exits. This API endpoint is available for `harp-manager` and `harp-proxy` services. +Liveness checks return either `true` with HTTP status code `200 (OK)` or an error. They never return `false` because the HTTP server listening for requests is stopped if the corresponding HARP service fails to start or exits. This API endpoint is available for `harp-manager` and `harp-proxy` services. From 43277e54faf8f138324692744f1473d5c2f53b76 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 18 Jul 2023 11:20:41 -0400 Subject: [PATCH 18/29] Update 02_overview.mdx --- product_docs/docs/pgd/3.7/harp/02_overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/3.7/harp/02_overview.mdx b/product_docs/docs/pgd/3.7/harp/02_overview.mdx index 80c6d066cbe..e3f4e336845 100644 --- a/product_docs/docs/pgd/3.7/harp/02_overview.mdx +++ b/product_docs/docs/pgd/3.7/harp/02_overview.mdx @@ -230,7 +230,7 @@ data centers as well. ### Health check -HARP provides the following HTTP(S) health check API endpoints. These APIs are `GET` requests and don't require a request body. See [Configurations](04_configuration#health-check-api-settings) for more details about enabling and configuring this. +HARP provides the following HTTP(S) health check API endpoints. These APIs are `GET` requests and don't require a request body. See [Configurations](04_configuration#health-check-api-settings) for more details about enabling and configuring this feature. ``` GET /health/is-ready From 732abde0acb22600730a1379341d35c7032c2e38 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 18 Jul 2023 11:23:20 -0400 Subject: [PATCH 19/29] Update index.mdx --- product_docs/docs/pgd/4/harp/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/4/harp/index.mdx b/product_docs/docs/pgd/4/harp/index.mdx index f59aa3d2348..c12fa463fd1 100644 --- a/product_docs/docs/pgd/4/harp/index.mdx +++ b/product_docs/docs/pgd/4/harp/index.mdx @@ -244,7 +244,7 @@ data centers as well. ### Health check -HARP provides the following HTTP(S) health check API endpoints. These APIs are `GET` requests and don't require a request body. See [Configurations](04_configuration#health-check-api-settings) for more details about enabling and configuring this. +HARP provides the following HTTP(S) health check API endpoints. These APIs are `GET` requests and don't require a request body. See [Configurations](04_configuration#health-check-api-settings) for more details about enabling and configuring this feature. ``` GET /health/is-ready From 4aed5a006566d9b9359f6b8ce4c1a514fc0b8eb4 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 18 Jul 2023 11:28:46 -0400 Subject: [PATCH 20/29] removed parens from new text --- product_docs/docs/pgd/5/ddl.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/ddl.mdx b/product_docs/docs/pgd/5/ddl.mdx index 0e0ccc16514..c9c86be7029 100644 --- a/product_docs/docs/pgd/5/ddl.mdx +++ b/product_docs/docs/pgd/5/ddl.mdx @@ -150,7 +150,7 @@ take a long time to acquire the lock. Hence it's preferable to run DDLs from a single node or the nodes that have nearly caught up with replication changes originating at other nodes. -The second kind is known as a global DML lock (or relation DML lock). This kind of lock is used when +The second kind is known as a global DML lock or relation DML lock. This kind of lock is used when either `ddl_locking = on` or `ddl_locking = dml`, and the DDL statement might cause in-flight DML statements to fail. These failures can occur when you add or modify a constraint, such as a unique constraint, check constraint, or NOT NULL constraint. From 794277008ba6513e487344567c0c30a126c83be1 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Tue, 25 Jul 2023 09:57:55 +0100 Subject: [PATCH 21/29] Fixed typo --- advocacy_docs/pg_extensions/pg_tuner/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/pg_extensions/pg_tuner/index.mdx b/advocacy_docs/pg_extensions/pg_tuner/index.mdx index d5b698a9161..3e9f26725e0 100644 --- a/advocacy_docs/pg_extensions/pg_tuner/index.mdx +++ b/advocacy_docs/pg_extensions/pg_tuner/index.mdx @@ -14,4 +14,4 @@ EDB Postgres Tuner is a PostgreSQL extension that automates 15+ years of EDB Pos Postgres uses some conservative settings to cover different host sizes. Some of the settings provided by Postgres are unsuitable because they don't take advantage of the available resources. Configuration parameters set by `initdb` don't account for the amount of memory, the number of CPU cores, and the kind of storage devices available to set appropriate values for parameters. Some parameters depend on the workload. The workload provides metrics to use to fine-tune some parameters dynamically. -This extension provides safe recommendations that maximize the use of available resources. It aso allows you to control if and when to apply the changes. EDB Postgres Tuner enables you to apply tuning recommendations automatically or view tuning recommendations and selectively apply them. It's now possible to successfully manage demanding Postgres databases without tuning expertise. +This extension provides safe recommendations that maximize the use of available resources. It also allows you to control if and when to apply the changes. EDB Postgres Tuner enables you to apply tuning recommendations automatically or view tuning recommendations and selectively apply them. It's now possible to successfully manage demanding Postgres databases without tuning expertise. From 4296c2c3ecdc2bd1fd1d99ce28bda7accce84e10 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Tue, 25 Jul 2023 11:54:56 +0100 Subject: [PATCH 22/29] Simplify upgrade messaging --- product_docs/docs/pgd/4/rel_notes/pgd_4.3.1-1_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.1-1_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.1-1_rel_notes.mdx index 93bbdcf76fc..a24fd832aed 100644 --- a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.1-1_rel_notes.mdx +++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.1-1_rel_notes.mdx @@ -5,7 +5,7 @@ navTitle: "Version 4.3.1-1" EDB Postgres Distributed version 4.3.1-1 is a minor release of EDB Postgres Distributed 4, which includes bug fixes for issues identified in previous versions. -It includes HARP 2.2.3 with bug fixes and enhancements. If you are using HARP 2.2.3 or earlier, we recommend that you upgrade to HARP 2.3.0. +If you are using any previous release of HARP, we recommend that you upgrade to HARP 2.3.0. !!! Note This version is required for EDB Postgres Advanced Server versions 12.15, 13.11, 14.8, and later. From 28830f715b49e0ab426f4ccc58f1afbf678cd6e1 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jul 2023 08:27:49 -0400 Subject: [PATCH 23/29] Replication Server: super user permissions not required for a Subscription database user. --- .../01_prerequisites/05_preparing_sub_database.mdx | 5 ----- 1 file changed, 5 deletions(-) diff --git a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx index 6bb2d289518..2c481de18de 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx @@ -20,11 +20,6 @@ Choose or create a database passworded user name to serve as the subscription da When creating the subscription database definition, enter the subscription database user name in the Subscription Service – Add Database dialog box (see [Adding a subscription database](../03_creating_subscription/02_adding_subscription_database/#adding_subscription_database)). -The subscription database user must also be able to run the `TRUNCATE` command on the subscription tables. This requires the following: - -- Superuser privileges. -- The ability to modify the system catalog tables to disable foreign key constraints on subscription tables. See [Disabling foreign key constraints for snapshot replications](../../10_appendix/03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication) for more information on this requirement. - When choosing the subscription database user name, you can either: - For the subscription database user name, use the Postgres user name postgres created when you installed PostgreSQL (enterprisedb for EDB Postgres Advanced Server installed in Oracle-compatible configuration mode). If you choose this option, skip Step 1 and proceed to Step 2. From cb6d909ecb7307dadb0dfbd6f717733478917e98 Mon Sep 17 00:00:00 2001 From: Stefan Fercot Date: Tue, 25 Jul 2023 15:19:43 +0200 Subject: [PATCH 24/29] Update debian11_quick_start Co-authored-by: Israel --- .../supported-open-source/patroni/debian11_quick_start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx b/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx index 3df7660a5ec..c794c3551e2 100644 --- a/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx +++ b/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx @@ -171,7 +171,7 @@ EOF `$MY_IP` and `$MY_NAME` are specific to the local host. Otherwise, the `patroni.yml` configuration is the same on all Patroni nodes. -Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. Before Patroni [version `3.0.3`](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), remove the `bin_name` setting from the configuration and create a symbolic link to let Patroni find that binary: +Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. As `postgresql.bin_name` setting was introduced in [version `3.0.3`](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), if you are running Patroni older than that, then remove the `bin_name` setting from the configuration and create a symbolic link to let Patroni find that binary: ```bash sudo ln -s /usr/lib/edb-as/15/bin/edb-postgres /usr/lib/edb-as/15/bin/postgres From 84cb82dba11566bd1089093f802c87e3abda1cbc Mon Sep 17 00:00:00 2001 From: Stefan Fercot Date: Tue, 25 Jul 2023 15:19:57 +0200 Subject: [PATCH 25/29] Update rhel8_quick_start Co-authored-by: Israel --- .../supported-open-source/patroni/rhel8_quick_start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx b/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx index c8dbb6e403b..517adae2642 100644 --- a/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx +++ b/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx @@ -173,7 +173,7 @@ EOF `$MY_IP` and `$MY_NAME` are specific to the local host. Otherwise, the `patroni.yml` configuration is the same on all Patroni nodes. -Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. Before Patroni [version `3.0.3`](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), remove the `bin_name` setting from the configuration and create a symbolic link to let Patroni find that binary: +Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. As `postgresql.bin_name` setting was introduced in [version `3.0.3`](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), if you are running Patroni older than that, then remove the `bin_name` setting from the configuration and create a symbolic link to let Patroni find that binary: ```bash sudo ln -s /usr/edb/as15/bin/edb-postgres /usr/edb/as15/bin/postgres From c96a8dd4479b8dbf05de54805f4dc2caf108030f Mon Sep 17 00:00:00 2001 From: Stefan Fercot Date: Tue, 25 Jul 2023 15:23:46 +0200 Subject: [PATCH 26/29] small rephrase --- .../supported-open-source/patroni/debian11_quick_start.mdx | 2 +- .../supported-open-source/patroni/rhel8_quick_start.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx b/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx index c794c3551e2..a3a864c73e3 100644 --- a/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx +++ b/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx @@ -171,7 +171,7 @@ EOF `$MY_IP` and `$MY_NAME` are specific to the local host. Otherwise, the `patroni.yml` configuration is the same on all Patroni nodes. -Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. As `postgresql.bin_name` setting was introduced in [version `3.0.3`](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), if you are running Patroni older than that, then remove the `bin_name` setting from the configuration and create a symbolic link to let Patroni find that binary: +Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. As the `postgresql.bin_name` setting was introduced in the [`3.0.3` release](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), remove it from the configuration if you are running an older version and create a symbolic link to let Patroni find that binary: ```bash sudo ln -s /usr/lib/edb-as/15/bin/edb-postgres /usr/lib/edb-as/15/bin/postgres diff --git a/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx b/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx index 517adae2642..259e7fe3a7f 100644 --- a/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx +++ b/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx @@ -173,7 +173,7 @@ EOF `$MY_IP` and `$MY_NAME` are specific to the local host. Otherwise, the `patroni.yml` configuration is the same on all Patroni nodes. -Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. As `postgresql.bin_name` setting was introduced in [version `3.0.3`](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), if you are running Patroni older than that, then remove the `bin_name` setting from the configuration and create a symbolic link to let Patroni find that binary: +Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. As the `postgresql.bin_name` setting was introduced in the [`3.0.3` release](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), remove it from the configuration if you are running an older version and create a symbolic link to let Patroni find that binary: ```bash sudo ln -s /usr/edb/as15/bin/edb-postgres /usr/edb/as15/bin/postgres From ec8fa46b18cc0e79637e92553709c693b76a10d3 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 25 Jul 2023 09:40:48 -0400 Subject: [PATCH 27/29] Update product_docs/docs/pgd/5/architectures.mdx Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> --- product_docs/docs/pgd/5/architectures.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/architectures.mdx b/product_docs/docs/pgd/5/architectures.mdx index 251fdb1b2a5..aee575d6b11 100644 --- a/product_docs/docs/pgd/5/architectures.mdx +++ b/product_docs/docs/pgd/5/architectures.mdx @@ -144,7 +144,7 @@ Use these criteria to help you to select the appropriate Always On architecture. ## Adding flexibility to the standard architectures -You can deploy the single-location architecture in as many locations as you want. Doing so provides the data resiliency needed and proximity to applications and to the users maintaining the data. While EDB Postgres Distributed has a variety of conflict-handling approaches available, in general take care to minimize the number of expected collisions if allowing write activity from geographically disparate locations. +To provide the data resiliency needed and proximity to applications and to the users maintaining the data, the single-location architecture can be deployed in as many locations as you want. While EDB Postgres Distributed has a variety of conflict-handling approaches available, do take care to minimize the number of expected collisions if allowing write activity from geographically disparate locations. You can also expand the standard architectures with two additional types of nodes: From 7e3f3bc27d20d2375c881d550063313d956b1345 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Fri, 14 Jul 2023 17:51:51 +0100 Subject: [PATCH 28/29] Internalised links - fixed old TPA version numbers Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/4/rel_notes/index.mdx | 22 ++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/product_docs/docs/pgd/4/rel_notes/index.mdx b/product_docs/docs/pgd/4/rel_notes/index.mdx index 525bf15937b..ecbad461708 100644 --- a/product_docs/docs/pgd/4/rel_notes/index.mdx +++ b/product_docs/docs/pgd/4/rel_notes/index.mdx @@ -38,16 +38,16 @@ The EDB Postgres Distributed documentation describes the latest version of EDB P | ------------ | ---------------------------- | ----- | ----- | ----- | -------------------------------------------------------------------------------- | | 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](https://techsupport.enterprisedb.com/customer_portal/sw/tpa/trunk/239/) | -| 2023 Feb 14 | [4.3.0](pgd_4.3.0_rel_notes) | 4.3.0 | 2.2.1 | 1.1.0 | [23.9](https://techsupport.enterprisedb.com/customer_portal/sw/tpa/trunk/239/) | -| 2022 Dec 14 | [4.2.2](pgd_4.2.2_rel_notes) | 4.2.2 | 2.2.1 | 1.1.0 | [23.9](https://techsupport.enterprisedb.com/customer_portal/sw/tpa/trunk/239/) | -| 2022 Nov 16 | [4.2.1](pgd_4.2.1_rel_notes) | 4.2.1 | 2.2.1 | 1.1.0 | [23.7](https://techsupport.enterprisedb.com/customer_portal/sw/tpa/trunk/237/) | -| 2022 Aug 22 | [4.2.0](pgd_4.2.0_rel_notes) | 4.2.0 | 2.2.0 | 1.1.0 | [23.5](https://techsupport.enterprisedb.com/customer_portal/sw/tpa/trunk/235/) | -| 2022 June 21 | [4.1.1](pgd_4.1.1_rel_notes) | 4.1.1 | 2.1.1 | 1.0.0 | [23.2](https://techsupport.enterprisedb.com/customer_portal/sw/tpa/trunk/232/) | -| 2022 May 17 | [4.1.0](pgd_4.1.0_rel_notes) | 4.1.0 | 2.1.0 | 1.0.0 | [23.1](https://techsupport.enterprisedb.com/customer_portal/sw/tpa/trunk/231/) | -| 2022 Mar 31 | [4.0.3](pgd_4.0.3_rel_notes) | - | 2.0.3 | - | [22.10](https://techsupport.enterprisedb.com/customer_portal/sw/tpa/trunk/2210/) | -| 2022 Feb 24 | [4.0.2](pgd_4.0.2_rel_notes) | 4.0.2 | 2.0.2 | - | [22.9](https://techsupport.enterprisedb.com/customer_portal/sw/tpa/trunk/229/) | -| 2022 Jan 31 | [4.0.1](pgd_4.0.1_rel_notes) | 4.0.1 | 2.0.1 | - | [22.6](https://techsupport.enterprisedb.com/customer_portal/sw/tpa/trunk/2206/) | -| 2021 Dec 01 | [4.0.0](pgd_4.0.0_rel_notes) | 4.0.0 | 2.0.0 | - | [22.9](https://techsupport.enterprisedb.com/customer_portal/sw/tpa/trunk/2106/) | +| 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) | +| 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 | From f0c80c8e5d56c820e6f6833a0ab17df7114fc397 Mon Sep 17 00:00:00 2001 From: Stefan Fercot Date: Tue, 25 Jul 2023 19:02:26 +0200 Subject: [PATCH 29/29] rephrase --- .../supported-open-source/patroni/debian11_quick_start.mdx | 2 +- .../supported-open-source/patroni/rhel8_quick_start.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx b/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx index a3a864c73e3..7cceffdee02 100644 --- a/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx +++ b/advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx @@ -171,7 +171,7 @@ EOF `$MY_IP` and `$MY_NAME` are specific to the local host. Otherwise, the `patroni.yml` configuration is the same on all Patroni nodes. -Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. As the `postgresql.bin_name` setting was introduced in the [`3.0.3` release](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), remove it from the configuration if you are running an older version and create a symbolic link to let Patroni find that binary: +Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. The `postgresql.bin_name` setting does not exist in Patroni prior to the [`3.0.3` release](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303) and will be silently ignored by older versions. For these versions, create an appropriately named symbolic link that points to the relevant binary: ```bash sudo ln -s /usr/lib/edb-as/15/bin/edb-postgres /usr/lib/edb-as/15/bin/postgres diff --git a/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx b/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx index 259e7fe3a7f..e44bf32bfcd 100644 --- a/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx +++ b/advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx @@ -173,7 +173,7 @@ EOF `$MY_IP` and `$MY_NAME` are specific to the local host. Otherwise, the `patroni.yml` configuration is the same on all Patroni nodes. -Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. As the `postgresql.bin_name` setting was introduced in the [`3.0.3` release](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303), remove it from the configuration if you are running an older version and create a symbolic link to let Patroni find that binary: +Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. The `postgresql.bin_name` setting does not exist in Patroni prior to the [`3.0.3` release](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303) and will be silently ignored by older versions. For these versions, create an appropriately named symbolic link that points to the relevant binary: ```bash sudo ln -s /usr/edb/as15/bin/edb-postgres /usr/edb/as15/bin/postgres