diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/creating_cluster/creating_a_cluster.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/creating_cluster/creating_a_cluster.mdx index 23927134752..f4fd50a94fb 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/creating_cluster/creating_a_cluster.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/creating_cluster/creating_a_cluster.mdx @@ -7,8 +7,6 @@ redirects: - /purl/upm/cluster-settings-tab/ - /purl/upm/read-only-connections/ - /purl/upm/csp-auth/ - - /purl/upm/csp-azure-ad-usermanagement/ - - /purl/upm/csp-aws-ad-usermanagement/ - /purl/upm/create-a-cluster/ - /purl/upm/private-endpoints-info/ - /purl/upm/read-only-workloads/ @@ -173,7 +171,7 @@ The following options aren't available when creating your cluster: When provisioning database storage, not all of the storage space you specify is available for holding your data. Some space is reserved for other purposes. For a full explanation of the structure of a Postgres data directory, see [Database File Layout](https://www.postgresql.org/docs/current/storage-file-layout.html). You can make more storage space available for data if you specify separate storage for write ahead logs (WAL). -8. In the **Network, Logs, & Telemetry** section: +8. In the **Network, Logs, & Telemetry** section: In **Connectivity Type**, specify whether to use private or public networking. Networking is set to **Public** by default. Public means that any client can connect to your cluster’s public IP address over the internet. Optionally, you can limit traffic to your public cluster by specifying an IP allowlist, which allows access only to certain blocks of IP addresses. To limit access, select **Use allowlists** and add one or more classless inter-domain routing (CIDR) blocks. CIDR is a method for allocating IP addresses and IP routing to a whole network or subnet. If you have any CIDR block entries, access is limited to those IP addresses. If none are specified, all network traffic is allowed. @@ -224,8 +222,12 @@ For more information, see [Periodic maintenance](/edb-postgres-ai/cloud-service/ ### Connections + + #### Read-only workloads + + !!! Note The **Read-only Workloads** option is not available on single node clusters. @@ -259,6 +261,8 @@ Use the **PgBouncer Configuration Settings** menu to set PgBouncer-specific sett #### Identity and Access Management (IAM) Authentication + + Enable **Identity and Access Management (IAM) Authentication** to turn on the ability to log in to Postgres using your AWS IAM credentials. For this feature to take effect, after you create the cluster, you must add each user to a role that uses AWS IAM authentication in Postgres. For details, see [IAM authentication for Postgres](/edb-postgres-ai/cloud-service/using_cluster/postgres_access/database_authentication/#iam-authentication-for-postgres). #### Superuser Access @@ -267,6 +271,8 @@ Enable **Superuser Access** to grant superuser privileges to the edb_admin role. ### Security + + Enable **Transparent Data Encryption (TDE)** to use your own encryption key. This option is available for EDB Postgres Advanced Server and EDB Postgres Extended Server for version 15 and later. Select an encryption key from your project and region to encrypt the cluster with TDE. To learn more about TDE support, see [Transparent Data Encryption](/edb-postgres-ai/cloud-service/security/security/#your-own-encryption-key---transparent-data-encryption-tde). !!!Note "Important" diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/connecting_azure.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/connecting_azure.mdx index 6dfa692e370..5366d01c476 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/connecting_azure.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/connecting_azure.mdx @@ -2,6 +2,7 @@ title: Connecting your Azure cloud navTitle: Azure redirects: + - /purl/upm/azure-subscription/ - /biganimal/latest/getting_started/02_connecting_to_your_cloud/connecting_azure/ #generated for BigAnimal URL path removal branch - /biganimal/latest/getting_started/02_azure_market_setup/ --- diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/index.mdx index c252d8bed0b..f0958c08f43 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/index.mdx @@ -2,7 +2,6 @@ title: Connecting your cloud description: How to connect your own cloud account to the Cloud Service redirects: - - /purl/upm/azure-subscription/ - /purl/upm/connect-your-cloud-overview/ - /purl/upm/connect-your-cloud/ - /biganimal/latest/getting_started/02_connect_cloud_account/ diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/managing_regions.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/managing_regions.mdx index e937591a253..569be52702d 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/managing_regions.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/managing_regions.mdx @@ -36,6 +36,9 @@ You can activate a region ahead of time using the Regions page. ## Suspend, reactivate, or delete a region + + + Before you suspend or delete a region, you must delete all clusters in that region. 1. On the left panel, select **Regions**. diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/index.mdx index 63e27c31d4f..80b01550dc3 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/index.mdx @@ -4,7 +4,6 @@ indexCards: simple description: When using Your Cloud Account, how to ensure its readiness to work with EDB Postgres AI. redirects: - /purl/upm/cloud-readiness/ - - /purl/upm/azure-raise-resource-limits/ - /biganimal/latest/getting_started/01_check_resource_limits/ - /biganimal/latest/getting_started/preparing_cloud_account/ #generated for BigAnimal URL path removal branch navigation: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/index.mdx index 6578a8dc1ad..874b307e4de 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/index.mdx @@ -2,6 +2,7 @@ title: "Preparing your Azure account" description: Prepare your Azure account to manage databases on EDB Postgres AI Cloud Service. redirects: + - /purl/upm/azure-raise-resource-limits/ - /biganimal/latest/getting_started/01_preparing_azure/ - /biganimal/latest/getting_started/preparing_cloud_account/01_preparing_azure/ #generated for BigAnimal URL path removal branch --- diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/backup_and_restore.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/backup_and_restore.mdx index 869c160a29b..b09154bddb8 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/backup_and_restore.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/backup_and_restore.mdx @@ -43,6 +43,8 @@ To determine the replication lag, you can compare the last log sequence number ( ## Restores + + If a restore is necessary—for example, in case of an accidental `DROP TABLE` statement—you can restore clusters to any point in the backup retention period. Cluster restores aren't performed in place on an existing cluster. Instead, a new cluster is created and initialized with data from the backup archive. Restores must replay the transaction logs between the most recent full database backup and the target restore point. Thus restore times (that is, RTO) depend on the write activity in the source cluster. diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/modifying_your_cluster/05_db_configuration_parameters.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/modifying_your_cluster/05_db_configuration_parameters.mdx index e21188d29ad..4f4bc0ba9d7 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/modifying_your_cluster/05_db_configuration_parameters.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/modifying_your_cluster/05_db_configuration_parameters.mdx @@ -23,6 +23,8 @@ Not all database configuration parameters are supported by Cloud Service. Some p ## Using formulas for parameter values + + In addition to entering specific values for parameters, for some parameters you can specify formulas to calculate a value. You can use formulas for parameters of type integer and real in ternary formulas, such as the [shared buffer example](#examples), using the following operators: `+ - / * > >= < <= == != && || ! ? : ( )`. Use `?` and `:` . Use `( )` to specify [order of operations](#order-of-operations), if needed. GUCs used in formulas must also be of type integer or real. All arithmetic is done on 64-bit floating point values rounded to an integer result if the target GUC is of type integer and not real. BigAnimal has what we refer to as *psuedo GUCs* to help with creating equations. These read-only GUCs are: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/periodic_maintenance.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/periodic_maintenance.mdx index 847312e0855..c48c0c62da7 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/periodic_maintenance.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/managing_your_cluster/periodic_maintenance.mdx @@ -18,6 +18,8 @@ In some cases, these updates might terminate existing network connections to you ## Specifying maintenance windows + + If you want to control when the updates are pushed, you can specify a weekly maintenance window for each cluster or each data group in the case of a distributed high-availability cluster. BigAnimal displays a *scheduled maintenance* message on your cluster list four hours prior to the scheduled maintenance time to remind you of the upcoming maintenance window. This reminder allows you to make any necessary preparations, such as saving your work and closing any open connections. For more information on specifying maintenance windows, see [Maintenance](/edb-postgres-ai/cloud-service/getting_started/creating_cluster/creating_a_cluster/#maintenance). ## Maintenance for high-availability clusters diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/references/supported_cluster_types/distributed_highavailability.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/references/supported_cluster_types/distributed_highavailability.mdx index ca11619eb9f..2eb8fdf3849 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/references/supported_cluster_types/distributed_highavailability.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/references/supported_cluster_types/distributed_highavailability.mdx @@ -63,6 +63,8 @@ Cross-cloud service provider witness nodes are available with AWS, Azure, and Go ## Read-only workloads + + When you enable the read-only workloads option during the cluster creation, a read-only connection string is created for the data group. You can use this connection to allow your application or service to route read-only requests through the shadow nodes (non-write leaders) to lighten the load on the write leaders and improve the distributed high-availability cluster's performance. If you have more than one data group, you can choose whether to enable the read-only workloads option on a per-data-group basis. diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/references/supported_database_versions.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/references/supported_database_versions.mdx index 024d731cc0d..dfd434e61ea 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/references/supported_database_versions.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/references/supported_database_versions.mdx @@ -20,6 +20,8 @@ We support the major Postgres versions from the date they're made available unti ## End-of-life policy + + Cloud Service deprecates support for Postgres versions following the same timeline as PostgreSQL. PostgreSQL, EDB Postgres Advanced Server, and EDB Postgres Extended Server follow the same timelines. We recommend that you take action and upgrade your Postgres databases running on the deprecated version to a later version as soon as possible. Six months before the PostgreSQL deprecation date, Cloud Service doesn't allow you to create new instances with the deprecated database version. @@ -30,6 +32,8 @@ The only exception is customers who purchased Extended Life Support (ELS) prior ## Key dates + + While PostgreSQL officially deprecated version 11 on November 9, 2023, Cloud Service deprecated PostgreSQL 11 on November 20, 2023 in alignment with the broader EDB portfolio. On November 20, 2023, Cloud Service deprecated support for PostgreSQL 11 and EDB Postgres Advanced Server 11 using the following schedule. We recommend that you take action and upgrade your Postgres databases running on major version 11 to a later version, such as PostgreSQL version 15. diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/connect_from_a_client/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/connect_from_a_client/index.mdx index 88b746a5356..f334108bfc7 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/connect_from_a_client/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/connect_from_a_client/index.mdx @@ -8,6 +8,7 @@ navigation: - connect_using_dbeaver - connecting_from_a_client redirects: + - /purl/upm/ssl-production-recommendation/ - /biganimal/latest/free_trial/detail/connect_to_a_cluster/ #generated for BigAnimal URL path removal branch - /biganimal/latest/using_cluster/02_connecting_your_cluster/connecting_from_a_client/ --- @@ -28,6 +29,8 @@ You can connect to your cluster using the client of your choice including: ## Recommended settings for SSL mode + + Different clients can have different default TLS/SSL modes (sslmode). For example, `psql` defaults to `prefer`, which means the client attempts to establish a TLS connection but falls back to non-TLS if the server doesn't support it. In the `psql` example provided by EDB in the **Quick Connect** field, `sslmode` is explicitly set to `require`, which means the client attempts a TLS connection and fails if the connection to the server can't be encrypted. For public connections and in most environments, EDB recommends setting `sslmode` to `verify-full`. This setting ensures that you connect to the server you specified and that the connection is encrypted. diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/connecting_your_cluster/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/connecting_your_cluster/index.mdx index 9d205515cf0..ffd32b9851f 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/connecting_your_cluster/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/connecting_your_cluster/index.mdx @@ -3,7 +3,6 @@ title: "Connecting to your cluster" description: Connect to your cluster from your applications, client apps, and EDB's tools. redirects: - /purl/upm/connect-to-cluster/ - - /purl/upm/ssl-production-recommendation/ - /biganimal/latest/using_cluster/02_connect_to_cluster/ - connecting_your_cluster - /biganimal/latest/using_cluster/02_connecting_your_cluster/ #generated for BigAnimal URL path removal branch diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/faraway_replicas.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/faraway_replicas.mdx index cab5230eaca..fe281ee18cb 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/faraway_replicas.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/faraway_replicas.mdx @@ -75,6 +75,8 @@ You can create faraway replicas in any active regions in your cloud. There's no ## Modify a replica + + 1. Sign in to the [Console](https://portal.biganimal.com/). 2. Go to the [Clusters](https://portal.biganimal.com/clusters) page. A list of previously created clusters appears. diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/monitoring_and_logging/other_monitoring/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/monitoring_and_logging/other_monitoring/index.mdx index 5a033e635f7..8e5e6c3576e 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/monitoring_and_logging/other_monitoring/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/monitoring_and_logging/other_monitoring/index.mdx @@ -13,6 +13,8 @@ redirects: ## Metrics + + You can access metrics in a [Prometheus format](https://prometheus.io/docs/concepts/data_model/) if you request this feature from Cloud Service Support. You can retrieve the hostname and port for your clusters by using the Prometheus URL available on the **Monitoring and logging** tab on each cluster's detail page in the Console. These [example metrics](example_metrics/) can help you get started. @@ -31,6 +33,8 @@ For more information on some common monitoring services, see: ## Logs + + You can view your logs in your cloud provider's blob storage solution if you request this feature from Cloud Service Support. You can retrieve the location of your object storage on the **Monitoring and logging** tab on your cluster's detail page in the Console. The general pattern for getting logs from blob storage into the cloud provider's solution is to write a custom serverless function that watches the blob storage and uploads to the desired solution. diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/postgres_access/database_authentication.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/postgres_access/database_authentication.mdx index f5034349942..bce8dd86d0f 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/postgres_access/database_authentication.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/postgres_access/database_authentication.mdx @@ -4,6 +4,8 @@ description: Setting up the database authentication for the Postgres clusters. redirects: - /purl/upm/csp-auth-use/ - /purl/upm/iam-auth-postgres/ + - /purl/upm/csp-aws-ad-usermanagement/ + - /purl/upm/csp-azure-ad-usermanagement/ - /biganimal/latest/using_cluster/01_postgres_access/ #generated for BigAnimal URL path removal branch --- @@ -75,6 +77,10 @@ If you use a single database to host multiple schemas, create a database owner a ## IAM authentication for Postgres + + + + Any user with a supported cloud account connected to a BigAnimal subscription who has the Postgres IAM role iam_aws, iam_azure, or iam_gcp can authenticate to the database using their IAM credentials. ### Configuring IAM for Postgres diff --git a/advocacy_docs/edb-postgres-ai/console/using/organizations/identity_provider/index.mdx b/advocacy_docs/edb-postgres-ai/console/using/organizations/identity_provider/index.mdx index 67e996473d1..0c79ecee86a 100644 --- a/advocacy_docs/edb-postgres-ai/console/using/organizations/identity_provider/index.mdx +++ b/advocacy_docs/edb-postgres-ai/console/using/organizations/identity_provider/index.mdx @@ -92,6 +92,8 @@ Step-by-step instructions for setting up specific identity providers are availab ### Add a domain + + You need a verified domain so your users can have a streamlined login experience with their email address. 1. On the **Domains** tab, enter the domain name and select **Next: Verify Domain**. @@ -160,6 +162,8 @@ You add users through your identity provider. A user who you add in the identity ### Add a tile + + Once you establish the identity provider, you can create a EDB Postgres AI tile for users to access the organization's EDB Postgres AI application. To do so, copy the quick sign-in URL from the **Settings > Identity Provider** page of the EDB Postgres AI portal. For details on how to add a tile, refer to your identify provider documentation for instructions on setting up SSO access to your application. ## Next steps diff --git a/advocacy_docs/edb-postgres-ai/console/using/projects/index.mdx b/advocacy_docs/edb-postgres-ai/console/using/projects/index.mdx index 97a58b773aa..8ad75ca0288 100644 --- a/advocacy_docs/edb-postgres-ai/console/using/projects/index.mdx +++ b/advocacy_docs/edb-postgres-ai/console/using/projects/index.mdx @@ -16,7 +16,6 @@ navigation: - settings - migrate redirects: -- /purl/upm/project-manage/ - /biganimal/latest/administering_cluster/projects/ --- diff --git a/advocacy_docs/edb-postgres-ai/console/using/projects/users.mdx b/advocacy_docs/edb-postgres-ai/console/using/projects/users.mdx index 1cc11369198..ac377d83a4b 100644 --- a/advocacy_docs/edb-postgres-ai/console/using/projects/users.mdx +++ b/advocacy_docs/edb-postgres-ai/console/using/projects/users.mdx @@ -3,6 +3,8 @@ title: Managing project users navTitle: Users description: Add users to projects and assign roles to control access to projects deepToC: true +redirects: +- /purl/upm/project-manage/ --- The **Users** page displays all the users in the organisation in a table. Each users full name, email, project roles, identity provider, and on the right hand side, a pen icon. Selecting the pen icon on a user allows you to assign or remove roles from that user. diff --git a/gatsby-node.js b/gatsby-node.js index 2c8337ebd1c..d93cbae8452 100644 --- a/gatsby-node.js +++ b/gatsby-node.js @@ -635,6 +635,26 @@ exports.onPostBuild = async ({ graphql, reporter, pathPrefix }) => { // // additional headers // + await addHeaders(graphql, reporter, pathPrefix); + + // + // redirects cleanup + // + await rewriteRedirects(pathPrefix, reporter); +}; + +/** + * Adds content type headers for raw files + * @param {function} graphql + * @param {GatsbyReporter} reporter + * @param {string} pathPrefix + */ +async function addHeaders(graphql, reporter, pathPrefix) { + const contentHeaderTimer = reporter.activityTimer( + "adding content type headers", + ); + contentHeaderTimer.start(); + const publicFileData = await graphql(` query { allPublicFile { @@ -699,17 +719,38 @@ exports.onPostBuild = async ({ graphql, reporter, pathPrefix }) => { "public/_headers", (await readFile("public/_headers")) + "\n" + newHeaders.join("\n"), ); + contentHeaderTimer.end(); +} + +/** + * Rewrites generated headers: + * - fix up unnecessary path prefix for legacy redirects + * - add hash for perma-URLs + * @param {string} pathPrefix + * @param {GatsbyReporter} reporter + */ +async function rewriteRedirects(pathPrefix, reporter) { + const redirectTimer = reporter.activityTimer("rewriting redirects"); + redirectTimer.start(); - // - // redirects cleanup - // const originalRedirects = await readFile("public/_redirects"); // rewrite legacy redirects to exclude the /docs prefix + // rewrite perma-URL redirects to include hash const prefixRE = new RegExp(`^${pathPrefix}/edb-docs/`); + const purlRE = new RegExp( + `^/docs/purl/(?[^/]+)/(?[^/]+)/?\\s+(?\\S+)\\s+\\d+`, + ); let rewrittenRedirects = originalRedirects .split("\n") .map((line) => line.replace(prefixRE, "/edb-docs/")) + .map((line) => + line.replace( + purlRE, + pathPrefix + + "/purl/$/$/ $#$_$ 302", + ), + ) .join("\n"); if (rewrittenRedirects.length === originalRedirects.length) { @@ -764,17 +805,18 @@ exports.onPostBuild = async ({ graphql, reporter, pathPrefix }) => { # Netlify pathPrefix path rewrite ${pathPrefix}/* /:splat 200`, ); -}; + redirectTimer.end(); +} /** * Strip compilation hashes from generated HTML * this speeds up Netlify deploys, as (otherwise unchanged) files don't change every build * there probably should be a faster / more elegant way to do this, possibly by overriding one of the * default webpack configs... But I've had no luck doing so up to now. - * @param {*} reporter Gatsby reporter + * @param {GatsbyReporter} reporter Gatsby reporter */ async function removeCompilationHashes(reporter) { - const hashTimer = reporter.createProgress("Removing compilation hashes"); + const hashTimer = reporter.createProgress("removing compilation hashes"); hashTimer.start(); const { globby } = await import("globby"); diff --git a/product_docs/docs/epas/12/epas_rel_notes/epas12_21_26_rel_notes.mdx b/product_docs/docs/epas/12/epas_rel_notes/epas12_21_26_rel_notes.mdx deleted file mode 100644 index c5dbe4a4f3d..00000000000 --- a/product_docs/docs/epas/12/epas_rel_notes/epas12_21_26_rel_notes.mdx +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: EDB Postgres Advanced Server 12.21.26 release notes -navTitle: "Version 12.21.26" ---- - -Released: 14 Nov 2024 - -EDB Postgres Advanced Server 12.21.26 includes the following enhancements and bug fixes: - -| Type | Description | Addresses                | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| -| Upstream merge | Merged with community PostgreSQL 12.21. See the [PostgreSQL 12.21 Release Notes](https://www.postgresql.org/docs/release/12.21/) for more information. | | -| Bug fix | Fixed an issue for Auditing. With `edb_audit`, now you can audit the initial connection process or authentication messages as well. | #39540 | -| Bug fix | Fixed an issue for EDB*Loader. Now the `negative bitmapset member not allowed` error is resolved for partitioned tables. | #39562 | -| Bug fix | Fixed an issue for `Oracle Proc*c`and `ecpg with PROC` . Corrected the macro definition in `sqlda-proc.h` to fix the compilation errors when used. | #40573 | -| Bug fix | Fixed an issue for replication. Now the login of locked account on the physical replica is not allowed. | | diff --git a/product_docs/docs/epas/12/epas_rel_notes/epas12_22_00_rel_notes.mdx b/product_docs/docs/epas/12/epas_rel_notes/epas12_22_00_rel_notes.mdx new file mode 100644 index 00000000000..e1eaf057251 --- /dev/null +++ b/product_docs/docs/epas/12/epas_rel_notes/epas12_22_00_rel_notes.mdx @@ -0,0 +1,16 @@ +--- +title: EDB Postgres Advanced Server 12.22.00 release notes +navTitle: "Version 12.22.00" +--- + +Released: 21 Nov 2024 + +EDB Postgres Advanced Server 12.21.26 includes the following enhancements and bug fixes: + +| Type | Description | Addresses                | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| Upstream merge | Merged with community PostgreSQL 12.22. This release includes a fix for [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/). See the [PostgreSQL 12.22 Release Notes](https://www.postgresql.org/docs/release/12.22/) for more information. | [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/) | +| Bug fix | Fixed an issue for Auditing. With `edb_audit`, now you can audit the initial connection process or authentication messages as well. | #39540 | +| Bug fix | Fixed an issue for EDB*Loader. Now the `negative bitmapset member not allowed` error is resolved for partitioned tables. | #39562 | +| Bug fix | Fixed an issue for `Oracle Proc*c`and `ecpg with PROC` . Corrected the macro definition in `sqlda-proc.h` to fix the compilation errors when used. | #40573 | +| Bug fix | Fixed an issue for replication. Now the login of locked account on the physical replica is not allowed. | | diff --git a/product_docs/docs/epas/12/epas_rel_notes/index.mdx b/product_docs/docs/epas/12/epas_rel_notes/index.mdx index efda9c6bd6c..0b9f44f1d17 100644 --- a/product_docs/docs/epas/12/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/12/epas_rel_notes/index.mdx @@ -2,7 +2,7 @@ navTitle: Release Notes title: "EDB Postgres Advanced Server Release Notes" navigation: -- epas12_21_26_rel_notes +- epas12_22_00_rel_notes - epas12_20_25_rel_notes - epas12_19_24_rel_notes - epas12_18_23_rel_notes @@ -33,7 +33,7 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merges | | ----------------------------------------- | ------------ | -------------------------------------------------------------- | -| [12.21.26](epas12_21_26_rel_notes.mdx) | 14 Nov 2024 | [12.21](https://www.postgresql.org/docs/12/release-12-21.html) | +| [12.22.00](epas12_22_00_rel_notes.mdx) | 21 Nov 2024 | [12.22](https://www.postgresql.org/docs/12/release-12-22.html) | | [12.20.25](epas12_20_25_rel_notes.mdx) | 08 Aug 2024 | [12.20](https://www.postgresql.org/docs/12/release-12-20.html) | | [12.19.24](epas12_19_24_rel_notes.mdx) | 09 May 2024 | [12.19](https://www.postgresql.org/docs/12/release-12-19.html) | | [12.18.23](epas12_18_23_rel_notes.mdx) | 08 Feb 2023 | [12.18](https://www.postgresql.org/docs/12/release-12-18.html) | diff --git a/product_docs/docs/epas/13/epas_rel_notes/epas13_17_23_rel_notes.mdx b/product_docs/docs/epas/13/epas_rel_notes/epas13_17_23_rel_notes.mdx deleted file mode 100644 index 2a52cab874c..00000000000 --- a/product_docs/docs/epas/13/epas_rel_notes/epas13_17_23_rel_notes.mdx +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: EDB Postgres Advanced Server 13.17.23 release notes -navTitle: "Version 13.17.23" ---- - -Released: 14 Nov 2024 - -EDB Postgres Advanced Server 13.17.23 includes the following enhancements and bug fixes: - -| Type | Description | Addresses                | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| -| Upstream merge | Merged with community PostgreSQL 13.17. See the [PostgreSQL 13.17 Release Notes](https://www.postgresql.org/docs/release/13.17/) for more information. | | -| Bug fix | Fixed an issue for Auditing. With `edb_audit`, now you can audit the initial connection process or authentication messages as well. | #39540 | -| Bug fix | Fixed an issue for EDB*Loader. Now the `negative bitmapset member not allowed` error is resolved for partitioned tables. | #39562 | -| Bug fix | Fixed an issue for `Oracle Proc*c`and `ecpg with PROC` . Corrected the macro definition in `sqlda-proc.h` to fix the compilation errors when used. | #40573 | -| Bug fix | Fixed an issue for replication. Now the login of locked account on the physical replica is not allowed. | | diff --git a/product_docs/docs/epas/13/epas_rel_notes/epas13_18_00_rel_notes.mdx b/product_docs/docs/epas/13/epas_rel_notes/epas13_18_00_rel_notes.mdx new file mode 100644 index 00000000000..cb8c9ab8974 --- /dev/null +++ b/product_docs/docs/epas/13/epas_rel_notes/epas13_18_00_rel_notes.mdx @@ -0,0 +1,16 @@ +--- +title: EDB Postgres Advanced Server 13.18.00 release notes +navTitle: "Version 13.18.00" +--- + +Released: 21 Nov 2024 + +EDB Postgres Advanced Server 13.18.00 includes the following enhancements and bug fixes: + +| Type | Description | Addresses                | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| Upstream merge | Merged with community PostgreSQL 13.18. This release includes a fix for [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/). See the [PostgreSQL 13.18 Release Notes](https://www.postgresql.org/docs/release/13.18/) for more information. | [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/) | +| Bug fix | Fixed an issue for Auditing. With `edb_audit`, now you can audit the initial connection process or authentication messages as well. | #39540 | +| Bug fix | Fixed an issue for EDB*Loader. Now the `negative bitmapset member not allowed` error is resolved for partitioned tables. | #39562 | +| Bug fix | Fixed an issue for `Oracle Proc*c`and `ecpg with PROC` . Corrected the macro definition in `sqlda-proc.h` to fix the compilation errors when used. | #40573 | +| Bug fix | Fixed an issue for replication. Now the login of locked account on the physical replica is not allowed. | | diff --git a/product_docs/docs/epas/13/epas_rel_notes/index.mdx b/product_docs/docs/epas/13/epas_rel_notes/index.mdx index d8c9ee672d8..9b5cf247a4f 100644 --- a/product_docs/docs/epas/13/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/13/epas_rel_notes/index.mdx @@ -2,7 +2,7 @@ navTitle: Release Notes title: "EDB Postgres Advanced Server Release Notes" navigation: -- epas13_17_23_rel_notes +- epas13_18_00_rel_notes - epas13_16_22_rel_notes - epas13_15_21_rel_notes - epas13_14_20_rel_notes @@ -26,7 +26,7 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merges | |-------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------| -| [13.17.23](epas13_17_23_rel_notes) | 14 Nov 2024 | [13.17](https://www.postgresql.org/docs/release/13.17/) | +| [13.18.00](epas13_18_00_rel_notes) | 21 Nov 2024 | [13.18](https://www.postgresql.org/docs/release/13.18/) | | [13.16.22](epas13_16_22_rel_notes) | 08 Aug 2024 | [13.16](https://www.postgresql.org/docs/release/13.16/) | | [13.15.21](epas13_15_21_rel_notes) | 09 May 2024 | [13.15](https://www.postgresql.org/docs/release/13.15/) | | [13.14.20](epas13_14_20_rel_notes) | 08 Feb 2024 | [13.14](https://www.postgresql.org/docs/release/13.14/) | diff --git a/product_docs/docs/epas/14/epas_rel_notes/epas14_14_0_rel_notes.mdx b/product_docs/docs/epas/14/epas_rel_notes/epas14_14_0_rel_notes.mdx deleted file mode 100644 index 51db778c2cb..00000000000 --- a/product_docs/docs/epas/14/epas_rel_notes/epas14_14_0_rel_notes.mdx +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: EDB Postgres Advanced Server 14.14.0 release notes -navTitle: "Version 14.14.0 " ---- - -Released: 14 Nov 2024 - -EDB Postgres Advanced Server 14.14.0 includes the following enhancements and bug fixes: - -| Type | Description | Addresses                | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| -| Upstream merge | Merged with community PostgreSQL 14.14. See the [PostgreSQL 14.14 Release Notes](https://www.postgresql.org/docs/release/14.14/) for more information. | | -| Bug fix | Fixed an issue for Auditing. With `edb_audit`, now you can audit the initial connection process or authentication messages as well. | #39540 | -| Bug fix | Fixed an issue for EDB*Loader. Now the `negative bitmapset member not allowed` error is resolved for partitioned tables. | #39562 | -| Bug fix | Fixed an issue for `Oracle Proc*c`and `ecpg with PROC` . Corrected the macro definition in `sqlda-proc.h` to fix the compilation errors when used. | #40573 | -| Bug fix | Fixed an issue for replication. Now the login of locked account on the physical replica is not allowed. | | diff --git a/product_docs/docs/epas/14/epas_rel_notes/epas14_15_0_rel_notes.mdx b/product_docs/docs/epas/14/epas_rel_notes/epas14_15_0_rel_notes.mdx new file mode 100644 index 00000000000..0e7a6ce14eb --- /dev/null +++ b/product_docs/docs/epas/14/epas_rel_notes/epas14_15_0_rel_notes.mdx @@ -0,0 +1,16 @@ +--- +title: EDB Postgres Advanced Server 14.15.0 release notes +navTitle: "Version 14.15.0 " +--- + +Released: 21 Nov 2024 + +EDB Postgres Advanced Server 14.15.0 includes the following enhancements and bug fixes: + +| Type | Description | Addresses                | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| Upstream merge | Merged with community PostgreSQL 14.15. This release includes a fix for [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/). See the [PostgreSQL 14.15 Release Notes](https://www.postgresql.org/docs/release/14.15/) for more information. | [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/) | +| Bug fix | Fixed an issue for Auditing. With `edb_audit`, now you can audit the initial connection process or authentication messages as well. | #39540 | +| Bug fix | Fixed an issue for EDB*Loader. Now the `negative bitmapset member not allowed` error is resolved for partitioned tables. | #39562 | +| Bug fix | Fixed an issue for `Oracle Proc*c`and `ecpg with PROC` . Corrected the macro definition in `sqlda-proc.h` to fix the compilation errors when used. | #40573 | +| Bug fix | Fixed an issue for replication. Now the login of locked account on the physical replica is not allowed. | | diff --git a/product_docs/docs/epas/14/epas_rel_notes/index.mdx b/product_docs/docs/epas/14/epas_rel_notes/index.mdx index 53d060f5ed7..4fa6b9b6922 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/index.mdx @@ -2,7 +2,7 @@ navTitle: Release notes title: "EDB Postgres Advanced Server release notes" navigation: -- epas14_14_0_rel_notes +- epas14_15_0_rel_notes - epas14_13_1_rel_notes - epas14_13_0_rel_notes - epas14_12_0_rel_notes @@ -26,7 +26,7 @@ The EDB Postgres Advanced Server (EDB Postgres Advanced Server) documentation de | Version | Release date | Upstream merges | |-----------------------------------|--------------|--------------------------------------------------------------------------------------------------------------------------| -| [14.14.0](epas14_14_0_rel_notes) | 14 Nov 2024 | [14.14](https://www.postgresql.org/docs/14/release-14-14.html/) | +| [14.15.0](epas14_15_0_rel_notes) | 21 Nov 2024 | [14.15](https://www.postgresql.org/docs/14/release-14-15.html/) | | [14.13.1](epas14_13_1_rel_notes) | 16 Aug 2024 | | | [14.13.0](epas14_13_0_rel_notes) | 08 Aug 2024 | [14.13](https://www.postgresql.org/docs/14/release-14-13.html) | | [14.12.0](epas14_12_0_rel_notes) | 09 May 2024 | [14.12](https://www.postgresql.org/docs/14/release-14-12.html) | diff --git a/product_docs/docs/epas/15/epas_rel_notes/epas15_10_0_rel_notes.mdx b/product_docs/docs/epas/15/epas_rel_notes/epas15_10_0_rel_notes.mdx new file mode 100644 index 00000000000..299ba80aac6 --- /dev/null +++ b/product_docs/docs/epas/15/epas_rel_notes/epas15_10_0_rel_notes.mdx @@ -0,0 +1,18 @@ +--- +title: EDB Postgres Advanced Server 15.10.0 release notes +navTitle: "Version 15.10.0 " +--- + +Released: 21 Nov 2024 + +EDB Postgres Advanced Server 15.10.0 includes the following enhancements and bug fixes: + +| Type | Description | Addresses | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| Upstream merge | Merged with community PostgreSQL 15.10. This release includes a fix for [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/). See the [PostgreSQL 15.10 Release Notes](https://www.postgresql.org/docs/release/15.10/) for more information. | [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/) | +| Bug fix | Fixed an issue for Auditing. With `edb_audit`, now you can audit the initial connection process or authentication messages as well. | #39540 | +| Bug fix | Fixed an issue for `EDB*Loader`. Now the `negative bitmapset member not allowed` error is resolved for partitioned tables. | #39562 | +| Bug fix | Fixed an issue for `Oracle Proc*c`and `ecpg with PROC` . Corrected the macro definition in `sqlda-proc.h` to fix the compilation errors when used. | #40573 | +| Bug fix | Fixed an issue for replication. Now the login of locked account on the physical replica is not allowed. | | +| Bug fix | Fixed an issue for `COPY` and `EDB*Loader`. Now the server is not crashed while using dynamic partitioning in `COPY` and `EDB*Loader`. | #38963 | +| Bug fix | Fixed an issue with tab completion for the object names while using in SQL statements. | | diff --git a/product_docs/docs/epas/15/epas_rel_notes/epas15_9_0_rel_notes.mdx b/product_docs/docs/epas/15/epas_rel_notes/epas15_9_0_rel_notes.mdx deleted file mode 100644 index d0648a1e04d..00000000000 --- a/product_docs/docs/epas/15/epas_rel_notes/epas15_9_0_rel_notes.mdx +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: EDB Postgres Advanced Server 15.9.0 release notes -navTitle: "Version 15.9.0 " ---- - -Released: 14 Nov 2024 - -EDB Postgres Advanced Server 15.9.0 includes the following enhancements and bug fixes: - -| Type | Description | Addresses                | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| -| Upstream merge | Merged with community PostgreSQL 15.9. See the [PostgreSQL 15.9 Release Notes](https://www.postgresql.org/docs/release/15.9/) for more information. | | -| Bug fix | Fixed an issue for Auditing. With `edb_audit`, now you can audit the initial connection process or authentication messages as well. | #39540 | -| Bug fix | Fixed an issue for `EDB*Loader`. Now the `negative bitmapset member not allowed` error is resolved for partitioned tables. | #39562 | -| Bug fix | Fixed an issue for `Oracle Proc*c`and `ecpg with PROC` . Corrected the macro definition in `sqlda-proc.h` to fix the compilation errors when used. | #40573 | -| Bug fix | Fixed an issue for replication. Now the login of locked account on the physical replica is not allowed. | | -| Bug fix | Fixed an issue for `COPY` and `EDB*Loader`. Now the server is not crashed while using dynamic partitioning in `COPY` and `EDB*Loader`. | #38963 | -| Bug fix | Fixed an issue with tab completion for the object names while using in SQL statements. | | diff --git a/product_docs/docs/epas/15/epas_rel_notes/index.mdx b/product_docs/docs/epas/15/epas_rel_notes/index.mdx index 330b09bf3e7..3c937115559 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/index.mdx @@ -2,7 +2,7 @@ navTitle: Release notes title: "EDB Postgres Advanced Server release notes" navigation: -- epas15_9_0_rel_notes +- epas15_10_0_rel_notes - epas15_8_1_rel_notes - epas15_8_0_rel_notes - epas15_7_0_rel_notes @@ -20,7 +20,7 @@ The EDB Postgres Advanced Server documentation describes the latest version of E | Version | Release date | Upstream merges | |--------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [15.9.0](epas15_9_0_rel_notes) | 14 Nov 2024 | [15.9](https://www.postgresql.org/docs/release/15.9/) | +| [15.10.0](epas15_10_0_rel_notes) | 14 Nov 2024 | [15.10](https://www.postgresql.org/docs/release/15.10/) | | [15.8.1](epas15_8_1_rel_notes) | 16 Aug 2024 | | | [15.8.0](epas15_8_0_rel_notes) | 08 Aug 2024 | [15.8](https://www.postgresql.org/docs/release/15.8/) | | [15.7.0](epas15_7_0_rel_notes) | 09 May 2024 | [15.7](https://www.postgresql.org/docs/release/15.7/) | diff --git a/product_docs/docs/epas/16/epas_rel_notes/epas16_5_0_rel_notes.mdx b/product_docs/docs/epas/16/epas_rel_notes/epas16_5_0_rel_notes.mdx deleted file mode 100644 index 6d75f920565..00000000000 --- a/product_docs/docs/epas/16/epas_rel_notes/epas16_5_0_rel_notes.mdx +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: EDB Postgres Advanced Server 16.5.0 release notes -navTitle: "Version 16.5.0 " ---- - -Released: 14 Nov 2024 - -EDB Postgres Advanced Server 16.5.0 includes the following enhancements and bug fixes: - -| Type | Description | Addresses                | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| -| Upstream merge | Merged with community PostgreSQL 16.5. See the [PostgreSQL 16.5 Release Notes](https://www.postgresql.org/docs/release/16.5/) for more information. | | -| Bug fix | Fixed an issue for Auditing. With `edb_audit`, now you can audit the initial connection process or authentication messages as well. | #39540 | -| Bug fix | Fixed an issue for `EDB*Loader`. Now the `negative bitmapset member not allowed` error is resolved for partitioned tables. | #39562 | -| Bug fix | Fixed an issue for `Oracle Proc*c`and `ecpg with PROC` . Corrected the macro definition in `sqlda-proc.h` to fix the compilation errors when used. | #40573 | -| Bug fix | Fixed an issue for replication. Now the login of locked account on the physical replica is not allowed. | | -| Bug fix | Fixed an issue for `COPY` and `EDB*Loader`. Now the server is not crashed while using dynamic partitioning in `COPY` and `EDB*Loader`. | #38963 | -| Bug fix | Fixed an issue with tab completion for the object names while using in SQL statements. | | -| Bug fix | Fixed an issue with `ecpg`. Now it supports `EXEC SQL INCLUDE` in Pro*C (`-C PROC`) mode. | #41438 | \ No newline at end of file diff --git a/product_docs/docs/epas/16/epas_rel_notes/epas16_6_0_rel_notes.mdx b/product_docs/docs/epas/16/epas_rel_notes/epas16_6_0_rel_notes.mdx new file mode 100644 index 00000000000..150677ac410 --- /dev/null +++ b/product_docs/docs/epas/16/epas_rel_notes/epas16_6_0_rel_notes.mdx @@ -0,0 +1,19 @@ +--- +title: EDB Postgres Advanced Server 16.6.0 release notes +navTitle: "Version 16.6.0 " +--- + +Released: 21 Nov 2024 + +EDB Postgres Advanced Server 16.6.0 includes the following enhancements and bug fixes: + +| Type | Description | Addresses                | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| Upstream merge | Merged with community PostgreSQL 16.6. This release includes a fix for [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/). See the [PostgreSQL 16.6 Release Notes](https://www.postgresql.org/docs/release/16.6/) for more information. | [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/) | +| Bug fix | Fixed an issue for Auditing. With `edb_audit`, now you can audit the initial connection process or authentication messages as well. | #39540 | +| Bug fix | Fixed an issue for `EDB*Loader`. Now the `negative bitmapset member not allowed` error is resolved for partitioned tables. | #39562 | +| Bug fix | Fixed an issue for `Oracle Proc*c`and `ecpg with PROC` . Corrected the macro definition in `sqlda-proc.h` to fix the compilation errors when used. | #40573 | +| Bug fix | Fixed an issue for replication. Now the login of locked account on the physical replica is not allowed. | | +| Bug fix | Fixed an issue for `COPY` and `EDB*Loader`. Now the server is not crashed while using dynamic partitioning in `COPY` and `EDB*Loader`. | #38963 | +| Bug fix | Fixed an issue with tab completion for the object names while using in SQL statements. | | +| Bug fix | Fixed an issue with `ecpg`. Now it supports `EXEC SQL INCLUDE` in Pro*C (`-C PROC`) mode. | #41438 | \ No newline at end of file diff --git a/product_docs/docs/epas/16/epas_rel_notes/index.mdx b/product_docs/docs/epas/16/epas_rel_notes/index.mdx index 3cad55edaad..32afb7c9134 100644 --- a/product_docs/docs/epas/16/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/16/epas_rel_notes/index.mdx @@ -2,7 +2,7 @@ navTitle: Release notes title: "EDB Postgres Advanced Server release notes" navigation: -- epas16_5_0_rel_notes +- epas16_6_0_rel_notes - epas16_4_1_rel_notes - epas16_4_0_rel_notes - epas16_3_0_rel_notes @@ -17,7 +17,7 @@ The EDB Postgres Advanced Server documentation describes the latest version of E | Version | Release date | Upstream merges | |--------------------------------|--------------|------------------------------------------------------------------------------------------------------------------| -| [16.5.0](epas16_5_0_rel_notes) | 14 Nov 2024 | [16.5](https://www.postgresql.org/docs/16/release-16-5.html) | +| [16.6.0](epas16_6_0_rel_notes) | 21 Nov 2024 | [16.6](https://www.postgresql.org/docs/16/release-16-6.html) | | [16.4.1](epas16_4_1_rel_notes) | 16 Aug 2024 | | | [16.4.0](epas16_4_0_rel_notes) | 08 Aug 2024 | [16.4](https://www.postgresql.org/docs/16/release-16-4.html) | | [16.3.0](epas16_3_0_rel_notes) | 09 May 2024 | [16.3](https://www.postgresql.org/docs/16/release-16-3.html) | diff --git a/product_docs/docs/livecompare/3/oracle_support.mdx b/product_docs/docs/livecompare/3/oracle_support.mdx index ecaab121097..3d2873e13ea 100644 --- a/product_docs/docs/livecompare/3/oracle_support.mdx +++ b/product_docs/docs/livecompare/3/oracle_support.mdx @@ -17,6 +17,14 @@ For example, you can define `technology = oracle` in a data connection. You can All other data connections must be PostgreSQL. +The `user` you use to connect to Oracle must have the necessary privileges to read the data from the tables you want to compare. Specifically, `CONNECT`, `SELECT ANY TABLE` and `SELECT_CATALOG_ROLE`. These can be granted with the command: + +```sql +GRANT CONNECT, SELECT ANY TABLE, SELECT_CATALOG_ROLE TO username; +``` + +Where `username` is the user you want to use to connect to Oracle. + Here's a simple example of comparison between an Oracle database and a PostgreSQL database: ```ini diff --git a/product_docs/docs/livecompare/3/rel_notes/3.0.2_rel_notes.mdx b/product_docs/docs/livecompare/3/rel_notes/3.0.2_rel_notes.mdx new file mode 100644 index 00000000000..3d274b86c53 --- /dev/null +++ b/product_docs/docs/livecompare/3/rel_notes/3.0.2_rel_notes.mdx @@ -0,0 +1,15 @@ +--- +title: "LiveCompare 3.0.2 release notes" +navTitle: Version 3.0.2 +--- + +Released: 21 November 2024 + +LiveCompare 3.0.2 includes the following new features, enhancements, bug fixes, and other changes: + + + +| Type | Description | Addresses | +|:--------|:---------------------------------------------------------------------------------|:----------| +| Bug Fix | Fixed an issue which caused the application to crash when using replication sets | | +| Enhancement | Revised documentation to clarify what roles are required for Oracle | | diff --git a/product_docs/docs/livecompare/3/rel_notes/index.mdx b/product_docs/docs/livecompare/3/rel_notes/index.mdx index e3eb37e5eed..c0ff6bc6625 100644 --- a/product_docs/docs/livecompare/3/rel_notes/index.mdx +++ b/product_docs/docs/livecompare/3/rel_notes/index.mdx @@ -2,13 +2,15 @@ title: Release notes originalFilePath: release_notes.md navigation: +- 3.0.2_rel_notes - 3.0.1_rel_notes --- -The LiveCompare documentation describes the latest version of LiveCompare 3 including minor releases and patches. The release notes in this section provide information on what's new in each release. +The LiveCompare documentation describes the latest version of LiveCompare 3 including minor releases and patches. The release notes in this section provide information on what's new in each release. -| Version | Release Date | -|--------------------------|--------------| +| Version | Release Date | +|------------------------------|--------------| +| [3.0.2](3.0.2_rel_notes.mdx) | Nov 21 2024 | | [3.0.1](3.0.1_rel_notes.mdx) | Sep 30 2024 | diff --git a/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx b/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx index 40fa733d998..648f1cea3d4 100644 --- a/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx +++ b/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx @@ -9,8 +9,8 @@ title: "Supported platforms and databases" You can use the following database product versions with Migration Toolkit: -- PostgreSQL versions 12, 13, 14, 15, and 16 -- EDB Postgres Advanced Server versions 12, 13, 14, 15, and 16 +- PostgreSQL versions 13, 14, 15, 16, and 17 +- EDB Postgres Advanced Server versions 13, 14, 15, 16, and 17 - Oracle 11g - Oracle 12c - Oracle 18c diff --git a/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx b/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx index 96dfc139cf2..b1a18ce27e2 100644 --- a/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx +++ b/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx @@ -1,6 +1,6 @@ --- title: "Specifying connection properities" - +DeepToC: true --- @@ -21,20 +21,20 @@ Before executing Migration Toolkit commands, modify the `toolkit.properties` fil - `SRC_DB_URL` specifies how Migration Toolkit connects to the source database. Details on forming the URL for each source database follows. - `SRC_DB_USER` specifies a user name (with sufficient privileges) in the source database. -- `SRC_DB_PASSWORD` specifies the password of the source database user. -- `TARGET_DB_URL` specifies the JDBC URL of the target database. +- `SRC_DB_PASSWORD` specifies the password of the source database user. Provide the password without any surrounding quotes. +- `TARGET_DB_URL` specifies the JDBC URL of the target database. - `TARGET_DB_USER` specifies the name of a privileged target database user. -- `TARGET_DB_PASSWORD` specifies the password of the target database user. +- `TARGET_DB_PASSWORD` specifies the password of the target database user. Provide the password without any surrounding quotes. !!! Note Unless specified in the command line, Migration Toolkit expects the source database to be Oracle and the target database to be EDB Postgres Advanced Server. For any other source or target database, specify the `-sourcedbtype` or `-targetdbtype` options as described in [Migrating from a non-Oracle source database](/migration_toolkit/latest/07_invoking_mtk/#migrating-schemas-from-a-non-oracle-source-database). -For specifying a target database on BigAnimal, see [Defining a BigAnimal URL](#defining-a-biganimal-url). +For specifying a target database on Cloud Service, see [Defining the URL and configuring the required parameters for Cloud Service](#url-and-parameters-for-cloud-service). -## Defining an Advanced Server URL +## URL and parameters for an Advanced Server Migration Toolkit helps with migration from the following platforms to Advanced Server: @@ -70,13 +70,15 @@ An Advanced Server URL contains the following information: - `` — The name of the source or target database. +Ensure these values are set in the `toolkit.properties` file: + - `{TARGET_DB_USER|SRC_DB_USER}` — Specifies a user with privileges to create each type of object migrated. If migrating data into a table, the specified user might also require insert, truncate, and references privileges for each target table. -- `{TARGET_DB_PASSWORD|SRC_DB_PASSWORD}` — Set to the password of the privileged Advanced Server user. +- `{TARGET_DB_PASSWORD|SRC_DB_PASSWORD}` — Set to the password of the privileged Advanced Server user. Provide the password without any surrounding quotes. -## Defining a PostgreSQL URL +## URL and parameters for PostgreSQL Migration Toolkit helps with migration from the following platforms to PostgreSQL: @@ -111,15 +113,17 @@ The URL contains the following information: - `` — The name of the source or target database. +Ensure these values are set in the `toolkit.properties` file: + - `{SRC_DB_USER|TARGET_DB_USER}` — Specify a user with privileges to create each type of object migrated. If migrating data into a table, the specified user might also need insert, truncate, and references privileges for each target table. -- `{SRC_DB_PASSWORD|TARGET_DB_PASSWORD}` — Set to the password of the privileged PostgreSQL user. +- `{SRC_DB_PASSWORD|TARGET_DB_PASSWORD}` — Set to the password of the privileged PostgreSQL user. Provide the password without any surrounding quotes. -## Defining a BigAnimal URL +## URL and parameters for Cloud Service -Migration Toolkit helps with migration from the following platforms to BigAnimal: +Migration Toolkit helps with migration from the following platforms to Cloud Service: - Oracle - Advanced Server @@ -133,7 +137,7 @@ Migration Toolkit reads connection specifications for the source and the target - The name of a privileged user - The password associated with the specified user -When migrating to BigAnimal, `TARGET_DB_URL` takes the form of a JDBC URL. For example: +When migrating to Cloud Service, `TARGET_DB_URL` takes the form of a JDBC URL. For example: ```text jdbc:://[:]/?sslmode= @@ -141,7 +145,7 @@ jdbc:://[:]/?sslmode= !!!Note -Many of the values you need for the target database URL are available from the BigAnimal portal. In BigAnimal, select your cluster and go to the **Connect** tab to find the values. +Many of the values you need for the target database URL are available from the Cloud Service portal. In Cloud Service, select your cluster and go to the **Connect** tab to find the values. !!! The URL contains the following information: @@ -150,19 +154,21 @@ The URL contains the following information: - `postgres_type` — The subprotocol is the Postgres type. Specify `edb` if you're using Advanced Server or `postgresql` if you're using PostgreSQL. -- `` — The host name of your cluster. You can copy it from the **Host** field on the **Connect** tab in the BigAnimal portal. +- `` — The host name of your cluster. You can copy it from the **Host** field on the **Connect** tab in the Cloud Service portal. -- `` — The port number that the database listener is monitoring. You can copy it from the **Port** field on the **Connect** tab in the BigAnimal portal. +- `` — The port number that the database listener is monitoring. You can copy it from the **Port** field on the **Connect** tab in the Cloud Service portal. -- `` — The name of the target database. Set this to the name of the database in your cluster that you want to use as your migration target database. The name of the default database for your cluster is shown in the **Dbname** field on the **Connect** tab in the BigAnimal portal. Often a separate database is created for use as the migration target. +- `` — The name of the target database. Set this to the name of the database in your cluster that you want to use as your migration target database. The name of the default database for your cluster is shown in the **Dbname** field on the **Connect** tab in the Cloud Service portal. Often a separate database is created for use as the migration target. -- `TARGET_DB_USER` — Specifies the name of a privileged database user. You can copy it from the **User** field on the **Connect** tab in the BigAnimal portal. +- `sslmode` — Either "require" or "verify-full". See [Recommended settings for SSL mode](/edb-postgres-ai/cloud-service/using_cluster/connect_from_a_client/#recommended-settings-for-ssl-mode). Listed at the end of the **Service URI** value on the **Connect** tab in the Cloud Service portal. -- `TARGET_DB_PASSWORD` — Contains the password of the specified user. +Ensure these values are set in the `toolkit.properties` file: -- `sslmode` — Either "require" or "verify-full". See [Recommended settings for SSL mode](/edb-postgres-ai/cloud-service/using_cluster/connect_from_a_client/#recommended-settings-for-ssl-mode). Listed at the end of the **Service URI** value on the **Connect** tab in the BigAnimal portal. +- `TARGET_DB_USER` — Specifies the name of a privileged database user. You can copy it from the **User** field on the **Connect** tab in the Cloud Service portal. -## Defining an Oracle URL +- `TARGET_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. + +## URL and parameters for Oracle Migration Toolkit helps with migration from an Oracle database to a PostgreSQL or Advanced Server database. When migrating from Oracle, you must specify connection specifications for the Oracle source database in the `toolkit.properties` file. The connection information must include: @@ -198,6 +204,8 @@ An Oracle URL contains the following information: - `` — The name of the Oracle service. +Ensure these values are set in the `toolkit.properties` file: + - `SRC_DB_USER` — Specifies the name of a privileged Oracle user. The Oracle user needs read access to the source database objects you want to migrate. If you want to migrate users/roles and related profiles/privileges, grant the Oracle user SELECT privileges on the following Oracle catalog objects: - `DBA_ROLES` @@ -209,11 +217,11 @@ An Oracle URL contains the following information: - `DBA_SYS_PRIVS` -- `SRC_DB_PASSWORD` — Contains the password of the specified user. +- `SRC_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. -## Defining a SQL Server URL +## URL and parameters for an SQL Server Migration Toolkit helps with migration from an SQL Server database to a PostgreSQL or Advanced Server database. Migration Toolkit supports migration of the following object definitions: @@ -251,9 +259,11 @@ A SQL server URL contains the following information: - `` — The name of the source database. +Ensure these values are set in the `toolkit.properties` file: + - `SRC_DB_USER` — Specifies the name of a privileged SQL Server user. -- `SRC_DB_PASSWORD` — Contains the password of the specified user. +- `SRC_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. ### JTDS URL @@ -279,11 +289,13 @@ A SQL server URL contains the following information: - `` — The name of the source database. +Ensure these values are set in the `toolkit.properties` file: + - `SRC_DB_USER` — Specifies the name of a privileged SQL Server user. -- `SRC_DB_PASSWORD` — Contains the password of the specified user. +- `SRC_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. -## Defining a MySQL URL +## URL and parameters for MySQL Migration Toolkit helps with migration from a MySQL database to an Advanced Server or PostgreSQL database. When migrating from MySQL, you must specify connection specifications for the MySQL source database in the `toolkit.properties` file. The connection information must include: @@ -309,9 +321,11 @@ The URL contains the following information: - `` — The name of the source database. +Ensure these values are set in the `toolkit.properties` file: + - `SRC_DB_USER` — Specifies the name of a privileged MySQL user. -- `SRC_DB_PASSWORD` — Contains the password of the specified user. +- `SRC_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. !!! Note @@ -333,7 +347,7 @@ In this case, the JDBC driver reports `TINYINT(1)` as `TINYINT` and is mapped to -## Defining a Sybase URL +## URL and parameters for Sybase Migration Toolkit helps with migration from a Sybase database to an Advanced Server database. When migrating from Sybase, you must specify connection specifications for the Sybase source database in the `toolkit.properties` file. The connection information must include: @@ -365,6 +379,8 @@ A Sybase URL contains the following information: - `` — The name of the source database. +Ensure these values are set in the `toolkit.properties` file: + - `SRC_DB_USER` — Specifies the name of a privileged Sybase user. -- `SRC_DB_PASSWORD` — Contains the password of the specified user. +- `SRC_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. \ No newline at end of file diff --git a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx index 22d8eea9795..b1e1ae155be 100644 --- a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx +++ b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx @@ -23,7 +23,7 @@ The command options that work with Migration Toolkit are grouped by their behavi | [Import options](#import-options) | -sourcedbtype, -targetdbtype, -schemaOnly, -dataOnly | | [Schema creation options](#schema-creation-options) | -dropSchema, -targetSchema | | [Schema object selection options](#schema-object-selection-options) | -allTables, -tables, -excludeTables,

