diff --git a/gatsby-browser.js b/gatsby-browser.js index 7651e54fe5d..ab2291b9008 100644 --- a/gatsby-browser.js +++ b/gatsby-browser.js @@ -10,6 +10,13 @@ exports.onRouteUpdate = ({ location }) => scrollToAnchor(location); * @param {Number} [mainNavHeight] - the height of any persistent nav -> document.querySelector(`nav`) */ function scrollToAnchor(location, mainNavHeight = 0) { + // left nav: scroll + const navItem = document.querySelector(".sidebar .active"); + if (navItem) navItem.scrollIntoView({ block: "nearest" }); + // right-nav: scroll + const toc = document.querySelector(".toc-sticky .active"); + if (toc) toc.scrollIntoView({ block: "nearest" }); + // Check for location so build does not fail if (location && location.hash) { try { diff --git a/gatsby-config.js b/gatsby-config.js index 171fa44b157..2d3f547c249 100644 --- a/gatsby-config.js +++ b/gatsby-config.js @@ -171,7 +171,6 @@ module.exports = { "gatsby-plugin-sass", "gatsby-plugin-react-helmet", "gatsby-transformer-sharp", - "gatsby-transformer-json", "gatsby-plugin-catch-links", "gatsby-plugin-sharp", { @@ -283,6 +282,7 @@ module.exports = { options: { linkImagesToOriginal: false, showCaptions: false, + maxWidth: 1080, }, }, { diff --git a/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx b/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx index 7a6a52f0eb8..f37a7da2a3e 100644 --- a/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx +++ b/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx @@ -138,7 +138,7 @@ The following is an example of the content of an Replication Server startup conf JAVA_EXECUTABLE_PATH="/usr/bin/java" JAVA_MINIMUM_VERSION=1.8 JAVA_BITNESS_REQUIRED=64 -JAVA_HEAP_SIZE="-Xms256m -Xmx1536m" +JAVA_HEAP_SIZE="-Xms2048m -Xmx4096m" PUBPORT=9051 SUBPORT=9052 ``` diff --git a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/01_setting_heap_size_for_pub_and_sub.mdx b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/01_setting_heap_size_for_pub_and_sub.mdx index e3c26b5123c..c733690351d 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/01_setting_heap_size_for_pub_and_sub.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/01_setting_heap_size_for_pub_and_sub.mdx @@ -16,7 +16,7 @@ The following is an example of the Replication Server startup configuration file JAVA_EXECUTABLE_PATH="/usr/bin/java" JAVA_MINIMUM_VERSION=1.8 JAVA_BITNESS_REQUIRED=64 -JAVA_HEAP_SIZE="-Xms256m -Xmx1536m" +JAVA_HEAP_SIZE="-Xms2048m -Xmx4096m" PUBPORT=9051 SUBPORT=9052 ``` diff --git a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx index b4db079d0cd..4c6575efa70 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx @@ -28,7 +28,7 @@ When you install Replication Server, the port numbers you specify for the public JAVA_EXECUTABLE_PATH="/usr/bin/java" JAVA_MINIMUM_VERSION=1.9 JAVA_BITNESS_REQUIRED=64 -JAVA_HEAP_SIZE="-Xms256m -Xmx1536m" +JAVA_HEAP_SIZE="-Xms2048m -Xmx4096m" PUBPORT=9051 SUBPORT=9052 ``` diff --git a/product_docs/docs/eprs/7/05_smr_operation/04_on_demand_replication/01_perform_replication.mdx b/product_docs/docs/eprs/7/05_smr_operation/04_on_demand_replication/01_perform_replication.mdx index 01b51b9f157..195eddc44eb 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/04_on_demand_replication/01_perform_replication.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/04_on_demand_replication/01_perform_replication.mdx @@ -31,3 +31,6 @@ The status messages of each snapshot are saved in the Migration Toolkit log file `POSTGRES_HOME` is the home directory of the Windows postgres account (enterprisedb account for EDB Postgres Advanced Server installed in Oracle-compatible configuration mode). The specific location of `POSTGRES_HOME` depends on your version of Windows. The Replication Server version number is represented by `x.x`. The publication is now replicated to the subscription database. A record of the snapshot is kept in the replication history. See [Viewing replication history](../../07_common_operations/04_view_replication_history/#view_replication_history) for more information. + +!!! Note + Before version 7.0.0, Replication Server required super user privileges to disable/enable constraints and indexes as part of its snapshot operation. Starting with version 7.0.0, the super user privileges are no longer required and the constraints/indexes are now dropped and re-created as part of the snapshot operation. This change might cause any views/materialized views with a dependency on the constraints from the target subscription/master database to be dropped. These views are then re-created at the end of snapshot operation. Depending on the permissions assigned to the Replication Server subscription database user, the recreated views/materialized views might have permissions that are inconsistent with those of the originally assigned permissions. Therefore, it is recommended to manually verify the assigned permissions of the relevant views/materialized views in the target database and make any corrections where applicable. diff --git a/product_docs/docs/eprs/7/06_mmr_operation/05_on_demand_replication_mmr.mdx b/product_docs/docs/eprs/7/06_mmr_operation/05_on_demand_replication_mmr.mdx index 7b8d88b9cf0..c4e8585172f 100644 --- a/product_docs/docs/eprs/7/06_mmr_operation/05_on_demand_replication_mmr.mdx +++ b/product_docs/docs/eprs/7/06_mmr_operation/05_on_demand_replication_mmr.mdx @@ -41,6 +41,9 @@ The status messages of each snapshot are saved in the Migration Toolkit log file The publication is now replicated from the primary definition node to the selected primary node. A record of the snapshot is saved in the replication history. See [Viewing replication history](../07_common_operations/04_view_replication_history/#view_replication_history) for more information. +!!! Note + Before version 7.0.0, Replication Server required super user privileges to disable/enable constraints and indexes as part of its snapshot operation. Starting with version 7.0.0, the super user privileges are no longer required and the constraints/indexes are now dropped and re-created as part of the snapshot operation. This change might cause any views/materialized views with a dependency on the constraints from the target subscription/master database to be dropped. These views are then re-created at the end of snapshot operation. Depending on the permissions assigned to the Replication Server subscription database user, the recreated views/materialized views might have permissions that are inconsistent with those of the originally assigned permissions. Therefore, it is recommended to manually verify the assigned permissions of the relevant views/materialized views in the target database and make any corrections where applicable. + ## Perform synchronization replication diff --git a/product_docs/docs/eprs/7/07_common_operations/05_managing_history.mdx b/product_docs/docs/eprs/7/07_common_operations/05_managing_history.mdx index 0779d7a435b..6eed3df74dc 100644 --- a/product_docs/docs/eprs/7/07_common_operations/05_managing_history.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/05_managing_history.mdx @@ -90,7 +90,7 @@ Cleaning up shadow table history deletes the rows in the following Replication S **For Postgres only:** When Postgres is the publication database, these tables are located in the publication database in schema `_edb_replicator_pub`. You can schedule shadow table history cleanup to run periodically (see [Scheduling shadow table history cleanup](#schedule_shadow_table_history_cleanup)) or on demand. !!! Note - The cleanup of certain processed rows in the shadow tables might not occur during an on-demand cleanup or might be delayed beyond the next scheduled cleanup. They are eventually removed in later cleanup events. + The cleanup of certain processed rows in the shadow tables might be delayed beyond the next scheduled cleanup. When Oracle or SQL Server are the publication database for clusters created using versions 7.5 and earlier, the cleanup delay can be there due to uncommitted changes. These rows are eventually removed in later cleanup events. For new clusters created using version 7.5.1 and later, the shadow cleanup operation is accurate and the delayed cleanup issue is fixed. To run shadow table history cleanup on demand for a chosen publication: diff --git a/product_docs/docs/eprs/7/08_xdb_cli/01_prereq_steps.mdx b/product_docs/docs/eprs/7/08_xdb_cli/01_prereq_steps.mdx index f106d15df5e..1cb1240af82 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/01_prereq_steps.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/01_prereq_steps.mdx @@ -24,7 +24,7 @@ The Replication Server CLI is included if you choose the Replication Server cons JAVA_EXECUTABLE_PATH="/usr/bin/java" JAVA_MINIMUM_VERSION=1.7 JAVA_BITNESS_REQUIRED=64 - JAVA_HEAP_SIZE="-Xms256m -Xmx1536m" + JAVA_HEAP_SIZE="-Xms2048m -Xmx4096m" PUBPORT=9051 SUBPORT=9052 ``` diff --git a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/04_troubleshooting_areas.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/04_troubleshooting_areas.mdx index 1d7a48da0e3..144479fb2f4 100644 --- a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/04_troubleshooting_areas.mdx +++ b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/04_troubleshooting_areas.mdx @@ -28,7 +28,7 @@ The following is an example of the content of the Replication Server Configurati JAVA_EXECUTABLE_PATH="/usr/bin/java" JAVA_MINIMUM_VERSION=1.8 JAVA_BITNESS_REQUIRED=64 -JAVA_HEAP_SIZE="-Xms256m -Xmx1536m" +JAVA_HEAP_SIZE="-Xms2048m -Xmx4096m" PUBPORT=9051 SUBPORT=9052 ``` diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.1.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.1.mdx new file mode 100644 index 00000000000..ae74dcd4452 --- /dev/null +++ b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.1.mdx @@ -0,0 +1,19 @@ +--- +title: "Version 7.5.1" +--- + + +New features, enhancements, bug fixes, and other changes in Replication Server 7.5.1 include the following: + +| Type | Description | +| ------- |------------ | +| Bug fix | Fixed an Oracle shadow table cleanup issue by adding the ability to set a threshold period via the `TX_MONITOR_PENDING_THRESHOLD_TIME` parameter. [Support ticket: #88095] | +| Bug fix | Fixed an issue that causes the removal of certain manually created views with a constraint dependency from the target subscription database on execution of re-snapshot. [Support ticket: #89491] | +| Bug fix | Fixed an issue in the upgrade routine that causes a `NumberFormatException` error while upgrading from version 6.2.18 to version 7.5.0. [Support ticket: #92056] | +| Bug fix | Fixed an issue that causes an `ArrayInexOutOfBoundsException` error and prevents publication server start-up while upgrading from version 6.2.15 to version 7.5.0. [Support ticket: #91588] | +| Bug fix | Fixed a corner case issue that results in data loss during replication from a SQL Server publication database when the transaction size exceeds the `txSetMaxSize` value. [Support ticket: #92797] | +| Bug fix | Fixed the packaging to add the ability to specify different `JAVA_HEAP` sizes for the Publication and Subscription servers. [Support ticket: #92552] | +| Bug fix | Fixed a Data Validator issue where `NUMERIC(n,0)` data type columns in Postgres were being represented as non-integer values when comparing the data in these columns to the corresponding `INT`, `BIGINT`, `SMALLINT`, or `BIT` data type columns in SQL Server, which are represented as integer values. | +| Bug fix | Fixed an issue that causes replicateDDL to fail when using the mssql-jdbc driver with SQL Server Publication database. | +| Bug fix | Increased the default `JAVA_HEAP` size for the publication server to reduce the possibility of `OutOfMemoryError` errors when default settings are used. | +| Bug fix | Fixed the issue where invalid values could be supplied when specifying a column mapping. A validation of the specified column name is now performed and will throw an error if the value is invalid. | diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx index e874398cce4..36623d6ebb4 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx @@ -3,6 +3,7 @@ title: "Release Notes" redirects: - ../01_whats_new/ navigation: + - eprs_rel_notes_7.5.1 - eprs_rel_notes_7.5.0 - eprs_rel_notes_7.4.0 --- @@ -12,6 +13,7 @@ The Replication Server documentation describes the latest version including mino | Version | Release Date | | -------------------------------- | ------------ | +| [7.5.1](eprs_rel_notes_7.5.1) | 2023 May 26 | | [7.5.0](eprs_rel_notes_7.5.0) | 2023 Feb 14 | | [7.4.0](eprs_rel_notes_7.4.0) | 2022 Nov 29 | | [7.3.0](15_eprs_rel_notes_7.3.0) | 2022 Nov 15 | diff --git a/product_docs/docs/pgd/5/cli/command_ref/index.mdx b/product_docs/docs/pgd/5/cli/command_ref/index.mdx index 37111f4317a..1ef87e61391 100644 --- a/product_docs/docs/pgd/5/cli/command_ref/index.mdx +++ b/product_docs/docs/pgd/5/cli/command_ref/index.mdx @@ -1,6 +1,5 @@ --- title: Command reference -navTitle: "CLI Command reference ▶" redirects: - /pgd/latest/cli/command_ref/pgd_show-camo/ --- diff --git a/product_docs/docs/pgd/5/cli/index.mdx b/product_docs/docs/pgd/5/cli/index.mdx index 43e5f0cfa49..44462edf138 100644 --- a/product_docs/docs/pgd/5/cli/index.mdx +++ b/product_docs/docs/pgd/5/cli/index.mdx @@ -1,6 +1,6 @@ --- title: "EDB Postgres Distributed Command Line Interface" -navTitle: "Command line interface ▶" +navTitle: "Command line interface" indexCards: none navigation: - installing_cli diff --git a/product_docs/docs/pgd/5/consistency/index.mdx b/product_docs/docs/pgd/5/consistency/index.mdx index 451771b6a35..66c4d1547a4 100644 --- a/product_docs/docs/pgd/5/consistency/index.mdx +++ b/product_docs/docs/pgd/5/consistency/index.mdx @@ -1,6 +1,6 @@ --- title: Consistency -navTitle: "Consistency ▶" + navigation: - conflicts - column-level-conflicts diff --git a/product_docs/docs/pgd/5/durability/index.mdx b/product_docs/docs/pgd/5/durability/index.mdx index 697bd0f19ed..5decde315f8 100644 --- a/product_docs/docs/pgd/5/durability/index.mdx +++ b/product_docs/docs/pgd/5/durability/index.mdx @@ -1,6 +1,6 @@ --- title: Durability and performance options -navTitle: "Durability options ▶" + navigation: - commit-scopes - group-commit diff --git a/product_docs/docs/pgd/5/monitoring/index.mdx b/product_docs/docs/pgd/5/monitoring/index.mdx index 5ab5932ddd1..5c21ff26d52 100644 --- a/product_docs/docs/pgd/5/monitoring/index.mdx +++ b/product_docs/docs/pgd/5/monitoring/index.mdx @@ -1,6 +1,5 @@ --- title: Monitoring -navTitle: "Monitoring ▶" originalFilePath: monitoring.md --- diff --git a/product_docs/docs/pgd/5/quickstart/index.mdx b/product_docs/docs/pgd/5/quickstart/index.mdx index 25fd7ed2345..1fea78ef9a1 100644 --- a/product_docs/docs/pgd/5/quickstart/index.mdx +++ b/product_docs/docs/pgd/5/quickstart/index.mdx @@ -1,6 +1,6 @@ --- title: "Introducing PGD quick starts" -navTitle: "Quick start ▶" +navTitle: "Quick start" description: > How to select your PGD quick start deployment and what to expect from the experience. indexCards: none diff --git a/product_docs/docs/pgd/5/rel_notes/index.mdx b/product_docs/docs/pgd/5/rel_notes/index.mdx index aa76df5afd0..0dcd6ba4f4e 100644 --- a/product_docs/docs/pgd/5/rel_notes/index.mdx +++ b/product_docs/docs/pgd/5/rel_notes/index.mdx @@ -1,6 +1,6 @@ --- title: "EDB Postgres Distributed Release notes" -navTitle: "Release notes ▶" +navTitle: "Release notes" navigation: - pgd_5.1.0_rel_notes - pgd_5.0.1_rel_notes diff --git a/product_docs/docs/pgd/5/routing/index.mdx b/product_docs/docs/pgd/5/routing/index.mdx index 7daaf7a5446..677587fb030 100644 --- a/product_docs/docs/pgd/5/routing/index.mdx +++ b/product_docs/docs/pgd/5/routing/index.mdx @@ -1,6 +1,6 @@ --- title: "Application connection management" -navTitle: "Connection management ▶" +navTitle: "Connection management" indexCards: none navigation: diff --git a/product_docs/docs/pgd/5/upgrades/index.mdx b/product_docs/docs/pgd/5/upgrades/index.mdx index c0bad3a4ad5..20b4710bc0f 100644 --- a/product_docs/docs/pgd/5/upgrades/index.mdx +++ b/product_docs/docs/pgd/5/upgrades/index.mdx @@ -1,6 +1,5 @@ --- title: "Upgrading" -navTitle: "Upgrading ▶" --- Because EDB Postgres Distributed consists of multiple software components, diff --git a/src/components/side-navigation.js b/src/components/side-navigation.js index fc4ac7c0752..c4cb6224523 100644 --- a/src/components/side-navigation.js +++ b/src/components/side-navigation.js @@ -1,4 +1,5 @@ import React from "react"; +import { useScrollRestoration } from "gatsby"; import { DarkModeToggle, Link, Logo } from "./"; const DocsLink = () => ( @@ -52,9 +53,11 @@ const SideNavigation = ({ footer = true, hideKBLink = false, }) => { + const scrollRestoration = useScrollRestoration("navigation-sidebar"); + return (