diff --git a/product_docs/docs/biganimal/release/migration/index.mdx b/product_docs/docs/biganimal/release/migration/index.mdx index b4a94fdd34d..c3716ecd4df 100644 --- a/product_docs/docs/biganimal/release/migration/index.mdx +++ b/product_docs/docs/biganimal/release/migration/index.mdx @@ -6,14 +6,16 @@ EDB provides migration tools to bring data from Oracle, PostgresSQL, and EDB Pos ## Migrating from Oracle -[Migration Portal](/migration_portal/latest) provides the details for executing the migration steps using Migration Portal: +Review the EDB [Migration Handbook](/migrating/oracle/) for helpful considerations and information when migrating from Oracle. + +EDB also provides a tool, [Migration Portal](/migration_portal/latest), which provides the details for executing the migration steps: 1. [Schema extraction](/migration_portal/latest/04_mp_migrating_database/01_mp_schema_extraction/) 2. [Schema assessment](/migration_portal/latest/04_mp_migrating_database/02_mp_schema_assessment/) 3. [Schema migration](/migration_portal/latest/04_mp_migrating_database/03_mp_schema_migration/) 4. [Data migration](/migration_portal/latest/04_mp_migrating_database/04_mp_data_migration/) -You can also use the Migration Toolkit for the data migration step. This toolkit is a good option for smaller databases. +You can also use the [Migration Toolkit](/migration_toolkit/latest/) for the data migration step. This toolkit is a good option for smaller databases. ## Accessing remote Oracle servers from BigAnimal diff --git a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx index a8f415a1b59..701148a1e35 100644 --- a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx +++ b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx @@ -6,5 +6,5 @@ New features, enhancements, bug fixes, and other changes in EDB\*Plus 41.2.0 inc | Type | Description | | ----------- | -------------------------------------------------------------- | -| Enhancement | The connection string syntax in EDB\*Plus now supports multi-host connectivity. When multiple hosts are specified, you can also use the `targetServerType` connection property and set it to `primary` to ensure that EDB\*Plus always establishes a connection with the active primary EDB Postgres Advanced Server (EPAS) database server. [Support ticket #92553] | +| Enhancement | The connection string syntax in EDB\*Plus now supports multi-host connectivity. When multiple hosts are specified, you can also use the `targetServerType` connection property and set it to `primary` to ensure that EDB\*Plus always establishes a connection with the active primary EDB Postgres Advanced Server database server. [Support ticket #92553] | | Bug fix | Fixed the issue whereby the ECHO command wasn't emitting the SQL statement in the spooled file when using EDB\*Plus in an interactive session. [Support ticket # 83580] | diff --git a/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx b/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx index b6902fe3f4c..561c258e9f3 100644 --- a/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx +++ b/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx @@ -40,7 +40,7 @@ edbplus [ -S[ILENT ] ] [ | /NOLOG ] [ @[. ] ] `port` is the port number receiving connections on the database server. The default is `5444`. !!! Note - If multiple hosts are specified, the driver will try to connect once to each of them in the order specified until the connection succeeds. If none succeed, a normal connection exception is thrown. Including the `targetServerType` connection property and setting it to `primary` ensures that the connection is only made to a primary database server. + If you specify multiple hosts, the driver tries to connect once to each of them in the order specified until the connection succeeds. If none succeed, a normal connection exception is thrown. Including the `targetServerType` connection property and setting it to `primary` ensures that the connection is made only to a primary database server. `dbname` is the name of the database to connect to. The default is `edb`. @@ -50,7 +50,7 @@ edbplus [ -S[ILENT ] ] [ | /NOLOG ] [ @[. ] ] edbplus.sh enterprisedb/password@[fe80::20c:29ff:fe7c:78b2]:5444/edb ``` - The `pg_hba.conf` file for the database server must contain an appropriate entry for the IPv6 connection. The following example shows an entry that allows all addresses: + The `pg_hba.conf` file for the database server must contain an appropriate entry for the IPv6 connection. This example shows an entry that allows all addresses: ```text # TYPE DATABASE USER ADDRESS METHOD diff --git a/product_docs/docs/edb_plus/41/06_command_summary.mdx b/product_docs/docs/edb_plus/41/06_command_summary.mdx index a43cfdfe2d2..10348cfde1c 100644 --- a/product_docs/docs/edb_plus/41/06_command_summary.mdx +++ b/product_docs/docs/edb_plus/41/06_command_summary.mdx @@ -298,9 +298,9 @@ CON[NECT] [/][@{ | } ] Where: - `username` is a database user name with which to connect to the database. + `username` is a database username with which to connect to the database. - `password` is the password associated with the specified user name. If you don't provide a `password` but a password is required for authentication, a search is made for a password file, first in the home directory of the Linux operating system account invoking EDB\*Plus (or in the `%APPDATA%\postgresql\` directory for Windows) and then at the location specified by the `PGPASSFILE` environment variable. The password file is `.pgpass` on Linux hosts and `pgpass.conf` on Windows hosts. The following is an example on a Windows host: + `password` is the password associated with the specified username. If you don't provide a password, but a password is required for authentication, a search is made for a password file. The search looks first in the home directory of the Linux operating system account invoking EDB\*Plus (or in the `%APPDATA%\postgresql\` directory for Windows) and then at the location specified by the `PGPASSFILE` environment variable. The password file is `.pgpass` on Linux hosts and `pgpass.conf` on Windows hosts. The following is an example on a Windows host: ```text C:\Users\Administrator\AppData\Roaming\postgresql\pgpass.conf @@ -323,7 +323,7 @@ Disconnected from EnterpriseDB Database. Connected to EnterpriseDB 14.0.0 (localhost:5445/edb) AS smith ``` -In this session, the connection is changed to user name `enterprisedb`. The host defaults to the `localhost`, the port defaults to `5444` (which isn't the same as the port previously used), and the database defaults to `edb`. +In this session, the connection is changed to the username `enterprisedb`. The host defaults to the localhost, the port defaults to `5444` (which isn't the same as the port previously used), and the database defaults to `edb`. ```sql SQL> CONNECT enterprisedb/password @@ -331,7 +331,7 @@ Disconnected from EnterpriseDB Database. Connected to EnterpriseDB 14.0.0 (localhost:5444/edb) AS enterprisedb ``` -The following example illustrates connectivity for a multi-node cluster (one primary node and two secondary nodes) setup. The given multi-host `connectstring` syntax is used to establish a connection with the active primary database server. In this case, using `CONNECT` command, the connection is established with the primary database node on host `192.168.22.24` at port `5444`. +This example shows connectivity for a multi-node cluster (one primary node and two secondary nodes) setup. The given multi-host `connectstring` syntax is used to establish a connection with the active primary database server. In this case, using `CONNECT` command, the connection is established with the primary database node on host `192.168.22.24` at port `5444`. ```sql SQL> CONNECT enterprisedb/edb@192.168.22.24:5444,192.168.22.25:5445,192.168.22.26:5446/edb?targetServerType=primary diff --git a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx index 524d5d631c0..9a03d92300c 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx @@ -9,26 +9,29 @@ Once you have upgraded to this version of EDB Postgres Advanced Server, you will #### EDB Postgres Advanced Server 15.4.0 includes the following enhancements and bug fixes: -| Type | Description | Addresses                | -| -------------- | -------------------------------------------------------------------------------------------------------------------------------------| --------------------- | -| Security fix | EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path. | [CVE-2023-XXXXX-1](/security/advisories/cve2023xxxxx1/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser. | [CVE-2023-XXXXX-2](/security/advisories/cve2023xxxxx2/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() | [CVE-2023-XXXXX-3](/security/advisories/cve2023xxxxx3/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass | [CVE-2023-XXXXX-4](/security/advisories/cve2023xxxxx4/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for materialized views | [CVE-2023-XXXXX-5](/security/advisories/cve2023xxxxx5/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL | [CVE-2023-XXXXX-6](/security/advisories/cve2023xxxxx6/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for large objects | [CVE-2023-XXXXX-7](/security/advisories/cve2023xxxxx7/) | 11+ -| Security fix | EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission | [CVE-2023-XXXXX-8](/security/advisories/cve2023xxxxx8/) | 11+ -| Bug fix | Allowed subtypes in INDEX BY clause of the packaged collection. | #1371 | 11+ -| Bug fix | Fixed %type resolution when pointing to a packaged type field. | #1243 | 11+ -| Bug fix | Profile: Fixed upgrade when `REUSE` constraints were `ENABLED`/`DISABLED`. | #92739 | 11+ -| Bug fix | Set correct collation for packaged cursor parameters. | #92739 | 11+ -| Bug fix | Rolled back autonomous transaction creating pg_temp in case of error. | #91614 | 11+ -| Bug fix | Added checks to ensure required WAL logging in EXCHANGE PARTITION command.| | 13+ -| Bug fix | Dumped/restored the sequences created for GENERATED AS IDENTITY constraint. | #90658 | 14+ -| Bug fix | Skipped updating the last DDL time for the parent table in CREATE INDEX. | #91270 | 14+ -| Bug fix | Removed existing package private procedure or function entries from the edb_last_ddl_time while replacing the package body. | | 14+ -| Bug fix | Fixed libpq to allow multiple PQprepare() calls under the same transaction. | #94735 | 14+ + +| Type | Description | Addresses                | | +| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | --- | +| Upstream merge | Merged with community PostgreSQL 15.4. See the [PostgreSQL 15 Release Notes](https://www.postgresql.org/docs/15/release-15-4.html) for more information. | | | +| Security fix | EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path. | [CVE-2023-XXXXX-1](/security/advisories/cve2023xxxxx1/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser. | [CVE-2023-XXXXX-2](/security/advisories/cve2023xxxxx2/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() | [CVE-2023-XXXXX-3](/security/advisories/cve2023xxxxx3/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass | [CVE-2023-XXXXX-4](/security/advisories/cve2023xxxxx4/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for materialized views | [CVE-2023-XXXXX-5](/security/advisories/cve2023xxxxx5/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL | [CVE-2023-XXXXX-6](/security/advisories/cve2023xxxxx6/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for large objects | [CVE-2023-XXXXX-7](/security/advisories/cve2023xxxxx7/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission | [CVE-2023-XXXXX-8](/security/advisories/cve2023xxxxx8/) | 11+ | +| Bug fix | Allowed subtypes in INDEX BY clause of the packaged collection. | #1371 | 11+ | +| Bug fix | Fixed %type resolution when pointing to a packaged type field. | #1243 | 11+ | +| Bug fix | Profile: Fixed upgrade when `REUSE` constraints were `ENABLED`/`DISABLED`. | #92739 | 11+ | +| Bug fix | Set correct collation for packaged cursor parameters. | #92739 | 11+ | +| Bug fix | Rolled back autonomous transaction creating pg_temp in case of error. | #91614 | 11+ | +| Bug fix | Added checks to ensure required WAL logging in EXCHANGE PARTITION command. | | 13+ | +| Bug fix | Dumped/restored the sequences created for GENERATED AS IDENTITY constraint. | #90658 | 14+ | +| Bug fix | Skipped updating the last DDL time for the parent table in CREATE INDEX. | #91270 | 14+ | +| Bug fix | Removed existing package private procedure or function entries from the edb_last_ddl_time while replacing the package body. | | 14+ | +| Bug fix | Fixed libpq to allow multiple PQprepare() calls under the same transaction. | #94735 | 14+ | +| Bug fix | Fixed a memory leak experienced when using EDB Postgres Distributed (PGD) with Transparent Data Encryption (TDE). | #93936 | | !!! Note Addresses Entries in the Addresses column are either CVE numbers or, if preceded by #, a customer case number. diff --git a/product_docs/docs/pge/15/release_notes/index.mdx b/product_docs/docs/pge/15/release_notes/index.mdx index 0d513be5602..82131a33b20 100644 --- a/product_docs/docs/pge/15/release_notes/index.mdx +++ b/product_docs/docs/pge/15/release_notes/index.mdx @@ -1,6 +1,7 @@ --- title: "Release notes" navigation: + - rel_notes15.4 - rel_notes15.3 - rel_notes15.2 --- @@ -10,6 +11,7 @@ cover what was new in each release. | Version | Release date | | ------------------------ | ------------ | +| [15.4](rel_notes15.4) | 21 Aug 2023 | | [15.3](rel_notes15.3) | 11 May 2023 | | [15.2](rel_notes15.2) | 14 Feb 2023 | diff --git a/product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx b/product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx new file mode 100644 index 00000000000..f26c12e7833 --- /dev/null +++ b/product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx @@ -0,0 +1,14 @@ +--- +title: "EDB Postgres Extended Server version 15.4" +navTitle: Version 15.4 +--- + +New features, enhancements, bug fixes, and other changes in EDB Postgres Extended Server 15.2 include: + +| Type | Description | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Upstream merge | Merged with community PostgreSQL 15.4. See the [PostgreSQL 15 Release Notes](https://www.postgresql.org/docs/15/release-15-4.html) for more information. | +| Bug fix | Fixed a memory leak experienced when using EDB Postgres Distributed (PGD) with Transparent Data Encryption (TDE). [Support issue: #93936] | + + +