-constraints, -ignoreCheckConstFilter,

-skipCKConst, -skipFKConst,

-skipColDefaultClause,

-indexes, -triggers,

-allViews, -views, -excludeViews,

-allSequences, -sequences, -excludeSequences,

-allProcs, -procs, -excludeProcs,

-allFuncs, -funcs, -excludeFuncs,

-checkFunctionBodies,

-allPackages, -packages, -excludePackages,

-allDomains,

-allQueues, -queues, -excludeQueues

-allRules,

-allgroups, -groups | -| [Migration options](#migration-options) | -truncLoad, -enableConstBeforeDataLoad,

-retryCount, -safeMode, -fastCopy,

-analyze, vacuumAnalyze, -replaceNullChar,

-copyDelimiter, -batchSize,

-cpBatchSize, -lobBatchSize,

-fetchSize, -filterProp

-customColTypeMapping, -customColTypeMappingFile | +| [Migration options](#migration-options) | -truncLoad, -enableConstBeforeDataLoad,

-retryCount, -safeMode, -fastCopy,

-analyze, vacuumAnalyze, -replaceNullChar,

-copyDelimiter, -batchSize,

-cpBatchSize, -lobBatchSize,

-fetchSize, -filterProp

-customColTypeMapping, -customColTypeMappingFile

-mapVirtualToRegular | | [Connection retry options](#connection-retry-options) | -connRetryCount, -connRetryInterval, -abortOnConnFailure | | [Oracle-specific options](#oracle-specific-options) | -allUsers, -users,

-allProfiles, -profiles,

-importPartitionAsTable,

-objectTypes,

-copyViaDBLinkOra, -allDBLinks

-allSynonyms, -allPublicSynonyms, -excludeSynonyms,

-allPrivateSynonyms, -useOraCase,

-skipUserSchemaCreation | | [Miscellaneous options](#miscellaneous-options) | -help, -logDir, -logFileCount, -logFileSize, -logBadSQL -verbose, -version | @@ -450,13 +450,13 @@ The right side specifies a condition that must be true for each row migrated. For example, this code migrates only those countries with a `COUNTRY_ID` value that isn't equal to `AR`: -### `COUNTRIES=COUNTRY_ID<>'AR'` +`COUNTRIES=COUNTRY_ID<>'AR'` This constraint applies to the COUNTRIES table. You can also specify conditions for multiple tables. However, the condition for each table must be on a new line in the property file. -### Example +Example: The following entries in the properties file migrate only the relevant data from EMPLOYEES and the DEPARTMENTS tables: @@ -464,7 +464,7 @@ The following entries in the properties file migrate only the relevant data from `DEPARTMENTS=(DEPARTMENT_ID BETWEEN 10 AND 30)` -`-customColTypeMapping ` +### `-customColTypeMapping ` Use custom type mapping to change the data type of migrated columns. The left side of each pair specifies the columns with a regular expression. The right side of each pair names the data type for that column to assume. You can include multiple pairs in a semi-colon-separated list for ``. For example, to map any column whose name ends in `ID` to type `INTEGER`, use the following custom mapping entry: @@ -482,12 +482,30 @@ On Windows, use `'\.'` to represent the `'.'` character: Alternatively, you can include multiple custom type mappings in a ``: -`-customColTypeMappingFile ` +### `-customColTypeMappingFile ` Specify each entry in the file on a separate line in a key=value pair. The left side of each pair selects the columns with a regular expression. The right side of each pair names the data type for that column to assume. When used in the ``, the `'\\'` characters act as an escape string in any operating system. +### `-mapVirtualToRegular` + +Include the `-mapVirtualToRegular` option to migrate virtual, computed or generated columns in the source database to regular columns in the target database. + +Turning virtual columns to regular columns is helpful when the expression used to compute the values in the source database column is not supported in the target database or cannot be translated into an expression supported by the target database. With this option, you can still migrate the column's values to the target, but the values will no longer be computed dynamically, as they are stored in a regular column. + +For schema migrations, including the option results in all virtual columns in the source database being migrated to regular columns in the target database. + +For data migrations, including the option extracts the computed values from all computed columns in the source database and inserts those values into regular columns in the target database. + +For example, in: + +``` +./runMTK.sh -sourcedbtype sqlserver -targetdbtype enterprisedb -mapVirtualToRegular -allTables +``` + +A column called `FullName` that is computed from other two columns called `FirstName` and `LastName` in the source database, is migrated as a regular column called `FullName` in the target database. In the target, this column is no longer dynamically generated, but displays the `FullName` value the source database had at the time the migration was performed. + ## Connection retry options Whenever there's a connection failure with the target database during a data migration, Migration Tookit attempts to reconnect to the diff --git a/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx b/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx index 29cd9cb5629..8a93686a46b 100644 --- a/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx +++ b/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx @@ -117,7 +117,7 @@ Check the connectivity credentials. The JDBC URL for the target database (EDB Postgres Advanced Server) specified in the `toolkit.properties` file contains invalid connection properties. -To resolve this error, edit the `toolkit.properties` file, specifying valid connection information for the target database in the `TARGET_DB_URL` property. For information about forming a JDBC URL for EDB Postgres Advanced Server, see [Defining an EDB Postgres Advanced Server URL](06_building_toolkit.properties_file/#defining-an-advanced-server-url). +To resolve this error, edit the `toolkit.properties` file, specifying valid connection information for the target database in the `TARGET_DB_URL` property. For information about forming a JDBC URL for EDB Postgres Advanced Server, see [Defining an EDB Postgres Advanced Server URL](06_building_toolkit.properties_file/#url-and-parameters-for-an-advanced-server). diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx index 1104b39f04c..5c131116b32 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx @@ -3,6 +3,7 @@ title: "Release notes" redirects: - ../01_whats_new/ navigation: + - mtk_55100_rel_notes - mtk_5590_rel_notes - mtk_5580_rel_notes - mtk_5570_rel_notes @@ -23,6 +24,7 @@ The Migration Toolkit documentation describes the latest version of Migration To | Version | Release Date | |---------------------------------|--------------| +| [55.10.0](mtk_55100_rel_notes) | 21 Nov 2024 | | [55.9.0](mtk_5590_rel_notes) | 21 Aug 2024 | | [55.8.0](mtk_5580_rel_notes) | 16 May 2024 | | [55.7.0](mtk_5570_rel_notes) | 13 Dec 2023 | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_55100_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_55100_rel_notes.mdx new file mode 100644 index 00000000000..8cd5a8bf42b --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_55100_rel_notes.mdx @@ -0,0 +1,17 @@ +--- +title: "Migration Toolkit 55.10.0 release notes" +navTitle: Version 55.10.0 +--- + +Released: 21 Nov 2024 + +New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.10.0 include: + +| Type | Description | Ticket | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| Enhancement | Migration Toolkit now supports PostgreSQL version 17 and EDB Postgres Advanced Server version 17 both as a source and target database. | | +| Enhancement | Improved the handling and consistency in migrating virtual columns across different source and target database combinations.
You can now choose whether to migrate virtual columns as virtual columns or map them to regular columns in the target. See [mapVirtualToRegular](../07_invoking_mtk/08_mtk_command_options/#-mapvirtualtoregular) for more information. | #38897 | +| Bug fix | Fixed an issue that caused synonyms from all source schemas to be migrated even when only one schema was selected for migration. | #41178 | +| Bug fix | Fixed an issue where the MySQL column type `BIGINT AUTO_INCREMENT` is not mapped to the `BIGSERIAL` column type in the target PostgreSQL/EDB Postgres Advanced Server table. | | +| Bug fix | Fixed the issue where migration fails in parallel mode for a table with a primary key based on the float data type. | | +| Bug fix | Fixed an issue where the indexes are skipped from migration when multiple tables are selected for a source MySQL database. | | diff --git a/product_docs/docs/pgd/5.6/cli/index.mdx b/product_docs/docs/pgd/5.6/cli/index.mdx index f95b828e8b7..e3c7b442bc4 100644 --- a/product_docs/docs/pgd/5.6/cli/index.mdx +++ b/product_docs/docs/pgd/5.6/cli/index.mdx @@ -11,6 +11,8 @@ navigation: description: Installing and using the PGD Command Line Interface (CLI) to manage your PGD cluster. directoryDefaults: description: "The PGD Command Line Interface (CLI) is a tool to manage your EDB Postgres Distributed cluster" +redirects: +- /purl/upm/pgd-cli/ --- The EDB Postgres Distributed Command Line Interface (PGD CLI) is a tool for managing your EDB Postgres Distributed cluster. It's the key tool for inspecting and managing cluster resources. diff --git a/product_docs/docs/pge/13/release_notes/index.mdx b/product_docs/docs/pge/13/release_notes/index.mdx index 67a6e0fbdc2..f92750561f1 100644 --- a/product_docs/docs/pge/13/release_notes/index.mdx +++ b/product_docs/docs/pge/13/release_notes/index.mdx @@ -4,13 +4,13 @@ navTitle: Release notes description: Release notes for EDB Postgres Extended Server 13. --- -## 2ndQuadrant Postgres 13.17 +## 2ndQuadrant Postgres 13.18 -Release date: 2024-11-14 +Release date: 2024-11-21 This release is primarily an upstream merge. -Merged with community PostgreSQL 13.17. See the [PostgreSQL 13.17 Release Notes](https://www.postgresql.org/docs/13/release-13-17.html) for more information. +Merged with community PostgreSQL 13.18. See the [PostgreSQL 13.18 Release Notes](https://www.postgresql.org/docs/13/release-13-18.html) for more information. ## 2ndQuadrant Postgres 13.16.1r1.1.19 diff --git a/product_docs/docs/pge/14/release_notes/index.mdx b/product_docs/docs/pge/14/release_notes/index.mdx index 8fb3d7b03e0..b571d80f2e3 100644 --- a/product_docs/docs/pge/14/release_notes/index.mdx +++ b/product_docs/docs/pge/14/release_notes/index.mdx @@ -4,13 +4,13 @@ navTitle: Release notes description: Release notes for EDB Postgres Extended Server 14. --- -## EDB Postgres Extended Server 14.14 +## EDB Postgres Extended Server 14.15 -Release date: 2024-11-14 +Release date: 2024-11-21 This release is primarily an upstream merge. -Merged with community PostgreSQL 14.14. See the [PostgreSQL 14.14 Release Notes](https://www.postgresql.org/docs/14/release-14-14.html) for more information. +Merged with community PostgreSQL 14.15. See the [PostgreSQL 14.15 Release Notes](https://www.postgresql.org/docs/14/release-14-15.html) for more information. ## EDB Postgres Extended Server 14.13.1 diff --git a/product_docs/docs/pge/15/release_notes/index.mdx b/product_docs/docs/pge/15/release_notes/index.mdx index cb0b87d637a..581c0ba8e02 100644 --- a/product_docs/docs/pge/15/release_notes/index.mdx +++ b/product_docs/docs/pge/15/release_notes/index.mdx @@ -1,7 +1,7 @@ --- title: "Release notes" navigation: - - rel_notes15.9 + - rel_notes15.10 - rel_notes15.8.1 - rel_notes15.8 - rel_notes15.7 @@ -17,7 +17,7 @@ release notes cover what was new in each release. | Version | Release date | |---------------------------|--------------| -| [15.9](rel_notes15.9) | 14 Nov 2024 | +| [15.10](rel_notes15.10) | 21 Nov 2024 | | [15.8.1](rel_notes15.8.1) | 22 Aug 2024 | | [15.8](rel_notes15.8) | 08 Aug 2024 | | [15.7](rel_notes15.7) | 09 May 2024 | diff --git a/product_docs/docs/pge/15/release_notes/rel_notes15.10.mdx b/product_docs/docs/pge/15/release_notes/rel_notes15.10.mdx new file mode 100644 index 00000000000..fb3bc8cdbf0 --- /dev/null +++ b/product_docs/docs/pge/15/release_notes/rel_notes15.10.mdx @@ -0,0 +1,12 @@ +--- +title: "EDB Postgres Extended Server 15.10 release notes" +navTitle: Version 15.10 +--- + +Released: 21 Nov 2024 + +New features, enhancements, bug fixes, and other changes in EDB Postgres Extended Server 15.10 include: + +| Type | Description | Ticket | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| Upstream merge | Merged with community PostgreSQL 15.10. This release includes a fix for [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/). See the [PostgreSQL 15.10 Release Notes](https://www.postgresql.org/docs/15/release-15-10.html) for more information. | [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/) | diff --git a/product_docs/docs/pge/15/release_notes/rel_notes15.9.mdx b/product_docs/docs/pge/15/release_notes/rel_notes15.9.mdx deleted file mode 100644 index b5f399f4a20..00000000000 --- a/product_docs/docs/pge/15/release_notes/rel_notes15.9.mdx +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: "EDB Postgres Extended Server 15.9 release notes" -navTitle: Version 15.9 ---- - -Released: 14 Nov 2024 - -New features, enhancements, bug fixes, and other changes in EDB Postgres Extended Server 15.9 include: - -| Type | Description | Ticket | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|---------| -| Upstream merge | Merged with community PostgreSQL 15.9. See the [PostgreSQL 15.9 Release Notes](https://www.postgresql.org/docs/15/release-15-9.html) for more information. | | - - diff --git a/product_docs/docs/pge/16/release_notes/index.mdx b/product_docs/docs/pge/16/release_notes/index.mdx index e8e3985316e..148db547aa4 100644 --- a/product_docs/docs/pge/16/release_notes/index.mdx +++ b/product_docs/docs/pge/16/release_notes/index.mdx @@ -2,7 +2,7 @@ title: "Release notes" description: "Release notes for EDB Postgres Extended Server 16." navigation: - - rel_notes16.5 + - rel_notes16.6 - rel_notes16.4.1 - rel_notes16.4 - rel_notes16.3 @@ -15,7 +15,7 @@ cover what was new in each release. | Version | Release date | |---------------------------|--------------| -| [16.5](rel_notes16.5) | 14 Nov 2024 | +| [16.6](rel_notes16.6) | 21 Nov 2024 | | [16.4.1](rel_notes16.4.1) | 22 Aug 2024 | | [16.4](rel_notes16.4) | 08 Aug 2024 | | [16.3](rel_notes16.3) | 09 May 2024 | diff --git a/product_docs/docs/pge/16/release_notes/rel_notes16.5.mdx b/product_docs/docs/pge/16/release_notes/rel_notes16.5.mdx deleted file mode 100644 index 6128fa911bb..00000000000 --- a/product_docs/docs/pge/16/release_notes/rel_notes16.5.mdx +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: EDB Postgres Extended Server 16.5 release notes -navTitle: "Version 16.5" ---- - -Released: 14 Nov 2024 - -EDB Postgres Extended Server 16.5 includes the following enhancements and bug fixes: - -| Type | Description | Ticket | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|---------| -| Upstream merge | Merged with community PostgreSQL 16.5. See the [PostgreSQL 16.5 Release Notes](https://www.postgresql.org/docs/16/release-16-5.html) for more information. | | - - - diff --git a/product_docs/docs/pge/16/release_notes/rel_notes16.6.mdx b/product_docs/docs/pge/16/release_notes/rel_notes16.6.mdx new file mode 100644 index 00000000000..d63003701d5 --- /dev/null +++ b/product_docs/docs/pge/16/release_notes/rel_notes16.6.mdx @@ -0,0 +1,12 @@ +--- +title: EDB Postgres Extended Server 16.6 release notes +navTitle: "Version 16.6" +--- + +Released: 21 Nov 2024 + +EDB Postgres Extended Server 16.6 includes the following enhancements and bug fixes: + +| Type | Description | Ticket | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| Upstream merge | Merged with community PostgreSQL 16.6. This release includes a fix for [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/). See the [PostgreSQL 16.6 Release Notes](https://www.postgresql.org/docs/16/release-16-6.html) for more information. | [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/) | diff --git a/src/components/index.js b/src/components/index.js index c42a9e30b77..7ff8a74169c 100644 --- a/src/components/index.js +++ b/src/components/index.js @@ -20,6 +20,7 @@ import Logo from "./logo"; import MainContent from "./main-content"; import PdfDownload from "./pdf-download.js"; import PrevNext from "./prev-next"; +import PurlAnchor from "./purl-anchor"; import SearchNavigationLinks from "./search-navigation-links"; import SearchNavigation from "./search-navigation"; import SideNavigation from "./side-navigation"; @@ -55,6 +56,7 @@ export { MainContent, PdfDownload, PrevNext, + PurlAnchor, SearchNavigationLinks, SearchNavigation, SideNavigation, diff --git a/src/components/layout.js b/src/components/layout.js index c39446b5e30..0ec5c1a655f 100644 --- a/src/components/layout.js +++ b/src/components/layout.js @@ -12,6 +12,7 @@ import { Link, StubCards, IconList, + PurlAnchor, } from "../components"; import { MDXProvider } from "@mdx-js/react"; import Icon from "../components/icon/"; @@ -138,6 +139,7 @@ const Layout = ({ IconList, Archive, AuthenticatedContentPlaceholder, + PurlAnchor, }), [katacodaPanelData, meta.path, meta.isIndexPage, meta.productVersions], ); diff --git a/src/components/purl-anchor.js b/src/components/purl-anchor.js new file mode 100644 index 00000000000..bcaa3298ea0 --- /dev/null +++ b/src/components/purl-anchor.js @@ -0,0 +1,68 @@ +import React from "react"; + +// Accepts the id used as the perma-URL path redirect and transforms it into an +// element with an id that will match the fragment generated by the matching +// redirect in static/_redirects. +// For use in documentation that will be linked to in external application UIs. +// Expected format: +// /purl/// +// ...where will be a short, stable name for the product (e.g. "pgd", "upm", "epas"), +// and will be a meaningful description of the expected content being linked to. +// Both parameters must be composed of characters valid in URL fragments; invalid characters will *not* be escaped! +// I recommend you limit these parameters to words containing alphanumeric characters, separated by dashes. +// +// This component is intentionally bare-bones right now; it's a component for only two reasons +// 1. it performs transformation and some limited validation of the id (ensure that it fits with the scheme expected by the matching redirect in static/_redirects) +// 2. it makes the purpose of the anchor more obvious when scanning the source Markdown +// (and hopefully when reorganizing content) +// +// Note that you *must* list the path passed to this function in the frontmatter +// redirects section of the file where it appears; I may automate that or at least +// validate it at some point in the future if this sees enough use to make that useful. +// +const PurlAnchor = ({ urlPath }) => { + if (!urlPath?.replace) { + console.error("PurlAnchor requires a urlPath property"); + return; + } + + let hash = urlPath + .replace(/^\/?purl\/?/, "") + .split("/") + .filter((s) => s) + .join("_"); + + if (!/^\/purl\/[^/]+\/[^/]+/.test(urlPath)) + console.error( + `PurlAnchor given a badly-formatted URL path: ${urlPath}; format must be /purl// - anchor id will be ${hash}`, + ); + + // h/t https://stackoverflow.com/questions/26088849/url-fragment-allowed-characters/26119120#26119120 + if (!/^([-?/:@._~!$&'()*+,;=a-zA-Z0-9]|%[0-9a-fA-F]{2})*$/.test(hash)) + console.error( + `PurlAnchor given a badly-formatted URL path: ${urlPath}; this results in an anchor id of ${hash}, which is invalid as a URL fragment`, + ); + + return ; +}; + +function snapToNearestSection(node) { + if ( + !node || + decodeURIComponent(window?.location?.hash?.substring(1)) !== node.id + ) + return; + + // walk backwards and find nearest previous sibling which is a header with an id, then use *that* id + // this is a "nice to have", as it makes it more likely that both the URL and section + // are those defined by the document structure (sections) vs. arbitrary ids. + for (let next = node.previousSibling; next; next = next.previousSibling) { + const prevId = next.getAttribute && next.getAttribute("id"); + if (prevId && /H\d/.test(next.nodeName)) { + window.history.replaceState(null, null, "#" + encodeURIComponent(prevId)); + break; + } + } +} + +export default PurlAnchor;