diff --git a/advocacy_docs/edb-postgres-ai/ai-ml/index.mdx b/advocacy_docs/edb-postgres-ai/ai-ml/index.mdx index f056c6dff8f..59e54f5a9e4 100644 --- a/advocacy_docs/edb-postgres-ai/ai-ml/index.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-ml/index.mdx @@ -9,7 +9,7 @@ navigation: - using-tech-preview --- -Postgres AI Database is designed to solve all AI data management needs, including storing, searching, and retrieving of AI data. This uplevels Postgres to a database that manages and serves all types of data modalities directly and combines it with its battle-proof strengths as an established Enterprise system of record that manages high-value business data. +EDB Postgres® AI Database is designed to solve all AI data management needs, including storing, searching, and retrieving of AI data. This uplevels Postgres to a database that manages and serves all types of data modalities directly and combines it with its battle-proof strengths as an established Enterprise system of record that manages high-value business data. In this tech preview, you will be able to use the pgai extension to build a simple retrieval augmented generation (RAG) application in Postgres. diff --git a/advocacy_docs/edb-postgres-ai/ai-ml/overview.mdx b/advocacy_docs/edb-postgres-ai/ai-ml/overview.mdx index 24c6765b802..becb50a0f74 100644 --- a/advocacy_docs/edb-postgres-ai/ai-ml/overview.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-ml/overview.mdx @@ -5,7 +5,7 @@ description: Where to start with EDB Postgres AI AI/ML and the pgai tech preview prevNext: True --- -At the heart of EDB Postgres AI is the EDB Postgres AI database (pgai). This builds on Postgres's flexibility and extends its capability to include store the vector data of embeddings. +At the heart of EDB Postgres® AI is the EDB Postgres AI database (pgai). This builds on Postgres's flexibility and extends its capability to include storing the vector data of embeddings. The pgai extension is currently available as a tech preview. It will be continuously extended with new functions. Here comes a description of the major functionality available to date. diff --git a/advocacy_docs/edb-postgres-ai/analytics/concepts.mdx b/advocacy_docs/edb-postgres-ai/analytics/concepts.mdx index 1dbd7a1becc..85b27735624 100644 --- a/advocacy_docs/edb-postgres-ai/analytics/concepts.mdx +++ b/advocacy_docs/edb-postgres-ai/analytics/concepts.mdx @@ -46,7 +46,7 @@ of an upcoming "Storage Location" feature that will also support ### Lakehouse Sync Lakehouse Sync is a Data Migration Service offered as part of the EDB -Postgres® AI platform. It can "sync" tables from a transactional database, to +Postgres AI platform. It can "sync" tables from a transactional database, to Lakehouse Tables in a destination Storage Location. Currently, it supports source databases hosted in the EDB Postgres AI Cloud Service (formerly known as BigAnimal). In the future, it will support more source databases (such as Oracle) diff --git a/advocacy_docs/edb-postgres-ai/analytics/index.mdx b/advocacy_docs/edb-postgres-ai/analytics/index.mdx index d500f685131..aa1f0279fee 100644 --- a/advocacy_docs/edb-postgres-ai/analytics/index.mdx +++ b/advocacy_docs/edb-postgres-ai/analytics/index.mdx @@ -9,9 +9,9 @@ navigation: - reference --- -_EDB Postgres Lakehouse extends the power of Postgres to analytical workloads, +EDB Postgres Lakehouse extends the power of Postgres to analytical workloads, by adding a vectorized query engine and separating storage from compute. Building -a Data Lakehouse has never been easier – just use Postgres._ +a Data Lakehouse has never been easier – just use Postgres. ## Rapid Analytics for Postgres @@ -51,7 +51,7 @@ it supports querying "Delta Tables" stored according to the Delta Lake protocol. ## Lakehouse Sync You can sync your own data from tables in transactional sources (initially, EDB -Postgres AI Cloud Service databases) into Lakehouse Tables in Storage Locations +Postgres® AI Cloud Service databases) into Lakehouse Tables in Storage Locations (initially, managed locations in S3 object storage). ## Fully Managed Service diff --git a/advocacy_docs/edb-postgres-ai/analytics/quick_start.mdx b/advocacy_docs/edb-postgres-ai/analytics/quick_start.mdx index ecebbb65c03..c2012886381 100644 --- a/advocacy_docs/edb-postgres-ai/analytics/quick_start.mdx +++ b/advocacy_docs/edb-postgres-ai/analytics/quick_start.mdx @@ -15,7 +15,7 @@ For more details and advanced use cases, see [reference](./reference). ## Introduction Postgres Lakehouse is a new type of Postgres “cluster” (it’s really just one -node) that you can provision in EDB Postgres AI Cloud Services (formerly known +node) that you can provision in EDB Postgres® AI Cloud Services (formerly known as "BigAnimal"). It includes a vectorized query engine (based on Apache [DataFusion](https://github.com/apache/datafusion)) for fast queries over columnar “Lakehouse Tables” in object storage diff --git a/advocacy_docs/edb-postgres-ai/analytics/reference.mdx b/advocacy_docs/edb-postgres-ai/analytics/reference.mdx index 47247f5be73..8ef4c8c4e16 100644 --- a/advocacy_docs/edb-postgres-ai/analytics/reference.mdx +++ b/advocacy_docs/edb-postgres-ai/analytics/reference.mdx @@ -22,7 +22,7 @@ Managed Storage Locations, and Lakehouse Sync) is limited to AWS. **EDB-Hosted Only**: "Bring Your Own Account" (BYOA) regions are NOT currently supported for Lakehouse resources. Support is limited to -ONLY **EDB Postgres AI - Hosted** environments on AWS (a.k.a. "EDB-Hosted AWS regions"). +ONLY **EDB Postgres® AI - Hosted** environments on AWS (a.k.a. "EDB-Hosted AWS regions"). This means you can select from one of the following regions: diff --git a/advocacy_docs/edb-postgres-ai/console/agent/create-machine-user.mdx b/advocacy_docs/edb-postgres-ai/console/agent/create-machine-user.mdx index 56d05701536..31196551535 100644 --- a/advocacy_docs/edb-postgres-ai/console/agent/create-machine-user.mdx +++ b/advocacy_docs/edb-postgres-ai/console/agent/create-machine-user.mdx @@ -4,7 +4,7 @@ description: Learn how to create a machine user in EDB Postgres AI Console to en --- -1. In the EDB Postgres AI Console, using your avatar's dropdown, select the **User Management** page. +1. In the EDB Postgres® AI Console, using your avatar's dropdown, select the **User Management** page. 2. Select the **Add New User** button. diff --git a/advocacy_docs/edb-postgres-ai/console/agent/index.mdx b/advocacy_docs/edb-postgres-ai/console/agent/index.mdx index 1f1ed3e173f..07648d0197b 100644 --- a/advocacy_docs/edb-postgres-ai/console/agent/index.mdx +++ b/advocacy_docs/edb-postgres-ai/console/agent/index.mdx @@ -12,7 +12,7 @@ navigation: To monitor your self-managed Postgres database with Beacon Agent, you will need to: -* [Create a machine user](create-machine-user) in the EDB Postgres AI Console. This will provide an access key for the agent. +* [Create a machine user](create-machine-user) in the EDB Postgres® AI Console. This will provide an access key for the agent. * [Install Beacon Agent](install-agent) on the server where your Postgres instance is running. You will use the access key to enable the agent to communicate with the EDB Postgres AI Estate service. * [Run Beacon Agent as a service](agent-as-a-service) to have it start automatically on system startup and restart after errors. diff --git a/advocacy_docs/edb-postgres-ai/console/agent/install-agent.mdx b/advocacy_docs/edb-postgres-ai/console/agent/install-agent.mdx index 9dc69e0dada..1797c6fa082 100644 --- a/advocacy_docs/edb-postgres-ai/console/agent/install-agent.mdx +++ b/advocacy_docs/edb-postgres-ai/console/agent/install-agent.mdx @@ -3,7 +3,7 @@ title: Installing Beacon Agent description: Installing, configuring, testing, and running Beacon Agent --- -The following steps walk you through how to install and configure Beacon Agent, test locally, and then run the agent to see the results in your Estates page in the EDB Postgres AI Console. +The following steps walk you through how to install and configure Beacon Agent, test locally, and then run the agent to see the results in your Estates page in the EDB Postgres® AI Console. Before you begin, you need to have the following: diff --git a/advocacy_docs/edb-postgres-ai/console/estate.mdx b/advocacy_docs/edb-postgres-ai/console/estate.mdx index 7e53bcd2366..156bcce627e 100644 --- a/advocacy_docs/edb-postgres-ai/console/estate.mdx +++ b/advocacy_docs/edb-postgres-ai/console/estate.mdx @@ -6,4 +6,4 @@ description: How to manage and integrate EDB Postgres AI Databases and more with ## What is EDB Postgres AI Estate -_The EDB Postgres AI Estate is a component of the EDB Postgres AI Console that provides a single pane of glass for managing and integrating EDB Postgres AI Databases and EDB Postgres AI Agents. The Estate provides a centralized location for managing the lifecycle of EDB Postgres AI Databases and EDB Postgres AI Agents, including provisioning, scaling, and monitoring. The Estate also provides a centralized location for managing the integration of EDB Postgres AI Databases and EDB Postgres AI Agents with the EDB Postgres AI Console's single pane of glass._ \ No newline at end of file +The EDB Postgres® AI Estate is a component of the EDB Postgres AI Console that provides a single pane of glass for managing and integrating EDB Postgres AI Databases and EDB Postgres AI Agents. The Estate provides a centralized location for managing the lifecycle of EDB Postgres AI Databases and EDB Postgres AI Agents, including provisioning, scaling, and monitoring. The Estate also provides a centralized location for managing the integration of EDB Postgres AI Databases and EDB Postgres AI Agents with the EDB Postgres AI Console's single pane of glass. \ No newline at end of file diff --git a/advocacy_docs/edb-postgres-ai/console/getstarted.mdx b/advocacy_docs/edb-postgres-ai/console/getstarted.mdx index 2c25b5a734c..ffb9e5ed18e 100644 --- a/advocacy_docs/edb-postgres-ai/console/getstarted.mdx +++ b/advocacy_docs/edb-postgres-ai/console/getstarted.mdx @@ -4,10 +4,10 @@ navTitle: Get Started description: Get started with the EDB Postgres AI Console. --- -The EDB Postgres AI Console is a web-based user interface that provides a single pane of glass for managing and monitoring EDB Postgres AI Database Cloud Service and EDB Postgres AI Databases. The EDB Postgres AI Console provides a unified view of the EDB Postgres AI Database Cloud Service and EDB Postgres AI Databases, allowing users to manage and monitor their databases, users, and resources from a single interface. +The EDB Postgres® AI Console is a web-based user interface that provides a single pane of glass for managing and monitoring EDB Postgres AI Database Cloud Service and EDB Postgres AI Databases. The EDB Postgres AI Console provides a unified view of the EDB Postgres AI Database Cloud Service and EDB Postgres AI Databases, allowing users to manage and monitor their databases, users, and resources from a single interface. ## Accessing the EDB Postgres AI Console To access the EDB Postgres AI Console, you will need to have an account with the EDB Postgres AI Database Cloud Service. If you do not have an account, you can sign up for a free trial at [https://www.enterprisedb.com/edb-postgres-ai](https://www.enterprisedb.com/edb-postgres-ai). -Once you have an account, you can access the EDB Postgres AI Console by navigating to [https://console.enterprisedb.com](https://console.enterprisedb.com) and logging in with your EDB Postgres AI Database Cloud Service credentials. +Once you have an account, you can access the EDB Postgres AI Console by navigating to [https://portal.biganimal.com](https://portal.biganimal.com) and logging in with your EDB Postgres AI Database Cloud Service credentials. diff --git a/advocacy_docs/edb-postgres-ai/console/index.mdx b/advocacy_docs/edb-postgres-ai/console/index.mdx index 7e4bce5d9f7..c94a6b16df0 100644 --- a/advocacy_docs/edb-postgres-ai/console/index.mdx +++ b/advocacy_docs/edb-postgres-ai/console/index.mdx @@ -10,6 +10,4 @@ navigation: - reference --- -Introduction to the EDB Postgres AI Console - -_The EDB Postgres AI Console is a web-based interface that allows you to manage your EDB Postgres AI environment. The console provides a user-friendly interface for managing your estate, including the remote agents and databases that run on your servers._ +The EDB Postgres® AI Console is a web-based interface that allows you to manage your EDB Postgres AI environment. The console provides a user-friendly interface for managing your estate, including the remote agents and databases that run on your servers. diff --git a/advocacy_docs/edb-postgres-ai/databases/cloudservice.mdx b/advocacy_docs/edb-postgres-ai/databases/cloudservice.mdx index 0eeb99399af..835212ecd5c 100644 --- a/advocacy_docs/edb-postgres-ai/databases/cloudservice.mdx +++ b/advocacy_docs/edb-postgres-ai/databases/cloudservice.mdx @@ -4,7 +4,7 @@ navTitle: Cloud Service description: An introduction to the EDB Postgres AI Cloud Service and its features. --- -The EDB Postgres AI Cloud Service, formerly known as [BigAnimal](/biganimal/latest/), is an evolution of the service to offer a holistic platform which offers hybrid data estate management, observability, and AI capabilities. +The EDB Postgres® AI Cloud Service, formerly known as [BigAnimal](/biganimal/latest/), is an evolution of the service to offer a holistic platform which offers hybrid data estate management, observability, and AI capabilities. The EDB Postgres AI Cloud Service itself is a fully managed cloud service that provides a high-performance, scalable, and secure database platform for AI and machine learning workloads. It also allows provides the platform for EDB Postgres AI Analytics and EDB Postgres AI Machine Learning services. diff --git a/advocacy_docs/edb-postgres-ai/databases/databases.mdx b/advocacy_docs/edb-postgres-ai/databases/databases.mdx index 9a749e92ad7..33969ef56b7 100644 --- a/advocacy_docs/edb-postgres-ai/databases/databases.mdx +++ b/advocacy_docs/edb-postgres-ai/databases/databases.mdx @@ -4,7 +4,7 @@ navTitle: Databases description: Deploy EDB Postgres AI Databases on-premises with the EDB Postgres AI Estate and Agent components. --- -EDB Postgres databases are the core of the EDB Postgres AI platform. EDB Postgres Databases are available for self-managed deployment and on the EDB Postgres AI Cloud Service. Self-managed EDB Postgres databases can be integrated with the EDB Postgres AI Cloud Service estate and managed through a single pane of glass by installing the [EDB Postgres AI Agent](/edb-postgres-ai/console/agent). +EDB Postgres® databases are the core of the EDB Postgres AI platform. EDB Postgres Databases are available for self-managed deployment and on the EDB Postgres AI Cloud Service. Self-managed EDB Postgres databases can be integrated with the EDB Postgres AI Cloud Service estate and managed through a single pane of glass by installing the [EDB Postgres AI Agent](/edb-postgres-ai/console/agent). ## EDB Postgres Advanced Server (EPAS) diff --git a/advocacy_docs/edb-postgres-ai/databases/index.mdx b/advocacy_docs/edb-postgres-ai/databases/index.mdx index 7d582172f38..ef7bd16c72e 100644 --- a/advocacy_docs/edb-postgres-ai/databases/index.mdx +++ b/advocacy_docs/edb-postgres-ai/databases/index.mdx @@ -9,7 +9,7 @@ navigation: - options --- -Building on decades of Postgres expertise, the EDB Postgres databases are the core of the EDB Postgres AI platform. EDB Postgres Advanced Server can take on Oracle workloads, while EDB Postgres Extended Server is designed for large-scale, mission-critical enterprise workloads. EDB Postgres Distributed provides high availability and fault tolerance for mission-critical workloads. +Building on decades of Postgres expertise, the EDB Postgres® databases are the core of the EDB Postgres AI platform. EDB Postgres Advanced Server can take on Oracle workloads, while EDB Postgres Extended Server is designed for large-scale, mission-critical enterprise workloads. EDB Postgres Distributed provides high availability and fault tolerance for mission-critical workloads. For here you can read more about the [databases](databases) that power EDB Postgres AI, and how they can be deployed on-premises with the EDB Postgres AI Estate and Agent components. diff --git a/advocacy_docs/edb-postgres-ai/databases/options.mdx b/advocacy_docs/edb-postgres-ai/databases/options.mdx index 4fd95b0ebdf..78068d666ad 100644 --- a/advocacy_docs/edb-postgres-ai/databases/options.mdx +++ b/advocacy_docs/edb-postgres-ai/databases/options.mdx @@ -15,7 +15,7 @@ Single instance databases are great for development and testing, but for product Primary/Secondary replication is a common high availability solution for databases. In this configuration, a primary database server is responsible for processing read and write requests. A secondary database server is configured to replicate the primary database server. If the primary database server fails, the secondary database server can take over and become the primary database server. -This configuration provides fault tolerance and high availability in a particular location. This can be used with EDB Postgres Advanced Server (EPAS) and EDB Postgres Extended Server (PGE). +This configuration provides fault tolerance and high availability in a particular location. This can be used with EDB Postgres® Advanced Server (EPAS) and EDB Postgres Extended Server (PGE). This is a standard configuration option on EDB Postgres AI Cloud Service. diff --git a/advocacy_docs/edb-postgres-ai/index.mdx b/advocacy_docs/edb-postgres-ai/index.mdx index 4023bff907f..653809b878f 100644 --- a/advocacy_docs/edb-postgres-ai/index.mdx +++ b/advocacy_docs/edb-postgres-ai/index.mdx @@ -15,5 +15,5 @@ navigation: - tools --- -The home of all EDB Postgres AI documentation. +The home of all EDB Postgres® AI documentation. diff --git a/advocacy_docs/edb-postgres-ai/overview/concepts.mdx b/advocacy_docs/edb-postgres-ai/overview/concepts.mdx index fe63f4178e7..c2c54d8ad5f 100644 --- a/advocacy_docs/edb-postgres-ai/overview/concepts.mdx +++ b/advocacy_docs/edb-postgres-ai/overview/concepts.mdx @@ -4,7 +4,7 @@ navTitle: Concepts description: A look at the concepts that underpin EDB Postgres AI. --- -EDB Postgres AI takes EDB’s leading expertise in Postgres and expands the scope of Postgres to address modern challenges. From simplifying your database estate management to infusing AI deep into Postgres and putting it to work to bring all your data under one analytical eye. +EDB Postgres® AI takes EDB’s leading expertise in Postgres and expands the scope of Postgres to address modern challenges. From simplifying your database estate management to infusing AI deep into Postgres and putting it to work to bring all your data under one analytical eye. EDB Postgres AI is composed of multiple elements which come together to deliver a unified and powerful experience: diff --git a/advocacy_docs/edb-postgres-ai/overview/guide.mdx b/advocacy_docs/edb-postgres-ai/overview/guide.mdx index 6a703da4b63..dde1ee8f16b 100644 --- a/advocacy_docs/edb-postgres-ai/overview/guide.mdx +++ b/advocacy_docs/edb-postgres-ai/overview/guide.mdx @@ -6,25 +6,25 @@ description: What do you want to use EDB Postgres AI for? Start navigating the d ## Do you want to run analytical queries on your Postgres data? -You'll want to look at the [EDB Postgres AI Analytics](/edb-postgres-ai/analytics) documentation, which covers the Postgres Lakehouse. +You'll want to look at the [EDB Postgres® AI Analytics](/edb-postgres-ai/analytics) documentation, which covers the Postgres Lakehouse. ## Are you looking at running machine learning models on your Postgres data? -You'll want to look at the [EDB Postgres AI Machine Learning](/edb-postgres-ai/ai-ml) documentation, which covers the technical preview of the pgai extension. +You'll want to look at the [EDB Postgres® AI Machine Learning](/edb-postgres-ai/ai-ml) documentation, which covers the technical preview of the pgai extension. ## Do you need to migrate your data to Postgres? -You'll want to look at the [EDB Postgres AI Migration](/edb-postgres-ai/tools/migration-and-ai) documentation, which covers the Migration Toolkit and Migration Portal. +You'll want to look at the [EDB Postgres® AI Migration](/edb-postgres-ai/tools/migration-and-ai) documentation, which covers the Migration Toolkit and Migration Portal. ## Do you want to manage your EDB Postgres AI Cloud databases? -You'll want to look at the [EDB Postgres AI Console](/edb-postgres-ai/console) documentation, which covers the Console and Cloud databases. +You'll want to look at the [EDB Postgres® AI Console](/edb-postgres-ai/console) documentation, which covers the Console and Cloud databases. ## Do you want to manage your self-managed Postgres databases as part of a hybrid data estate? -You'll want to look at the [EDB Postgres AI Platform Agent](/edb-postgres-ai/console/agent) documentation, which covers the Estate management and on premises agent installation. +You'll want to look at the [EDB Postgres® AI Platform Agent](/edb-postgres-ai/console/agent) documentation, which covers the Estate management and on premises agent installation. ## Do you want to know more about the EDB Postgres AI Cloud Service? -You'll want to look at the [EDB Postgres AI Cloud Service](/edb-postgres-ai/databases/cloudservice) documentation, which covers the Cloud Service and its databases. +You'll want to look at the [EDB Postgres® AI Cloud Service](/edb-postgres-ai/databases/cloudservice) documentation, which covers the Cloud Service and its databases. diff --git a/advocacy_docs/edb-postgres-ai/overview/index.mdx b/advocacy_docs/edb-postgres-ai/overview/index.mdx index 8e649a63560..79037cd1aed 100644 --- a/advocacy_docs/edb-postgres-ai/overview/index.mdx +++ b/advocacy_docs/edb-postgres-ai/overview/index.mdx @@ -6,7 +6,7 @@ iconName: Earth deepToC: true --- -EDB Postgres AI is a new era for EDB. With EDB Postgres AI, customers can now leverage EDB’s enterprise-grade Postgres offerings to support not just their mission critical transactional workloads, but also their analytical and AI applications. This also means that, in addition to the core transactional database releases you have come to expect from EDB, we will now be delivering regular updates to our analytics, AI, and platform capabilities. +EDB Postgres® AI is a new era for EDB. With EDB Postgres AI, customers can now leverage EDB’s enterprise-grade Postgres offerings to support not just their mission critical transactional workloads, but also their analytical and AI applications. This also means that, in addition to the core transactional database releases you have come to expect from EDB, we will now be delivering regular updates to our analytics, AI, and platform capabilities. In this overview section we will: diff --git a/advocacy_docs/edb-postgres-ai/overview/releasenotes.mdx b/advocacy_docs/edb-postgres-ai/overview/releasenotes.mdx index d940a919500..d2cf0d36642 100644 --- a/advocacy_docs/edb-postgres-ai/overview/releasenotes.mdx +++ b/advocacy_docs/edb-postgres-ai/overview/releasenotes.mdx @@ -4,7 +4,7 @@ navTitle: Release Notes description: The current features released and updated in EDB Postgres AI. --- -EDB Postgres AI is a a new era for EDB. With EDB Postgres AI, customers can now +EDB Postgres® AI is a a new era for EDB. With EDB Postgres AI, customers can now leverage EDB’s enterprise-grade Postgres offerings to support not just their mission critical transactional workloads, but also their analytical and AI applications. This also means that, in addition to the core transactional diff --git a/advocacy_docs/edb-postgres-ai/tools/backup.mdx b/advocacy_docs/edb-postgres-ai/tools/backup.mdx index bbe47b016ee..c8d85d56056 100644 --- a/advocacy_docs/edb-postgres-ai/tools/backup.mdx +++ b/advocacy_docs/edb-postgres-ai/tools/backup.mdx @@ -6,5 +6,5 @@ description: The backup and recovery tools available in EDB Postgres AI Tools [Barman](/supported-open-source/barman/) is a tool for managing backup and recovery of PostgreSQL databases. It is designed for business critical databases and provides features such as backup catalogues, incremental backup, retention policies, and remote recovery. -Barman is integrated with EDB Postgres AI and can be used to manage backups of your EDB Postgres AI databases. +Barman is integrated with EDB Postgres® AI and can be used to manage backups of your EDB Postgres AI databases. diff --git a/advocacy_docs/edb-postgres-ai/tools/index.mdx b/advocacy_docs/edb-postgres-ai/tools/index.mdx index ebd6205c435..5f3a5094991 100644 --- a/advocacy_docs/edb-postgres-ai/tools/index.mdx +++ b/advocacy_docs/edb-postgres-ai/tools/index.mdx @@ -9,7 +9,7 @@ navigation: - backup --- -Tools - Everything you need to manage your EDB Postgres AI databases, from migration to backup and recovery. +Tools - Everything you need to manage your EDB Postgres® AI databases, from migration to backup and recovery. EDB Postgres AI Tools is a set of tools, utilities and extensions that are designed to help you manage your EDB Postgres AI databases. From migration to backup and recovery, EDB Postgres AI Tools has you covered. diff --git a/advocacy_docs/edb-postgres-ai/tools/management.mdx b/advocacy_docs/edb-postgres-ai/tools/management.mdx index ff5a1924152..5eeb0f6fbf4 100644 --- a/advocacy_docs/edb-postgres-ai/tools/management.mdx +++ b/advocacy_docs/edb-postgres-ai/tools/management.mdx @@ -4,7 +4,7 @@ navTitle: Management description: An introduction to the management tools of EDB Postgres AI such as Postgres Enterprise Manager. --- -An introduction to the management tools of EDB Postgres AI such as Postgres Enterprise Manager. +An introduction to the management tools of EDB Postgres® AI such as Postgres Enterprise Manager. [PEM](/pem/latest/) is a comprehensive management tool for EDB Postgres Advanced Server and PostgreSQL databases. PEM provides database administrators with a graphical view of the server, allowing them to easily monitor and manage their databases. PEM also provides tools for database design, monitoring, and tuning, as well as tools for managing database objects, users, and roles. diff --git a/advocacy_docs/edb-postgres-ai/tools/migration-and-ai.mdx b/advocacy_docs/edb-postgres-ai/tools/migration-and-ai.mdx index 92d0141a3ec..4ce65a71b7a 100644 --- a/advocacy_docs/edb-postgres-ai/tools/migration-and-ai.mdx +++ b/advocacy_docs/edb-postgres-ai/tools/migration-and-ai.mdx @@ -4,7 +4,7 @@ navTitle: Migration and AI description: The Migration offering of EDB Postgres AI Tools includes an innovative migration copilot. --- -EDB Postgres AI Tools Migration Portal offers an [AI copilot](/migration_portal/latest/03_mp_using_portal/mp_ai_copilot/) to assist users who are migrating their databases to EDB Postgres. +EDB Postgres® AI Tools Migration Portal offers an [AI copilot](/migration_portal/latest/03_mp_using_portal/mp_ai_copilot/) to assist users who are migrating their databases to EDB Postgres. The AI copilot is an AI-driven chatbot tool that helps users with the migration process. The AI copilot is designed to help users with the following tasks: diff --git a/product_docs/docs/biganimal/release/release_notes/2024_01_jan_rel_notes.mdx b/product_docs/docs/biganimal/release/release_notes/2024_01_jan_rel_notes.mdx index 53d591c813b..35022e12f31 100644 --- a/product_docs/docs/biganimal/release/release_notes/2024_01_jan_rel_notes.mdx +++ b/product_docs/docs/biganimal/release/release_notes/2024_01_jan_rel_notes.mdx @@ -3,7 +3,7 @@ title: BigAnimal January 2024 release notes navTitle: January 2024 --- -BigAnimal's January 2024 includes the following enhancements and bugfixes: +BigAnimal's January 2024 release includes the following enhancements and bug fixes: | Type | Description | |------|-------------| diff --git a/product_docs/docs/biganimal/release/release_notes/2024_02_feb_rel_notes.mdx b/product_docs/docs/biganimal/release/release_notes/2024_02_feb_rel_notes.mdx index 489bfefc986..16459b26987 100644 --- a/product_docs/docs/biganimal/release/release_notes/2024_02_feb_rel_notes.mdx +++ b/product_docs/docs/biganimal/release/release_notes/2024_02_feb_rel_notes.mdx @@ -3,7 +3,7 @@ title: BigAnimal February 2024 release notes navTitle: February 2024 --- -BigAnimal's February 2024 includes the following enhancements and bugfixes: +BigAnimal's February 2024 release includes the following enhancements and bug fixes: | Type | Description | |-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| diff --git a/product_docs/docs/biganimal/release/release_notes/2024_03_mar_rel_notes.mdx b/product_docs/docs/biganimal/release/release_notes/2024_03_mar_rel_notes.mdx index 647dc1653a7..65863a8a8df 100644 --- a/product_docs/docs/biganimal/release/release_notes/2024_03_mar_rel_notes.mdx +++ b/product_docs/docs/biganimal/release/release_notes/2024_03_mar_rel_notes.mdx @@ -3,7 +3,7 @@ title: BigAnimal March 2024 release notes navTitle: March 2024 --- -BigAnimal's March 2024 includes the following enhancements and bugfixes: +BigAnimal's March 2024 release includes the following enhancements and bug fixes: | Type | Description | |------|-------------| diff --git a/product_docs/docs/biganimal/release/release_notes/2024_04_apr_rel_notes.mdx b/product_docs/docs/biganimal/release/release_notes/2024_04_apr_rel_notes.mdx index 17b80d755a3..2621cf80da9 100644 --- a/product_docs/docs/biganimal/release/release_notes/2024_04_apr_rel_notes.mdx +++ b/product_docs/docs/biganimal/release/release_notes/2024_04_apr_rel_notes.mdx @@ -3,7 +3,7 @@ title: BigAnimal April 2024 release notes navTitle: April 2024 --- -In April 2024 BigAnimal saw the following enhancements and bugfixes: +BigAnimal's April 2024 release includes the following enhancements and bug fixes: | Type | Description | |------|-------------| diff --git a/product_docs/docs/jdbc_connector/42.5.4.2/02_requirements_overview.mdx b/product_docs/docs/jdbc_connector/42.5.4.2/02_requirements_overview.mdx index cc46ec2f823..d1933cd8c10 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.2/02_requirements_overview.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.2/02_requirements_overview.mdx @@ -17,20 +17,20 @@ The JDBC Connector is supported on the same platforms as EDB Postgres Advanced S This table lists the latest JDBC Connector versions and their supported corresponding EDB Postgres Advanced Server (EPAS) versions. -| JDBC Connector | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 | -| ---------------------------------------------------------- | ------- | ------- | ------- | ------- | ------- | -| [42.5.4.2](01_jdbc_rel_notes/jdbc_42.5.4.2_rel_notes) | Y | Y | Y | Y | Y | -| [42.5.4.1](01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes) | Y | Y | Y | Y | Y | -| [42.5.1.2](01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes) | Y | Y | Y | Y | Y | -| [42.5.1.1](01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes) | N | Y | Y | Y | Y | -| [42.5.0.1](01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes) | N | Y | Y | Y | Y | -| [42.3.3.1](01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes) | N | Y | Y | Y | Y | -| [42.3.2.1](01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes) | N | Y | Y | Y | Y | -| [42.2.24.1](01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes) | N | Y | Y | Y | Y | -| [42.2.19.1](01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes) | N | N | Y | Y | Y | -| [42.2.12.3](01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes) | N | N | Y | Y | Y | -| [42.2.9.1](01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes) | N | N | N | Y | Y | -| [42.2.8.1](01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes) | N | N | N | Y | Y | +| JDBC Connector | EPAS16 | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 | +| ---------------------------------------------------------- | --------|-------- | ------- | ------- | ------- | ------- | +| [42.5.4.2](01_jdbc_rel_notes/jdbc_42.5.4.2_rel_notes) | Y | Y | Y | Y | Y | Y | +| [42.5.4.1](01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes) | N | Y | Y | Y | Y | Y | +| [42.5.1.2](01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes) | N | Y | Y | Y | Y | Y | +| [42.5.1.1](01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes) | N | N | Y | Y | Y | Y | +| [42.5.0.1](01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes) | N | N | Y | Y | Y | Y | +| [42.3.3.1](01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes) | N | N | Y | Y | Y | Y | +| [42.3.2.1](01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes) | N | N | Y | Y | Y | Y | +| [42.2.24.1](01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes) | N | N | Y | Y | Y | Y | +| [42.2.19.1](01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes) | N | N | N | Y | Y | Y | +| [42.2.12.3](01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes) | N | N | N | Y | Y | Y | +| [42.2.9.1](01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes) | N | N | N | N | Y | Y | +| [42.2.8.1](01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes) | N | N | N | N | Y | Y | ## Supported JDK distribution diff --git a/product_docs/docs/lasso/4/appendix-a.mdx b/product_docs/docs/lasso/4/appendix-a.mdx index 6ce0493b080..de67a2b981c 100644 --- a/product_docs/docs/lasso/4/appendix-a.mdx +++ b/product_docs/docs/lasso/4/appendix-a.mdx @@ -5,7 +5,7 @@ title: Servers accepting upload of reports !!! Note This information applies only to Lasso executables with external network access. You can verify that your Lasso -can access the Internet using the `--version` option. Look for +can access the Internet using the `--info` option. Look for the line `External network access enabled`. !!! diff --git a/product_docs/docs/pgd/5/deploy-config/deploy-biganimal/index.mdx b/product_docs/docs/pgd/5/deploy-config/deploy-biganimal/index.mdx index d9766e5b874..97810ab124e 100644 --- a/product_docs/docs/pgd/5/deploy-config/deploy-biganimal/index.mdx +++ b/product_docs/docs/pgd/5/deploy-config/deploy-biganimal/index.mdx @@ -6,7 +6,7 @@ redirects: - /pgd/latest/admin-biganimal/ #generated for pgd deploy-config-planning reorg --- -EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility. It runs in your cloud account or BigAnimal's cloud account, where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and multi-region Always On clusters. +EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility. It runs in your cloud account or BigAnimal's cloud account, where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and multi-region Always-on clusters. This section covers how to work with EDB Postgres Distributed when deployed on BigAnimal. diff --git a/product_docs/docs/pgd/5/deploy-config/deploy-tpa/deploying/index.mdx b/product_docs/docs/pgd/5/deploy-config/deploy-tpa/deploying/index.mdx index 9fe74716323..9a15b43292a 100644 --- a/product_docs/docs/pgd/5/deploy-config/deploy-tpa/deploying/index.mdx +++ b/product_docs/docs/pgd/5/deploy-config/deploy-tpa/deploying/index.mdx @@ -22,7 +22,7 @@ This applies to physical and virtual machines, both self-hosted and in the cloud !!! Note Get started with TPA and PGD quickly - If you want to experiment with a local deployment as quickly as possible, you can [deploy an EDB Postgres Distributed example cluster on Docker](/pgd/latest/quickstart/quick_start_docker) to configure, provision, and deploy a PGD 5 Always-On cluster on Docker. + If you want to experiment with a local deployment as quickly as possible, you can [deploy an EDB Postgres Distributed example cluster on Docker](/pgd/latest/quickstart/quick_start_docker) to configure, provision, and deploy a PGD 5 Always-on cluster on Docker. If deploying to the cloud is your aim, you can [deploy an EDB Postgres Distributed example cluster on AWS](/pgd/latest/quickstart/quick_start_aws) to get a PGD 5 cluster on your own Amazon account. diff --git a/product_docs/docs/pgd/5/deploy-config/deploy-tpa/index.mdx b/product_docs/docs/pgd/5/deploy-config/deploy-tpa/index.mdx index 4b6f2ff132d..70bbf1bb7b1 100644 --- a/product_docs/docs/pgd/5/deploy-config/deploy-tpa/index.mdx +++ b/product_docs/docs/pgd/5/deploy-config/deploy-tpa/index.mdx @@ -11,7 +11,7 @@ both self-hosted and in the cloud (with AWS EC2). !!! Note Get started with TPA and PGD quickly - If you want to experiment with a local deployment as quickly as possible, you can [deploying an EDB Postgres Distributed example cluster on Docker](/pgd/latest/quickstart/quick_start_docker) to configure, provision, and deploy a PGD 5 Always-On cluster on Docker. + If you want to experiment with a local deployment as quickly as possible, you can [deploying an EDB Postgres Distributed example cluster on Docker](/pgd/latest/quickstart/quick_start_docker) to configure, provision, and deploy a PGD 5 Always-on cluster on Docker. If deploying to the cloud is your aim, you can [deploying an EDB Postgres Distributed example cluster on AWS](/pgd/latest/quickstart/quick_start_aws) to get a PGD 5 cluster on your own Amazon account. diff --git a/product_docs/docs/pgd/5/overview/index.mdx b/product_docs/docs/pgd/5/overview/index.mdx index 2d0687c56ea..00715c9bdf7 100644 --- a/product_docs/docs/pgd/5/overview/index.mdx +++ b/product_docs/docs/pgd/5/overview/index.mdx @@ -63,13 +63,13 @@ DDL is replicated across nodes by default. DDL execution can be user controlled ## Architectural options and performance -### Always On architectures +### Always-on architectures A number of different architectures can be configured, each of which has different performance and scalability characteristics. The group is the basic building block consisting of 2+ nodes (servers). In a group, each node is in a different availability zone, with dedicated router and backup, giving immediate switchover and high availability. Each group has a dedicated replication set defined on it. If the group loses a node, you can easily repair or replace it by copying an existing node from the group. -The Always On architectures are built from either one group in a single location or two groups in two separate locations. Each group provides high availability. When two groups are leveraged in remote locations, they together also provide disaster recovery (DR). +The Always-on architectures are built from either one group in a single location or two groups in two separate locations. Each group provides high availability. When two groups are leveraged in remote locations, they together also provide disaster recovery (DR). Tables are created across both groups, so any change goes to all nodes, not just to nodes in the local group. diff --git a/product_docs/docs/pgd/5/planning/architectures.mdx b/product_docs/docs/pgd/5/planning/architectures.mdx index c23f9feeaa4..5a63bb78a5b 100644 --- a/product_docs/docs/pgd/5/planning/architectures.mdx +++ b/product_docs/docs/pgd/5/planning/architectures.mdx @@ -8,7 +8,7 @@ redirects: - /pgd/latest/architectures/ --- -Always On architectures reflect EDB’s Trusted Postgres architectures. They +Always-on architectures reflect EDB’s Trusted Postgres architectures. They encapsulate practices and help you to achieve the highest possible service availability in multiple configurations. These configurations range from single-location architectures to complex distributed systems that protect from @@ -21,16 +21,16 @@ described here. Use-case-specific variations have been successfully deployed in production. However, these variations must undergo rigorous architecture review first. -Always On architectures can be deployed using EDB’s standard deployment tool +Always-on architectures can be deployed using EDB’s standard deployment tool Trusted Postgres Architect (TPA) or configured manually. -## Standard EDB Always On architectures +## Standard EDB Always-on architectures EDB has identified a set of standardized architectures to support single- or multi-location deployments with varying levels of redundancy, depending on your recovery point objective (RPO) and recovery time objective (RTO) requirements. -The Always ON architecture uses three database node groups as a basic building block. +The Always-on architecture uses three database node groups as a basic building block. You can also use a five-node group for extra redundancy. EDB Postgres Distributed consists of the following major building blocks: @@ -40,7 +40,7 @@ EDB Postgres Distributed consists of the following major building blocks: - PGD Proxy — A connection router that makes sure the application is connected to the right data nodes. -All Always On architectures protect an increasing range of failure situations. +All Always-on architectures protect an increasing range of failure situations. For example, a single active location with two data nodes protects against local hardware failure but doesn't provide protection from location (data center or availability zone) failure. Extending that architecture with a backup @@ -75,7 +75,7 @@ requires an odd number of nodes to make decisions using a [Raft](https://raft.gi consensus model. Thus, even the simpler architectures always have three nodes, even if not all of them are storing data. -Applications connect to the standard Always On architectures by way of multi-host +Applications connect to the standard Always-on architectures by way of multi-host connection strings, where each PGD Proxy server is a distinct entry in the multi-host connection string. You must always have at least two proxy nodes in each location to ensure high availability. You can colocate the proxy with the @@ -83,11 +83,11 @@ database instance, in which case we recommend putting the proxy on every data node. Other connection mechanisms have been successfully deployed in production. However, -they aren't part of the standard Always On architectures. +they aren't part of the standard Always-on architectures. -### Always On Single Location +### Always-on Single Location -![Always On 1 Location, 3 Nodes Diagram](images/always_on_1x3_updated.png) +![Always-on 1 Location, 3 Nodes Diagram](images/always_on_1x3_updated.png) * Additional replication between data nodes 1 and 3 isn't shown but occurs as part of the replication mesh * Redundant hardware to quickly restore from local failures @@ -104,9 +104,9 @@ they aren't part of the standard Always On architectures. * Postgres Enterprise Manager (PEM) for monitoring (not depicted) * Can be shared by multiple PGD clusters -### Always On multi-location +### Always-on multi-location -![Always On 2 Locations, 3 Nodes Per Location, Active/Active Diagram](images/always_on_2x3_aa_updated.png) +![Always-on 2 Locations, 3 Nodes Per Location, Active/Active Diagram](images/always_on_2x3_aa_updated.png) * Application can be Active/Active in each location or can be Active/Passive or Active DR with only one location taking writes. * Additional replication between data nodes 1 and 3 isn't shown but occurs as part of the replication mesh. @@ -133,7 +133,7 @@ All architectures provide the following: * Zero downtime upgrades * Support for availability zones in public/private cloud -Use these criteria to help you to select the appropriate Always On architecture. +Use these criteria to help you to select the appropriate Always-on architecture. | | Single  Data Location | Two  Data  Locations | Two  Data Locations  + Witness | Three or More Data Locations | |------------------------------------------------------|----------------------------------------------------------|----------------------------------------------------------|----------------------------------------------------------|----------------------------------------------------------| diff --git a/product_docs/docs/pgd/5/planning/deployments.mdx b/product_docs/docs/pgd/5/planning/deployments.mdx index 236f3267526..17efb93254e 100644 --- a/product_docs/docs/pgd/5/planning/deployments.mdx +++ b/product_docs/docs/pgd/5/planning/deployments.mdx @@ -9,7 +9,7 @@ You can deploy and install EDB Postgres Distributed products using the following -- [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. TPA's flexibility allows deployments to virtual machines, AWS cloud instances or Linux host hardware. See [Deploying with TPA](../deploy-config/deploy-tpa/deploying/) for more information. -- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/distributed_highavailability/) in the [BigAnimal documentation](/biganimal/latest) for more information. +- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and and multi-region Always-on clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/distributed_highavailability/) in the [BigAnimal documentation](/biganimal/latest) for more information. - [EDB Postgres Distributed for Kubernetes](/postgres_distributed_for_kubernetes/latest/) is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. diff --git a/product_docs/docs/pgd/5/quickstart/further_explore_conflicts.mdx b/product_docs/docs/pgd/5/quickstart/further_explore_conflicts.mdx index 01d0c8fbf64..5c56c99a851 100644 --- a/product_docs/docs/pgd/5/quickstart/further_explore_conflicts.mdx +++ b/product_docs/docs/pgd/5/quickstart/further_explore_conflicts.mdx @@ -9,7 +9,7 @@ In a multi-master architecture like PGD, conflicts happen. PGD is built to handl A conflict can occur when one database node has an update from an application to a row and another node has a different update to the same row. This type of conflict is called a *row-level conflict*. Conflicts aren't errors. Resolving them effectively is core to how Postgres Distributed maintains consistency. -The best way to handle conflicts is not to have them in the first place! Use PGD's Always-On architecture with proxies to ensure that your applications write to the same server in the cluster. +The best way to handle conflicts is not to have them in the first place! Use PGD's Always-on architecture with proxies to ensure that your applications write to the same server in the cluster. When conflicts occur, though, it's useful to know how PGD resolves them, how you can control that resolution, and how you can find out that they're happening. Row insertion and row updates are two actions that can cause conflicts. diff --git a/product_docs/docs/pgd/5/quickstart/next_steps.mdx b/product_docs/docs/pgd/5/quickstart/next_steps.mdx index 69a98ba17bc..eae96251803 100644 --- a/product_docs/docs/pgd/5/quickstart/next_steps.mdx +++ b/product_docs/docs/pgd/5/quickstart/next_steps.mdx @@ -9,7 +9,7 @@ description: > ### Architecture -In this quick start, we created a single region cluster of high availability Postgres databases. This is the, Always On Single Location architecture, one of a range of available PGD architectures. Other architectures include Always On Multi-Location, with clusters in multiple data centers working together, and variations of both with witness nodes enhancing resilience. Read more in [architectural options](../planning/architectures/). +In this quick start, we created a single region cluster of high availability Postgres databases. This is the, Always-on Single Location architecture, one of a range of available PGD architectures. Other architectures include Always-on Multi-Location, with clusters in multiple data centers working together, and variations of both with witness nodes enhancing resilience. Read more in [architectural options](../planning/architectures/). ### Postgres versions diff --git a/product_docs/docs/pgd/5/quickstart/quick_start_aws.mdx b/product_docs/docs/pgd/5/quickstart/quick_start_aws.mdx index 524911f1141..079211cebdc 100644 --- a/product_docs/docs/pgd/5/quickstart/quick_start_aws.mdx +++ b/product_docs/docs/pgd/5/quickstart/quick_start_aws.mdx @@ -10,7 +10,7 @@ redirects: --- -This quick start sets up EDB Postgres Distributed with an Always On Single Location architecture using Amazon EC2. +This quick start sets up EDB Postgres Distributed with an Always-on Single Location architecture using Amazon EC2. ## Introducing TPA and PGD @@ -147,7 +147,7 @@ tpaexec configure democluster \ --hostnames-unsorted ``` -You specify the PGD-Always-ON architecture (`--architecture PGD-Always-ON`), which sets up the configuration for [PGD 5's Always On architectures](../planning/architectures/). As part of the default architecture, +You specify the PGD-Always-ON architecture (`--architecture PGD-Always-ON`), which sets up the configuration for [PGD 5's Always-on architectures](../planning/architectures/). As part of the default architecture, this configures your cluster with three data nodes, cohosting three [PGD Proxy](../routing/proxy/) servers, along with a [Barman](../backup#physical-backup) node for backup. Specify that you're using AWS (`--platform aws`) and eu-west-1 as the region (`--region eu-west-1`). diff --git a/product_docs/docs/pgd/5/quickstart/quick_start_docker.mdx b/product_docs/docs/pgd/5/quickstart/quick_start_docker.mdx index 6aab9a58948..2d3d9f01230 100644 --- a/product_docs/docs/pgd/5/quickstart/quick_start_docker.mdx +++ b/product_docs/docs/pgd/5/quickstart/quick_start_docker.mdx @@ -8,7 +8,7 @@ redirects: --- -This quick start uses TPA to set up PGD with an Always On Single Location architecture using local Docker containers. +This quick start uses TPA to set up PGD with an Always-on Single Location architecture using local Docker containers. ## Introducing TPA and PGD @@ -154,7 +154,7 @@ tpaexec configure democluster \ ``` You specify the PGD-Always-ON architecture (`--architecture PGD-Always-ON`), which -sets up the configuration for [PGD 5's Always On +sets up the configuration for [PGD 5's Always-on architectures](../planning/architectures/). As part of the default architecture, it configures your cluster with three data nodes, cohosting three [PGD Proxy](../routing/proxy/) servers, along with a [Barman](../backup#physical-backup) diff --git a/product_docs/docs/pgd/5/quickstart/quick_start_linux.mdx b/product_docs/docs/pgd/5/quickstart/quick_start_linux.mdx index dd8b3780f5e..acf40655704 100644 --- a/product_docs/docs/pgd/5/quickstart/quick_start_linux.mdx +++ b/product_docs/docs/pgd/5/quickstart/quick_start_linux.mdx @@ -132,7 +132,7 @@ tpaexec configure democluster \ --hostnames-unsorted ``` -You specify the PGD-Always-ON architecture (`--architecture PGD-Always-ON`), which sets up the configuration for [PGD 5's Always On architectures](../planning/architectures/). As part of the default architecture, it configures your cluster with three data nodes, cohosting three [PGD Proxy](../routing/proxy/) servers and a [Barman](/backup/#physical-backup) node for backup. +You specify the PGD-Always-ON architecture (`--architecture PGD-Always-ON`), which sets up the configuration for [PGD 5's Always-on architectures](../planning/architectures/). As part of the default architecture, it configures your cluster with three data nodes, cohosting three [PGD Proxy](../routing/proxy/) servers and a [Barman](/backup/#physical-backup) node for backup. For Linux hosts, specify that you're targeting a "bare" platform (`--platform bare`). TPA will determine the Linux version running on each host during deployment. See [the EDB Postgres Distributed compatibility table](https://www.enterprisedb.com/resources/platform-compatibility) for details about the supported operating systems. diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.5.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.5.0_rel_notes.mdx index 841995bf6f2..29806a56fdf 100644 --- a/product_docs/docs/pgd/5/rel_notes/pgd_5.5.0_rel_notes.mdx +++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.5.0_rel_notes.mdx @@ -17,7 +17,7 @@ We recommend that all users of PGD 5 upgrade to PGD 5.5. See [PGD/TPA upgrades]( Highlights of this 5.5.0 release include: * Read scalability enhancements in PGD Proxy which allow [read-only queries to be routed](/pgd/latest/routing/readonly/) to nodes that are members of a read-only pool. This feature can improve the overall performance of the PGD cluster. -I' + ## Compatibility !!! Note EDB server version compatibility diff --git a/product_docs/docs/pgd/5/repsets.mdx b/product_docs/docs/pgd/5/repsets.mdx index 6be0f762fd5..7fec0ed65e9 100644 --- a/product_docs/docs/pgd/5/repsets.mdx +++ b/product_docs/docs/pgd/5/repsets.mdx @@ -263,7 +263,7 @@ This configuration looks like this: ![Multi-Region 3 Nodes Configuration](./images/always-on-2x3-aa-updated.png) -This is the standard Always-On multiregion configuration as discussed in the [Choosing your architecture](planning/architectures) section. +This is the standard Always-on multiregion configuration as discussed in the [Choosing your architecture](planning/architectures) section. ### Application Requirements diff --git a/product_docs/docs/pgd/5/sequences.mdx b/product_docs/docs/pgd/5/sequences.mdx index 12da76b6fbe..a588a03668f 100644 --- a/product_docs/docs/pgd/5/sequences.mdx +++ b/product_docs/docs/pgd/5/sequences.mdx @@ -304,10 +304,10 @@ the next value. ```sql -- determine highest sequence value across all nodes SELECT max((x->'response'->'command_tuples'->0->>'nextval')::bigint) - FROM json_array_elements( + FROM jsonb_array_elements( bdr.run_on_all_nodes( E'SELECT nextval(\'public.sequence\');' - )::jsonb AS x; + )::jsonb) AS x; -- turn into a galloc sequence SELECT bdr.alter_sequence_set_kind('public.sequence'::regclass, 'galloc', $MAX + $MARGIN); diff --git a/product_docs/docs/pgd/5/terminology.mdx b/product_docs/docs/pgd/5/terminology.mdx index 0bf2f1881b2..2777b771fbe 100644 --- a/product_docs/docs/pgd/5/terminology.mdx +++ b/product_docs/docs/pgd/5/terminology.mdx @@ -137,7 +137,7 @@ Witness nodes primarily serve to help the cluster establish a consensus. An odd #### Write leader -In an Always-On architecture, a node is selected as the correct connection endpoint for applications. This node is called the write leader. Once selected, proxy nodes route queries and updates to it. With only one node receiving writes, unintended multi-node writes can be avoided. The write leader is selected by consensus of a quorum of data nodes. If the write leader becomes unavailable, the data nodes select another node to become write leader. Nodes that aren't the write leader are referred to as *shadow nodes*. +In an Always-on architecture, a node is selected as the correct connection endpoint for applications. This node is called the write leader. Once selected, proxy nodes route queries and updates to it. With only one node receiving writes, unintended multi-node writes can be avoided. The write leader is selected by consensus of a quorum of data nodes. If the write leader becomes unavailable, the data nodes select another node to become write leader. Nodes that aren't the write leader are referred to as *shadow nodes*. #### Writer diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_23_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_23_1_rel_notes.mdx new file mode 100644 index 00000000000..e9d8bfac2db --- /dev/null +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_23_1_rel_notes.mdx @@ -0,0 +1,12 @@ +--- +title: "EDB Postgres for Kubernetes 1.23.1 release notes" +navTitle: "Version 1.23.1" +--- + +Released: 29 Apr 2024 + +This release of EDB Postgres for Kubernetes includes the following: + +| Type | Description | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Upstream merge | Merged with community CloudNativePG 1.23.1. See the community [Release Notes](https://cloudnative-pg.io/documentation/1.23/release_notes/v1.23/). | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx index 5e1ef89fc17..28319235998 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx @@ -4,6 +4,7 @@ navTitle: "Release notes" redirects: - ../release_notes navigation: +- 1_23_1_rel_notes - 1_23_0_rel_notes - 1_22_3_rel_notes - 1_22_2_rel_notes @@ -95,6 +96,7 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | Version | Release date | Upstream merges | | -------------------------- | ------------ | ------------------------------------------------------------------------------------------- | +| [1.23.1](1_23_1_rel_notes) | 29 Apr 2024 | Upstream [1.23.1](https://cloudnative-pg.io/documentation/1.22/release_notes/v1.23/) | | [1.23.0](1_23_0_rel_notes) | 24 Apr 2024 | Upstream [1.23.0](https://cloudnative-pg.io/documentation/1.22/release_notes/v1.23/) | | [1.22.3](1_22_3_rel_notes) | 24 Apr 2024 | Upstream [1.22.3](https://cloudnative-pg.io/documentation/1.22/release_notes/v1.22/) | | [1.22.2](1_22_2_rel_notes) | 22 Mar 2024 | Upstream [1.22.2](https://cloudnative-pg.io/documentation/1.22/release_notes/v1.22/) | diff --git a/tools/user/import/bareleasenotes/barelease.js b/tools/user/import/bareleasenotes/barelease.js index 6284171b0d0..c176227953f 100644 --- a/tools/user/import/bareleasenotes/barelease.js +++ b/tools/user/import/bareleasenotes/barelease.js @@ -47,7 +47,7 @@ navTitle: ${getMonthName(currentMonth)} ${currentYear} BigAnimal's ${getMonthName( currentMonth, - )} ${currentYear} includes the following enhancements and bugfixes: + )} ${currentYear} release includes the following enhancements and bug fixes: | Type | Description | |------|-------------|`; @@ -58,6 +58,7 @@ async function fetchAndProcess(directory, currentYear, currentMonth) { const response = await fetch( "https://status.biganimal.com/api/maintenance-windows/done/index.json", ); + ``; const data = await response.json(); const filteredData = data.data.filter((item) => {