diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx index 8d43059de39..2bea31b38d2 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx @@ -22,9 +22,9 @@ The EDB Postgres® AI Cloud Service is a holistic platform which includes hybrid ## Overview -The EDB Postgres AI Cloud Service itself is a fully managed cloud service that provides a high-performance, scalable, and secure database platform for analytics, AI, and machine learning workloads. It also provides the platform for [EDB Postgres AI Analytics](../analytics/) and [EDB Postgres AI Machine Learning](../ai-ml/) services. +The EDB Postgres AI Cloud Service itself is a fully managed cloud service that provides a high-performance, scalable, and secure database platform for analytics and AI workloads. It also provides the platform for [EDB Postgres AI Analytics](../analytics/) and [EDB Postgres AIDB](../ai-ml/) services. -Cloud Service builds on the [EDB Postgres Advanced Server](/epas/latest) and [EDB Postgres Extended](/pge/latest) databases and it's designed to help organizations accelerate the development and deployment of AI and machine learning applications. +Cloud Service builds on the [EDB Postgres Advanced Server](/epas/latest) and [EDB Postgres Extended](/pge/latest) databases and it's designed to help organizations accelerate the development and deployment of AI and analytics applications. Databases in the EDB Postgres AI Cloud Service can run on EDB's own cloud accounts or managed by EDB on your own cloud on your behalf. diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_01_jan_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_01_jan_rel_notes.mdx similarity index 92% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_01_jan_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_01_jan_rel_notes.mdx index 2798469d410..cb10f457a66 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_01_jan_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_01_jan_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service January release notes navTitle: "January 2023" redirects: - /biganimal/latest/release_notes/2023_01_jan_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_01_jan_rel_notes/ --- Cloud Service's January 2023 release includes the following enhancements and bug fixes: @@ -11,4 +12,4 @@ Cloud Service's January 2023 release includes the following enhancements and bug | ----------- | ------------------------------------------------------------------------------------------------------------------------------- | | Enhancement | Added support for an additional AWS region: AWS Asia Pacific Southeast 2 (Sydney). | | Enhancement | Cloud Service CLI v1.12.0 & v1.13.0 now allows users to provision faraway replicas and get monitoring info for their clusters. | - \ No newline at end of file + diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_02_feb_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_02_feb_rel_notes.mdx similarity index 89% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_02_feb_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_02_feb_rel_notes.mdx index f783d3c6859..6c5ef0201e4 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_02_feb_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_02_feb_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service February release notes navTitle: "February 2023" redirects: - /biganimal/latest/release_notes/2023_02_feb_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_02_feb_rel_notes/ --- Cloud Service's February 2023 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_03_mar_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_03_mar_rel_notes.mdx similarity index 98% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_03_mar_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_03_mar_rel_notes.mdx index 5f65cc6ef71..56a1c5165a5 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_03_mar_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_03_mar_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service March release notes navTitle: "March 2023" redirects: - /biganimal/latest/release_notes/2023_03_mar_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_03_mar_rel_notes/ --- Cloud Service's March 2023 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_04_apr_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_04_apr_rel_notes.mdx similarity index 89% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_04_apr_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_04_apr_rel_notes.mdx index 60d3f359434..3213122566b 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_04_apr_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_04_apr_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service April release notes navTitle: "April 2023" redirects: - /biganimal/latest/release_notes/2023_04_apr_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_04_apr_rel_notes/ --- Cloud Service's April 2023 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_05_may_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_05_may_rel_notes.mdx similarity index 94% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_05_may_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_05_may_rel_notes.mdx index 662084c1382..a46e7d8b45e 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_05_may_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_05_may_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service May release notes navTitle: "May 2023" redirects: - /biganimal/latest/release_notes/2023_05_may_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_05_may_rel_notes/ --- Cloud Service's May 2023 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_06_jun_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_06_jun_rel_notes.mdx similarity index 95% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_06_jun_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_06_jun_rel_notes.mdx index 535a692ab85..7d472348e17 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_06_jun_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_06_jun_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service June release notes navTitle: "June 2023" redirects: - /biganimal/latest/release_notes/2023_06_jun_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_06_jun_rel_notes/ --- Cloud Service's June 2023 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_07_jul_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_07_jul_rel_notes.mdx similarity index 95% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_07_jul_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_07_jul_rel_notes.mdx index 13642c91a81..4479b5fe957 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_07_jul_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_07_jul_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service July release notes navTitle: "July 2023" redirects: - /biganimal/latest/release_notes/2023_07_jul_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_07_jul_rel_notes/ --- Cloud Service's July 2023 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_08_aug_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_08_aug_rel_notes.mdx similarity index 90% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_08_aug_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_08_aug_rel_notes.mdx index ad2a0827f82..bbbb76a5f83 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_08_aug_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_08_aug_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service August release notes navTitle: "August 2023" redirects: - /biganimal/latest/release_notes/2023_08_aug_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_08_aug_rel_notes/ --- Cloud Service's August 2023 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_09_sep_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_09_sep_rel_notes.mdx similarity index 96% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_09_sep_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_09_sep_rel_notes.mdx index e51b1c277ce..f7d64692700 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_09_sep_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_09_sep_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service September release notes navTitle: "September 2023" redirects: - /biganimal/latest/release_notes/2023_09_sep_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_09_sep_rel_notes/ --- Cloud Service's September 2023 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_10_oct_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_10_oct_rel_notes.mdx similarity index 92% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_10_oct_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_10_oct_rel_notes.mdx index 5186cee8b53..178cb899de1 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_10_oct_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_10_oct_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service October release notes navTitle: "October 2023" redirects: - /biganimal/latest/release_notes/2023_10_oct_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_10_oct_rel_notes/ --- Cloud Service's October 2023 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_11_nov_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_11_nov_rel_notes.mdx similarity index 94% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_11_nov_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_11_nov_rel_notes.mdx index 5e1dfc8efe9..cd8ec2699c4 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_11_nov_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_11_nov_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service November release notes navTitle: "November 2023" redirects: - /biganimal/latest/release_notes/2023_11_nov_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_11_nov_rel_notes/ --- Cloud Service's November 2023 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_12_dec_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_12_dec_rel_notes.mdx similarity index 91% rename from advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_12_dec_rel_notes.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_12_dec_rel_notes.mdx index 3a5c378a49e..a63a87b9a1b 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023_12_dec_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/2023_12_dec_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service December release notes navTitle: "December 2023" redirects: - /biganimal/latest/release_notes/2023_12_dec_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2023_12_dec_rel_notes/ --- Cloud Service's December 2023 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/index.mdx new file mode 100644 index 00000000000..cba14e3e277 --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2023/index.mdx @@ -0,0 +1,34 @@ +--- +title: Cloud Service release notes 2023 +navTitle: "2023" +description: 2023 release notes for Cloud Service +navigation: + - 2023_12_dec_rel_notes + - 2023_11_nov_rel_notes + - 2023_10_oct_rel_notes + - 2023_09_sep_rel_notes + - 2023_08_aug_rel_notes + - 2023_07_jul_rel_notes + - 2023_06_jun_rel_notes + - 2023_05_may_rel_notes + - 2023_04_apr_rel_notes + - 2023_03_mar_rel_notes + - 2023_02_feb_rel_notes + - 2023_01_jan_rel_notes +indexCards: none +--- + +| 2023 | +|--------------------------------------| +| [December 2023](2023_12_dec_rel_notes) | +| [November 2023](2023_11_nov_rel_notes) | +| [October 2023](2023_10_oct_rel_notes) | +| [September 2023](2023_09_sep_rel_notes)| +| [August 2023](2023_08_aug_rel_notes) | +| [July 2023](2023_07_jul_rel_notes) | +| [June 2023](2023_06_jun_rel_notes) | +| [May 2023](2023_05_may_rel_notes) | +| [April 2023](2023_04_apr_rel_notes) | +| [March 2023](2023_03_mar_rel_notes) | +| [February 2023](2023_02_feb_rel_notes) | +| [January 2023](2023_01_jan_rel_notes) | \ No newline at end of file diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_01_jan_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_01_jan_rel_notes.mdx index dac6eaabc2b..c5a78504853 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_01_jan_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_01_jan_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service January 2024 release notes navTitle: January 2024 redirects: - /biganimal/latest/release_notes/2024_01_jan_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2024_01_jan_rel_notes/ --- Cloud Service's January 2024 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_02_feb_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_02_feb_rel_notes.mdx index b8b87f7c223..05618b4db91 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_02_feb_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_02_feb_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service February 2024 release notes navTitle: February 2024 redirects: - /biganimal/latest/release_notes/2024_02_feb_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2024_02_feb_rel_notes/ --- Cloud Service's February 2024 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_03_mar_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_03_mar_rel_notes.mdx index 8dbf95c1d6b..e42cca9bb2a 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_03_mar_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_03_mar_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service March 2024 release notes navTitle: March 2024 redirects: - /biganimal/latest/release_notes/2024_03_mar_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2024_03_mar_rel_notes/ --- Cloud Service's March 2024 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_04_apr_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_04_apr_rel_notes.mdx index c891385f8f1..a6d89d13c3e 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_04_apr_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_04_apr_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service April 2024 release notes navTitle: April 2024 redirects: - /biganimal/latest/release_notes/2024_04_apr_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2024_04_apr_rel_notes/ --- Cloud Service's April 2024 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_05_may_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_05_may_rel_notes.mdx index 65217348d88..9039749faf5 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_05_may_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_05_may_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service May 2024 release notes navTitle: May 2024 redirects: - /biganimal/latest/release_notes/2024_05_may_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2024_05_may_rel_notes/ --- Cloud Service's May 2024 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_06_jun_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_06_jun_rel_notes.mdx index 9e7e8e38766..48ddcb2ad31 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_06_jun_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_06_jun_rel_notes.mdx @@ -3,6 +3,7 @@ title: Cloud Service June 2024 release notes navTitle: June 2024 redirects: - /biganimal/latest/release_notes/2024_06_jun_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2024_06_jun_rel_notes/ --- Cloud Service's June 2024 release includes the following enhancements and bug fixes: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_07_jul_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_07_jul_rel_notes.mdx index 71d9d10b034..e9fc25a8660 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_07_jul_rel_notes.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_07_jul_rel_notes.mdx @@ -3,10 +3,12 @@ title: BigAnimal July 2024 release notes navTitle: July 2024 redirects: - /biganimal/latest/release_notes/2024_07_jul_rel_notes/ #generated for BigAnimal URL path removal branch - - /biganimal/latest/release_notes/2024_07_jul_rel_notes/ #generated for BigAnimal URL path removal branch + - /edb-postgres-ai/cloud-service/release_notes/2024_07_jul_rel_notes/ --- -No updates were released for BigAnimal in July 2024. - +EDB Postgres® AI Cloud Service's July 2024 release includes the following enhancements and bug fixes: +| Type | Description | +|------|-------------| +| Enhancement | Support for [tagging AWS resources](/edb-postgres-ai/cloud-service/using_cluster/your_cloud_account/csp_tagging/) added | diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_08_aug_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_08_aug_rel_notes.mdx new file mode 100644 index 00000000000..b6eb0a6ac39 --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_08_aug_rel_notes.mdx @@ -0,0 +1,16 @@ +--- +title: Cloud Service August 2024 release notes +navTitle: August 2024 +redirect: +- /edb-postgres-ai/cloud-service/release_notes/2024_08_aug_rel_notes/ +--- + +EDB Postgres® AI Cloud Service's August 2024 release includes the following enhancements and bug fixes: + +| Type | Description | +|------|-------------| +| Enhancement | Volume Snapshot Backup support for Distributed HA Clusters (PGD). | +| Enhancement | BigAnimal CLI v3.9.0 is now available. Learn more about what’s new [**here**](https://cli.biganimal.com/versions/v3.9.0/). | +| Enhancement | Internal improvements and updates for the cloud service. | +| Enhancement | Support added for AWS t3 instance types. | +| Enhancement | UI now enables customers to change backup times. | diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_09_sep_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_09_sep_rel_notes.mdx new file mode 100644 index 00000000000..c5b817a24d8 --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_09_sep_rel_notes.mdx @@ -0,0 +1,12 @@ +--- +title: Cloud Service September 2024 release notes +navTitle: September 2024 +redirect: +- /edb-postgres-ai/cloud-service/release_notes/2024_09_sep_rel_notes/ +--- + +EDB Postgres® AI Cloud Service's September 2024 release includes the following enhancements and bug fixes: + +| Type | Description | +|------|-------------| +| Enhancement | Support for wal2json extension added. | diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_10_oct_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_10_oct_rel_notes.mdx new file mode 100644 index 00000000000..2e4db68ebca --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_10_oct_rel_notes.mdx @@ -0,0 +1,12 @@ +--- +title: Cloud Service October 2024 release notes +navTitle: October 2024 +redirect: +- /edb-postgres-ai/cloud-service/release_notes/2024_10_oct_rel_notes/ +--- + +EDB Postgres® AI Cloud Service's October 2024 release includes the following enhancements and bug fixes: + +| Type | Description | +|------|-------------| +| Enhancement | Implemented graceful handling of "0% storage available" scenarios. | diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx index 068069a0c69..d95154b39d7 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx @@ -3,6 +3,9 @@ title: Cloud Service release notes navTitle: Release notes description: Provides monthly release notes for Cloud Service navigation: + - 2024_10_oct_rel_notes + - 2024_09_sep_rel_notes + - 2024_08_aug_rel_notes - 2024_07_jul_rel_notes - 2024_06_jun_rel_notes - 2024_05_may_rel_notes @@ -10,26 +13,18 @@ navigation: - 2024_03_mar_rel_notes - 2024_02_feb_rel_notes - 2024_01_jan_rel_notes - - 2023_12_dec_rel_notes - - 2023_11_nov_rel_notes - - 2023_10_oct_rel_notes - - 2023_09_sep_rel_notes - - 2023_08_aug_rel_notes - - 2023_07_jul_rel_notes - - 2023_06_jun_rel_notes - - 2023_05_may_rel_notes - - 2023_04_apr_rel_notes - - 2023_03_mar_rel_notes - - 2023_02_feb_rel_notes - - 2023_01_jan_rel_notes redirects: - /biganimal/latest/release_notes/ #generated for BigAnimal URL path removal branch +indexCards: none --- The Cloud Service documentation describes the latest version of Cloud Service, including minor releases and patches. These release notes provide information on what was new in each release. For new functionality introduced in a minor or patch release, the content also indicates the release that introduced the feature. | 2024 | |----------------------------------------| +| [October 2024](2024_10_oct_rel_notes) | +| [September 2024](2024_09_sep_rel_notes)| +| [August 2024](2024_08_aug_rel_notes) | | [July 2024](2024_07_jul_rel_notes) | | [June 2024](2024_06_jun_rel_notes) | | [May 2024](2024_05_may_rel_notes) | @@ -38,17 +33,21 @@ The Cloud Service documentation describes the latest version of Cloud Service, i | [February 2024](2024_02_feb_rel_notes) | | [January 2024](2024_01_jan_rel_notes) | -| 2023 | +
2023 + +|| |--------------------------------------| -| [December 2023](2023_12_dec_rel_notes) | -| [November 2023](2023_11_nov_rel_notes) | -| [October 2023](2023_10_oct_rel_notes) | -| [September 2023](2023_09_sep_rel_notes)| -| [August 2023](2023_08_aug_rel_notes) | -| [July 2023](2023_07_jul_rel_notes) | -| [June 2023](2023_06_jun_rel_notes) | -| [May 2023](2023_05_may_rel_notes) | -| [April 2023](2023_04_apr_rel_notes) | -| [March 2023](2023_03_mar_rel_notes) | -| [February 2023](2023_02_feb_rel_notes) | -| [January 2023](2023_01_jan_rel_notes) | +| [December 2023](2023/2023_12_dec_rel_notes) | +| [November 2023](2023/2023_11_nov_rel_notes) | +| [October 2023](2023/2023_10_oct_rel_notes) | +| [September 2023](2023/2023_09_sep_rel_notes)| +| [August 2023](2023/2023_08_aug_rel_notes) | +| [July 2023](2023/2023_07_jul_rel_notes) | +| [June 2023](2023/2023_06_jun_rel_notes) | +| [May 2023](2023/2023_05_may_rel_notes) | +| [April 2023](2023/2023_04_apr_rel_notes) | +| [March 2023](2023/2023_03_mar_rel_notes) | +| [February 2023](2023/2023_02_feb_rel_notes) | +| [January 2023](2023/2023_01_jan_rel_notes) | + +
diff --git a/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/index.mdx b/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/index.mdx index 4d6373b08ca..4c7f7239c36 100644 --- a/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/index.mdx +++ b/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/index.mdx @@ -2,6 +2,9 @@ title: PG Failover Slots release notes navTitle: "Release notes" indexCards: none +navigation: +- pg_failover_slots_1.1.0_rel_notes +- pg_failover_slots_1.0.0_rel_notes --- The PG Failover Slots documentation describes the latest version of PG Failover Slots, including minor releases and patches. These release notes @@ -11,8 +14,8 @@ about the release that introduced the feature. | Version | Release Date | | --------------------------- | ------------ | +| [1.1.0](pg_failover_slots_1.1.0_rel_notes) | 27 Aug 2024 | | [1.0.0](pg_failover_slots_1.0.0_rel_notes) | 31 Mar 2023 | - diff --git a/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/pg_failover_slots_1.1.0_rel_notes.mdx b/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/pg_failover_slots_1.1.0_rel_notes.mdx new file mode 100644 index 00000000000..0540d0bc280 --- /dev/null +++ b/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/pg_failover_slots_1.1.0_rel_notes.mdx @@ -0,0 +1,13 @@ +--- +title: Release notes for PG Failover Slots version 1.1.0 +navTitle: "Version 1.1.0" +--- + +This release of PG Failover Slots includes: + +| Type | Description | +| ------- | --------------------------------------- | +| Feature | Add support for PostgreSQL 17. | +| Bug fix | Do not drop physical slots on standby. Previously, physical replication slots were dropped on the standby if they didn't exist on the primary. This fix ensures only logical replication slots are acted upon. +| Enhancement | New configuration setting: `pg_failover_slots.maintenance_db`. This value was previously hardcoded. | +| Enhancement | New configuration setting: `pg_failover_slots.worker_nap_time`. This value was previously hardcoded. | \ No newline at end of file diff --git a/advocacy_docs/pg_extensions/wait_states/configuring.mdx b/advocacy_docs/pg_extensions/wait_states/configuring.mdx new file mode 100644 index 00000000000..fbd5b58031c --- /dev/null +++ b/advocacy_docs/pg_extensions/wait_states/configuring.mdx @@ -0,0 +1,15 @@ +--- +title: Configuring EDB Wait States +navTitle: Configuring +--- + +## Parameters + +The following parameters in `postgresql.conf` control the EDB Wait States extension behavior. If you modify these parameters, reload or restart Postgres to apply the changes. + +| Parameter | Description | Default | Reload or Restart | | +|---------------------------------|-------------|---------|----------------------| +| `edb_wait_states.sampling_interval`| The interval between two EDB Wait States sampling cycles.| 1 second | Reload| +| `edb_wait_states.retention_period`| Deletes EDB Wait States log files after a defined retention period. | 604800 seconds (7 days)| Reload| | +| `edb_wait_states.enable_collection`| Enable or disable EDB Wait States data collection. | true | Reload| | +| `edb_wait_states.directory` | Stores the EDB Wait States logs in this directory. The path must be a full, absolute path. It can't be a relative path. | $PGDATA/edb_wait_states |Restart| diff --git a/advocacy_docs/pg_extensions/wait_states/index.mdx b/advocacy_docs/pg_extensions/wait_states/index.mdx index 21e78717259..acbcfcf8f1d 100644 --- a/advocacy_docs/pg_extensions/wait_states/index.mdx +++ b/advocacy_docs/pg_extensions/wait_states/index.mdx @@ -6,6 +6,7 @@ directoryDefaults: navigation: - rel_notes - installing + - configuring - using --- diff --git a/product_docs/docs/pgd/3.7/pglogical/subscriptions/index.mdx b/product_docs/docs/pgd/3.7/pglogical/subscriptions/index.mdx index 32090912e28..6da40ea7cc9 100644 --- a/product_docs/docs/pgd/3.7/pglogical/subscriptions/index.mdx +++ b/product_docs/docs/pgd/3.7/pglogical/subscriptions/index.mdx @@ -184,6 +184,11 @@ alternately choose your own replication slot name instead of using `gen_slot_name` then pass it as the `slot_name` parameter to `create_subscription`. +!!! Note pglogical.gen_slot_name +This function only accepts lower-case letters and underscores. When you pass names to this function, it converts upper-case text and non-underscore symbols to underscores. +Ensure that any names passed to the function have sufficient lower-case characters to be unique when normalized. +!!! + #### Parameters - `subscription_name` - name of the subscription; must be unique diff --git a/product_docs/docs/pgd/5.6/commit-scopes/camo.mdx b/product_docs/docs/pgd/5.6/commit-scopes/camo.mdx index 13fccf17ad2..fb5269bf609 100644 --- a/product_docs/docs/pgd/5.6/commit-scopes/camo.mdx +++ b/product_docs/docs/pgd/5.6/commit-scopes/camo.mdx @@ -241,7 +241,7 @@ node isn't part of a CAMO pair. To check the status of a transaction that was being committed when the node failed, the application must use the function -[`bdr.logical_transaction_status`](/pgd/latest/reference/functions#bdrlogical_transaction_status). +[`bdr.logical_transaction_status()`](/pgd/latest/reference/functions#bdrlogical_transaction_status). You pass this function the the node_id and transaction_id of the transaction you want to check on. With CAMO used in pair mode, you can use this function only on a node that's part of a CAMO pair. Along with Eager Replication, you can use it on all nodes. diff --git a/product_docs/docs/pgd/5.6/monitoring/sql.mdx b/product_docs/docs/pgd/5.6/monitoring/sql.mdx index a57699aefc5..4f5d18f198f 100644 --- a/product_docs/docs/pgd/5.6/monitoring/sql.mdx +++ b/product_docs/docs/pgd/5.6/monitoring/sql.mdx @@ -699,7 +699,7 @@ consumed the corresponding transactions. Consequently, it's not necessary to monitor the status of the group slot. The function [`bdr.monitor_local_replslots()`](/pgd/latest/reference/functions#bdrmonitor_local_replslots) provides a summary of whether all -PGD node replication slots are working as expected. For example: +PGD node replication slots are working as expected. This summary is also available on subscriber-only nodes that are operating as subscriber-only group leaders in a PGD cluster when [optimized topology](../nodes/subscriber_only/optimizing-so) is enabled. For example: ```sql bdrdb=# SELECT * FROM bdr.monitor_local_replslots(); @@ -710,11 +710,14 @@ bdrdb=# SELECT * FROM bdr.monitor_local_replslots(); One of the following status summaries is returned: -- `UNKNOWN`: `This node is not part of any BDR group` -- `OK`: `All BDR replication slots are working correctly` -- `OK`: `This node is part of a subscriber-only group` -- `CRITICAL`: `There is at least 1 BDR replication slot which is inactive` -- `CRITICAL`: `There is at least 1 BDR replication slot which is missing` +| Status | Message | +|----------|------------------------------------------------------------| +| UNKNOWN | This node is not part of any BDR group | +| OK | All BDR replication slots are working correctly | +| OK | This node is part of a subscriber-only group | +| CRITICAL | There is at least 1 BDR replication slot which is inactive | +| CRITICAL | There is at least 1 BDR replication slot which is missing | + ## Monitoring transaction COMMITs diff --git a/product_docs/docs/pgd/5.6/reference/catalogs-internal.mdx b/product_docs/docs/pgd/5.6/reference/catalogs-internal.mdx index fb688d60534..469e184b283 100644 --- a/product_docs/docs/pgd/5.6/reference/catalogs-internal.mdx +++ b/product_docs/docs/pgd/5.6/reference/catalogs-internal.mdx @@ -92,6 +92,12 @@ A view of the `bdr.event_history` catalog that displays the information in a mor human-friendly format. Specifically, it displays the event types and subtypes as textual representations rather than integers. +### `bdr.local_leader_change` + +This is a local cache of the recent portion of leader change history. It has the same fields as [`bdr.leader`](/pgd/5.6/reference/catalogs-visible#bdrleader), except that it is an ordered set of (node_group_id, leader_kind, generation) instead of a map tracking merely the current version. + + + ### `bdr.node_config` An internal catalog table with per-node configuration options. @@ -160,12 +166,18 @@ An internal catalog table holding current routing information for a proxy. #### `bdr.node_group_routing_info` columns -| Name | Type | Description | -|--------------------|-------|-----------------------------| -| node_group_id | oid | Node group ID | -| write_node_id | oid | Current write node | -| prev_write_node_id | oid | Previous write node | -| read_node_ids | oid[] | List of read-only nodes IDs | +| Name | Type | Description | +|----------------------|-------------|------------------------------------------------------------------------------------------| +| node_group_id | oid | Node group ID | +| write_node_id | oid | Current write node | +| prev_write_node_id | oid | Previous write node | +| read_node_ids | oid[] | List of read-only nodes IDs | +| record_version | bigint | Record version. Incremented by 1 on every material change to the routing record. | +| record_ts | timestamptz | Timestamp of last update to record_version. | +| write_leader_version | bigint | Write leader version. Copied from record_version every time write_node_id is changed. | +| write_leader_ts | timestamptz | Write leader timestamp. Copied from record_ts every time write_node_id is changed. | +| read_nodes_version | bigint | Read nodes version. Copied from record_version every time read_node_ids list is changed. | +| read_nodes_ts | timestamptz | Read nodes timestamp. Copied from record_tw every time read_node_ids list is changed. | ### `bdr.node_group_routing_summary` @@ -202,25 +214,25 @@ An internal catalog table holding proxy specific configurations. #### `bdr.proxy_config` columns -| Name | Type | Description | -|-----------------------------|----------|------------------------------------------------------------------------------| -| proxy_name | name | Name of the proxy | -| node_group_id | oid | Node group ID that this proxy uses | +| Name | Type | Description | +|-----------------------------|----------|----------------------------------------------------------------------------------| +| proxy_name | name | Name of the proxy | +| node_group_id | oid | Node group ID that this proxy uses | | listen_port | int | Port that the proxy uses for read-write connections (setting to 0 disables port) | -| max_client_conn | int | Number of maximum read-write client connections that the proxy accepts | -| max_server_conn | int | Number of maximum read-write connections that the server accepts | -| server_conn_timeout | interval | Timeout for the read-write server connections | -| server_conn_keepalive | interval | Interval between the server connection keep-alive | -| fallback_group_timeout | interval | Timeout needed for the fallback | -| fallback_group_ids | oid[] | List of group IDs to use for the fallback | -| listen_addrs | text[] | Listen address | +| max_client_conn | int | Number of maximum read-write client connections that the proxy accepts | +| max_server_conn | int | Number of maximum read-write connections that the server accepts | +| server_conn_timeout | interval | Timeout for the read-write server connections | +| server_conn_keepalive | interval | Interval between the server connection keep-alive | +| fallback_group_timeout | interval | Timeout needed for the fallback | +| fallback_group_ids | oid[] | List of group IDs to use for the fallback | +| listen_addrs | text[] | Listen address | | read_listen_port | int | Port that the proxy uses for read-only connections (setting to 0 disables port) | -| read_max_client_conn | int | Number of maximum read-only client connections that the proxy accepts | -| read_max_server_conn | int | Number of maximum read-only connections that the server accepts | -| read_server_conn_timeout | interval | Timeout for the server read-only connections | -| read_server_conn_keepalive | interval | Interval between the server read-only connection keep-alive | -| read_listen_addrs | text[] | Listen address for read-only connections | -| read_consensus_grace_period | interval | Duration for which proxy continues to route even upon loss of consensus | +| read_max_client_conn | int | Number of maximum read-only client connections that the proxy accepts | +| read_max_server_conn | int | Number of maximum read-only connections that the server accepts | +| read_server_conn_timeout | interval | Timeout for the server read-only connections | +| read_server_conn_keepalive | interval | Interval between the server read-only connection keep-alive | +| read_listen_addrs | text[] | Listen address for read-only connections | +| read_consensus_grace_period | interval | Duration for which proxy continues to route even upon loss of consensus | ### `bdr.proxy_config_summary` @@ -229,27 +241,27 @@ A friendly view of per-proxy, instance-specific configuration options. #### `bdr.proxy_config_summary` columns -| Name | Type | Description | -|---------------------------------|----------|-------------------------------------------------------------------------------| -| proxy_name | name | Name of the proxy | -| node_group_name | name | Node group name that this proxy uses | +| Name | Type | Description | +|---------------------------------|----------|-----------------------------------------------------------------------------------| +| proxy_name | name | Name of the proxy | +| node_group_name | name | Node group name that this proxy uses | | listen_port | int | Port that the proxy uses for read-write connections (setting to -1 disables port) | -| max_client_conn | int | Number of maximum read-write client connections that the proxy accepts | -| max_server_conn | int | Number of maximum read-write connections that the server accepts | -| server_conn_timeout | interval | Timeout for the read-write server connections | -| server_conn_keepalive | interval | Interval between the server connection keep-alive | -| node_group_enable_proxy_routing | boolean | Does the group the proxy is in enable proxy routing? | -| node_group_location | name | The group's location value | -| fallback_group_timeout | interval | Timeout needed for the fallback | -| fallback_group_ids | oid[] | List of group IDs to use for the fallback | -| listen_addrs | text[] | Listen address | +| max_client_conn | int | Number of maximum read-write client connections that the proxy accepts | +| max_server_conn | int | Number of maximum read-write connections that the server accepts | +| server_conn_timeout | interval | Timeout for the read-write server connections | +| server_conn_keepalive | interval | Interval between the server connection keep-alive | +| node_group_enable_proxy_routing | boolean | Does the group the proxy is in enable proxy routing? | +| node_group_location | name | The group's location value | +| fallback_group_timeout | interval | Timeout needed for the fallback | +| fallback_group_ids | oid[] | List of group IDs to use for the fallback | +| listen_addrs | text[] | Listen address | | read_listen_port | int | Port that the proxy uses for read-only connections (setting to -1 disables port) | -| read_max_client_conn | int | Number of maximum read-only client connections that the proxy accepts | -| read_max_server_conn | int | Number of maximum read-only connections that the server accepts | -| read_server_conn_timeout | interval | Timeout for the server read-only connections | -| read_server_conn_keepalive | interval | Interval between the server read-only connection keep-alive | -| read_listen_addrs | text[] | Listen address for read-only connections | -| read_consensus_grace_period | interval | Duration for which proxy continues to route even upon loss of consensus | +| read_max_client_conn | int | Number of maximum read-only client connections that the proxy accepts | +| read_max_server_conn | int | Number of maximum read-only connections that the server accepts | +| read_server_conn_timeout | interval | Timeout for the server read-only connections | +| read_server_conn_keepalive | interval | Interval between the server read-only connection keep-alive | +| read_listen_addrs | text[] | Listen address for read-only connections | +| read_consensus_grace_period | interval | Duration for which proxy continues to route even upon loss of consensus | ### `bdr.sequence_kind` @@ -258,7 +270,7 @@ An internal state table storing the type of each non-local sequence. We recommen #### `bdr.sequence_kind` columns -| Name | Type | Description | -| ------- | ---- | ----------------------------------------------------------- | -| seqid | oid | Internal OID of the sequence | +| Name | Type | Description | +|---------|------|-----------------------------------------------------------------------------| +| seqid | oid | Internal OID of the sequence | | seqkind | char | Internal sequence kind (`l`=local,`t`=timeshard,`s`=snowflakeid,`g`=galloc) | diff --git a/product_docs/docs/pgd/5.6/reference/catalogs-visible.mdx b/product_docs/docs/pgd/5.6/reference/catalogs-visible.mdx index 7e1179589db..eb96906b31e 100644 --- a/product_docs/docs/pgd/5.6/reference/catalogs-visible.mdx +++ b/product_docs/docs/pgd/5.6/reference/catalogs-visible.mdx @@ -377,6 +377,26 @@ Uses `bdr.run_on_all_nodes` to gather PGD information from all nodes. | postgres_version | text | PostgreSQL version on the node | | bdr_version | text | PGD version on the node | +### `bdr.leader` + +Tracks leader nodes across subgroups in the cluster. Shows the status of all write leaders and subscriber-only group leaders (when optimized topology is enabled) in the cluster. + +#### `bdr.leader` columns + +| Name | Type | Description | +| ---------------- | ---- | ------------------------------ | +| node_group_id | oid | ID of the node group | +| leader_node_id | oid | ID of the leader node | +| generation | int | Generation of the leader node. Leader_kind sets semantics. | +| leader_kind | "char" | Kind of the leader node | + +Leader_kind values can be: + +| Value | Description | +|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| W | Write leader, as per proxy routing. In this case leader is maintained by subgroup Raft instance.
`generation` corresponds to `write_leader_version` of respective `bdr.node_group_routing_info` record. | +| S | Subscriber-only group leader. This designated member of a SO group subscribes to upstream data nodes, and is tasked with publishing upstream changes to remaining SO group members. Leader is maintained by toplevel Raft instance.
`generation` is updated sequentially upon leader change. | + ### `bdr.local_consensus_snapshot` This catalog table contains consensus snapshots created or received by diff --git a/product_docs/docs/pgd/5.6/reference/functions.mdx b/product_docs/docs/pgd/5.6/reference/functions.mdx index 95b92ff5436..350a46ba0af 100644 --- a/product_docs/docs/pgd/5.6/reference/functions.mdx +++ b/product_docs/docs/pgd/5.6/reference/functions.mdx @@ -911,6 +911,8 @@ view `pg_replication_slots` (slot active or inactive) to provide a local check considering all replication slots except the PGD group slots. +This function also provides status information on subscriber-only nodes that are operating as subscriber-only group leaders in a PGD cluster when [optimized topology](../nodes/subscriber_only/optimizing-so) is enabled. + #### Synopsis ```sql @@ -919,8 +921,17 @@ bdr.monitor_local_replslots() #### Notes -This function returns a record with fields `status` and `message`, -as explained in [Monitoring replication slots](../monitoring/sql/#monitoring-replication-slots). +This function returns a record with fields `status` and `message`. + +| Status | Message | +|----------|------------------------------------------------------------| +| UNKNOWN | This node is not part of any BDR group | +| OK | All BDR replication slots are working correctly | +| OK | This node is part of a subscriber-only group | +| CRITICAL | There is at least 1 BDR replication slot which is inactive | +| CRITICAL | There is at least 1 BDR replication slot which is missing | + +Further explaination is available in [Monitoring replication slots](../monitoring/sql/#monitoring-replication-slots). ### `bdr.wal_sender_stats` @@ -1078,7 +1089,7 @@ This function begins a wait for CAMO transactions to be fully resolved. bdr.camo_transactions_resolved() ``` -### bdr.logical_transaction_status +### `bdr.logical_transaction_status` To check the status of a transaction that was being committed when the node failed, the application must use this function, passing as parameters the node id of the node the transaction originated from and the transaction id on the origin node. diff --git a/product_docs/docs/pgd/5.6/reference/index.json b/product_docs/docs/pgd/5.6/reference/index.json index 8e7c3a67f6e..a102cffe597 100644 --- a/product_docs/docs/pgd/5.6/reference/index.json +++ b/product_docs/docs/pgd/5.6/reference/index.json @@ -17,6 +17,7 @@ "bdrgroup_replslots_details": "/pgd/5.6/reference/catalogs-visible#bdrgroup_replslots_details", "bdrgroup_subscription_summary": "/pgd/5.6/reference/catalogs-visible#bdrgroup_subscription_summary", "bdrgroup_versions_details": "/pgd/5.6/reference/catalogs-visible#bdrgroup_versions_details", + "bdrleader": "/pgd/5.6/reference/catalogs-visible#bdrleader", "bdrlocal_consensus_snapshot": "/pgd/5.6/reference/catalogs-visible#bdrlocal_consensus_snapshot", "bdrlocal_consensus_state": "/pgd/5.6/reference/catalogs-visible#bdrlocal_consensus_state", "bdrlocal_node": "/pgd/5.6/reference/catalogs-visible#bdrlocal_node", @@ -299,6 +300,7 @@ "bdrddl_epoch": "/pgd/5.6/reference/catalogs-internal#bdrddl_epoch", "bdrevent_history": "/pgd/5.6/reference/catalogs-internal#bdrevent_history", "bdrevent_summary": "/pgd/5.6/reference/catalogs-internal#bdrevent_summary", + "bdrlocal_leader_change": "/pgd/5.6/reference/catalogs-internal#bdrlocal_leader_change", "bdrnode_config": "/pgd/5.6/reference/catalogs-internal#bdrnode_config", "bdrnode_config_summary": "/pgd/5.6/reference/catalogs-internal#bdrnode_config_summary", "bdrnode_group_config": "/pgd/5.6/reference/catalogs-internal#bdrnode_group_config", diff --git a/product_docs/docs/pgd/5.6/reference/index.mdx b/product_docs/docs/pgd/5.6/reference/index.mdx index d7cc35590ab..7612375d274 100644 --- a/product_docs/docs/pgd/5.6/reference/index.mdx +++ b/product_docs/docs/pgd/5.6/reference/index.mdx @@ -52,6 +52,7 @@ The reference section is a definitive listing of all functions, views, and comma * [`bdr.group_replslots_details`](catalogs-visible#bdrgroup_replslots_details) * [`bdr.group_subscription_summary`](catalogs-visible#bdrgroup_subscription_summary) * [`bdr.group_versions_details`](catalogs-visible#bdrgroup_versions_details) + * [`bdr.leader`](catalogs-visible#bdrleader) * [`bdr.local_consensus_snapshot`](catalogs-visible#bdrlocal_consensus_snapshot) * [`bdr.local_consensus_state`](catalogs-visible#bdrlocal_consensus_state) * [`bdr.local_node`](catalogs-visible#bdrlocal_node) @@ -158,7 +159,7 @@ The reference section is a definitive listing of all functions, views, and comma * [`bdr.get_configured_camo_partner`](functions#bdrget_configured_camo_partner) * [`bdr.wait_for_camo_partner_queue`](functions#bdrwait_for_camo_partner_queue) * [`bdr.camo_transactions_resolved`](functions#bdrcamo_transactions_resolved) - * [bdr.logical_transaction_status](functions#bdrlogical_transaction_status) + * [`bdr.logical_transaction_status`](functions#bdrlogical_transaction_status) ### [Commit Scope functions](functions#commit-scope-functions) * [`bdr.add_commit_scope`](functions#bdradd_commit_scope) * [`bdr.alter_commit_scope`](functions#bdralter_commit_scope) @@ -425,6 +426,7 @@ The reference section is a definitive listing of all functions, views, and comma * [`bdr.ddl_epoch`](catalogs-internal#bdrddl_epoch) * [`bdr.event_history`](catalogs-internal#bdrevent_history) * [`bdr.event_summary`](catalogs-internal#bdrevent_summary) + * [`bdr.local_leader_change`](catalogs-internal#bdrlocal_leader_change) * [`bdr.node_config`](catalogs-internal#bdrnode_config) * [`bdr.node_config_summary`](catalogs-internal#bdrnode_config_summary) * [`bdr.node_group_config`](catalogs-internal#bdrnode_group_config) diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/architecture.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/architecture.mdx index 41c66e7a42b..b338ba5839a 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/architecture.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/architecture.mdx @@ -98,8 +98,8 @@ Two kinds of routing are available with PGD proxies: In EDB Postgres Distributed for Kubernetes, local routing is used by default, and a configuration option is available to select global routing. -For more information, see the -[PGD documentation of routing with Raft](/pgd/latest/routing/raft/). +For more information on routing with Raft, see +[Proxies, Raft, and Raft subgroups](/pgd/latest/routing/raft/) in the PGD documentation. ### PGD architectures and high availability diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/backup.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/backup.mdx index eafa8914125..e9185dfeeb9 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/backup.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/backup.mdx @@ -60,19 +60,19 @@ The `.spec.backup.schedulers[].method` field allows you to define the scheduled - `volumeSnapshot` - `barmanObjectStore` (the default) -You can define more than one scheduler, but each method can only be used by one -scheduler, i.e. two schedulers are not allowed to use the same method. +You can define more than one scheduler, but each method can be used by only one +scheduler. That is, two schedulers aren't allowed to use the same method. -For object store backups, with the default `barmanObjectStore` method, the stanza -`spec.backup.configuration.barmanObjectStore` is used to define the object store information for both backup and wal archiving. -More information can be found in [EDB Postgres for Kubernetes Backup on Object Stores](/postgres_for_kubernetes/latest/backup_barmanobjectstore/). +For object store backups, with the default `barmanObjectStore` method, use the stanza +`spec.backup.configuration.barmanObjectStore` to define the object store information for both backup and WAL archiving. +For more information, see [Backup on object stores](/postgres_for_kubernetes/latest/backup_barmanobjectstore/) in the EDB Postgres for Kubernetes documentation. -To perform volumeSnapshot backups, the `volumeSnapshot` method can be selected. -The stanza -`spec.backup.configuration.barmanObjectStore.volumeSnapshot` is used to define the volumeSnapshot configuration. -More information can be found in [EDB Postgres for Kubernetes Backup on Volume Snapshots](/postgres_for_kubernetes/latest/backup_volumesnapshot/). +To perform volumeSnapshot backups, you can select the `volumeSnapshot` method. +Use the stanza +`spec.backup.configuration.barmanObjectStore.volumeSnapshot` to define the volumeSnapshot configuration. +For more information, see [Backup on volume snapshots](/postgres_for_kubernetes/latest/backup_volumesnapshot/) in the EDB Postgres for Kubernetes documentation. -The following example shows how to use the `volumeSnapshot` method for backup. WAL archiving is still done onto the barman object store. +This example shows how to use the `volumeSnapshot` method for backup. WAL archiving is still done onto the Barman object store. ```yaml apiVersion: pgd.k8s.enterprisedb.io/v1beta1 @@ -104,10 +104,10 @@ spec: immediate: true ``` -For more information about the comparison of two backup methods, see [EDB Postgres for Kubernetes for Object stores or volume snapshots](/postgres_for_kubernetes/latest/backup/#object-stores-or-volume-snapshots-which-one-to-use). +For a comparison of these two backup methods, see [Object stores or volume snapshots](/postgres_for_kubernetes/latest/backup/#object-stores-or-volume-snapshots-which-one-to-use) in the EDB Postgres for Kubernetes documentation. The `.spec.backup.schedulers[].schedule` field allows you to define a cron schedule, expressed -in the [Go `cron` package format](https://pkg.go.dev/github.com/robfig/cron#hdr-CRON_Expression_Format). +in the [Go `cron` package format](https://pkg.go.dev/github.com/robfig/cron#hdr-CRON_Expression_Format): ```yaml apiVersion: pgd.k8s.enterprisedb.io/v1beta1 @@ -123,28 +123,28 @@ spec: immediate: true ``` -You can suspend scheduled backups if necessary by setting `.spec.backup.schedulers[].suspend` to `true`. -This will prevent new backups from being scheduled. +If necessary, you can suspend scheduled backups by setting `.spec.backup.schedulers[].suspend` to `true`. +This setting prevents new backups from being scheduled. If you want to execute a backup as soon as the `ScheduledBackup` resource is created, set `.spec.backup.schedulers[].immediate` to `true`. `.spec.backupOwnerReference` indicates the `ownerReference` to use -in the created backup resources. The choices are: +in the created backup resources. The options are: -- **none** — No owner reference for created backup objects. -- **self** — Sets the `ScheduledBackup` object as owner of the backup. -- **cluster** — Sets the cluster as owner of the backup. +- **none** — Doesn't set an owner reference for created backup objects. +- **self** — Sets the `ScheduledBackup` object as owner of the backup. +- **cluster** — Sets the cluster as owner of the backup. !!! Warning - The `.spec.backup.cron` field is now deprecated. Please use + The `.spec.backup.cron` field is deprecated. Use `.spec.backup.schedulers` instead. - Note that while `.spec.backup.cron` can still be used, it cannot - be used simultaneously with `.spec.backup.schedulers`. + While you can still use `.spec.backup.cron`, you can't use it + at the same time as `.spec.backup.schedulers`. !!! Note The EDB Postgres for Kubernetes `ScheduledBackup` object contains the `cluster` option to specify the - cluster to back up. This option is currently not supported by EDB Postgres Distributed for Kubernetes and is + cluster to back up. This option currently isn't supported by EDB Postgres Distributed for Kubernetes and is ignored if specified. If an elected backup node is deleted, the operator transparently elects a new backup node diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/connectivity.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/connectivity.mdx index b32266ff3ff..32884097dad 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/connectivity.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/connectivity.mdx @@ -20,14 +20,14 @@ PGD cluster includes: Resources in a PGD cluster are accessible through Kubernetes services. Every PGD group manages several of them, namely: -- One service per node, used for internal communications (*node service*) +- One service per node, used for internal communications (*node service*). - A *group service* to reach any node in the group, used primarily by EDB Postgres Distributed for Kubernetes - to discover a new group in the cluster + to discover a new group in the cluster. - A *proxy service* to enable applications to reach the write leader of the - group transparently using PGD Proxy + group transparently using PGD Proxy. - A *proxy-r service* to enable applications to reach the read nodes of the - group, transparently using PGD Proxy. This service is disabled by default - and controlled by the `.spec.proxySettings.enableReadNodeRouting` setting + group transparently using PGD Proxy. This service is disabled by default + and controlled by the `.spec.proxySettings.enableReadNodeRouting` setting. For an example that uses these services, see [Connecting an application to a PGD cluster](#connecting-to-a-pgd-cluster-from-an-application). @@ -58,7 +58,7 @@ Proxy Service Template Proxy Read Service Template : Each PGD group has a proxy service to reach the group read nodes through - the PGD proxy, can be enabled by `.spec.proxySettings.enableReadNodeRouting`, + the PGD proxy. Can be enabled by `.spec.proxySettings.enableReadNodeRouting`, and can be configured in the `.spec.connectivity.proxyReadServiceTemplate` section. This is the entry-point service for the applications. @@ -169,11 +169,11 @@ either manually or automated, by updating the content of the secret. ## Connecting to a PGD cluster from an application -Connecting to a PGD Group from an application running inside the same Kubernetes cluster -or from outside the cluster is a simple procedure. In both cases, you will connect to -the proxy service of the PGD Group as the `app` user. The proxy service is a LoadBalancer -service that will route the connection to the write leader or read nodes of the PGD Group, -depending on which proxy service is connecting to. +Connecting to a PGD group from an application running inside the same Kubernetes cluster +or from outside the cluster is a simple procedure. In both cases, you connect to +the proxy service of the PGD group as the `app` user. The proxy service is a LoadBalancer +service that routes the connection to the write leader or read nodes of the PGD group, +depending on the proxy service it's connecting to. ### Connecting from inside the cluster diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/labels_annotations.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/labels_annotations.mdx index d40cab60aee..dc653ffc188 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/labels_annotations.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/labels_annotations.mdx @@ -41,9 +41,8 @@ their metadata cleaned up before creating the PGD node. This is written by the restore job. `k8s.pgd.enterprisedb.io/hash` -: Holds the hash of the certain part of PGDGroup spec that is utilized in various entities -like `Cluster`, `ScheduledBackup`, `StatefulSet`, and `Service (node, group and proxy service)` -to determine if any updates are required for the corresponding resources. +: To determine if any updates are required for the corresponding resources, holds the hash of the certain part of PGDGroup spec that's used in entities +like `Cluster`, `ScheduledBackup`, `StatefulSet`, and `Service (node, group and proxy service)`. `k8s.pgd.enterprisedb.io/latestCleanupExecuted` : Set in the PGDGroup to indicate that the cleanup was executed. @@ -53,7 +52,7 @@ to determine if any updates are required for the corresponding resources. generated. Added to the certificate resources. `k8s.pgd.enterprisedb.io/nodeRestartHash` -: Stores the hash of the CNP configuration in PGDGroup, a restart is needed when the configuration +: Stores the hash of the CNP configuration in PGDGroup. A restart is needed when the configuration is changed. `k8s.pgd.enterprisedb.io/noFinalizers` diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/ldap.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/ldap.mdx index c042e377e38..a795d14f652 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/ldap.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/ldap.mdx @@ -1,22 +1,22 @@ --- -title: 'LDAP Authentication' +title: 'LDAP authentication' originalFilePath: 'src/ldap.md' --- -EDB Postgres Distributed for Kubernetes supports LDAP authentication, +EDB Postgres Distributed for Kubernetes supports LDAP authentication. LDAP configuration on EDB Postgres Distributed for Kubernetes relies on the -implementation from EDB Postgres for Kubernetes (PG4K). Please refer to -[the PG4K documentation](/postgres_for_kubernetes/latest/postgresql_conf/#ldap-configuration) +implementation from EDB Postgres for Kubernetes (PG4K). See the +[PG4K documentation](/postgres_for_kubernetes/latest/postgresql_conf/#ldap-configuration) for the full context. !!! Important - Before you proceed, please take some time to familiarize with the - [LDAP authentication feature in the postgres documentation](https://www.postgresql.org/docs/current/auth-ldap.html). + Before you proceed, familiarize yourself with the + [LDAP authentication feature in the Postgres documentation](https://www.postgresql.org/docs/current/auth-ldap.html). -With LDAP support, only the user authentication is sent to LDAP, so the user must already exist in the postgres database. +With LDAP support, only the user authentication is sent to LDAP, so the user must already exist in the postgres database. -Here is an example of LDAP configuration using `simple bind` mode in PGDGroup, -postgres simply use `prefix + username + suffix` and password to bind the LDAP +This example shows an LDAP configuration using `simple bind` mode in PGDGroup. +The Postgres server uses `prefix + username + suffix` and password to bind the LDAP server to achieve the authentication. ```yaml @@ -31,10 +31,10 @@ spec: suffix: ",dc=example,dc=org" ``` -Here is a example of LDAP configuration using `search+bind` mode in PGDGroup. -In this mode, the postgres is first bound to the LDAP using `bindDN` with its password stored -in the secret `bindPassword`, then postgres tries to perform a search under `baseDN` to find a -username that matches the item specified by `searchAttribute`, if a match is found, postgres finally +This example shows configuring LDAP using `search+bind` mode in PGDGroup. +In this mode, the Postgres instance is first bound to the LDAP using `bindDN` with its password stored +in the secret `bindPassword`. Then Postgres tries to perform a search under `baseDN` to find a +username that matches the item specified by `searchAttribute`. If a match is found, Postgres finally verifies the entry and the password against the LDAP server. ```yaml diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/managed.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/managed.mdx index d19b9520628..f8bfb9e7a8a 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/managed.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/managed.mdx @@ -1,12 +1,12 @@ --- -title: 'Managed Configuration' +title: 'Managed configuration' originalFilePath: 'src/managed.md' --- The PGD operator allows configuring the `managed` section of a PG4K cluster. The `spec.cnp.managed` stanza -is used for configuring the supported managed roles within the cluster. +is used for configuring the supported managed roles in the cluster. -In this example, a pgdgroup is configured to have a managed role named `foo` with the specified properties set up in postgres. +In this example, a PGDgroup is configured to have a managed role named `foo` with the specified properties set up in postgres: ```yaml apiVersion: pgd.k8s.enterprisedb.io/v1beta1 @@ -30,5 +30,4 @@ spec: replication: true ``` -For more information about managed roles, refer to [EDB Postgres for Kubernetes recovery - Database Role Management](/postgres_for_kubernetes/latest/declarative_role_management/) - +For more information about managed roles, see [Database role management](/postgres_for_kubernetes/latest/declarative_role_management/) in the EDB Postgres for Kubernetes documentation. diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/mutations.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/mutations.mdx index 7ff807ad911..184090a2526 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/mutations.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/mutations.mdx @@ -3,15 +3,15 @@ title: 'SQLMutations' originalFilePath: 'src/mutations.md' --- -SQLMutations consist of a list of SQL queries to be executed on the application -database via the superuser role after a pgd node joins the pgdgroup. Each +SQLMutations consist of a list of SQL queries to execute on the application +database via the superuser role after a PGD node joins the PGDgroup. Each SQLMutation includes an `isApplied` list of queries and an `exec` list of queries. -The `isApplied` SQL queries are used to check if the mutation has already been +The `isApplied` SQL queries are used to check if the mutation was already applied. If any of the `isApplied` queries return false, the `exec` list of SQL -queries will be added to the execution queue. +queries is added to the execution queue. -Here is a sample of SQLMutations +Here's a sample of SQLMutations: ```yaml apiVersion: pgd.k8s.enterprisedb.io/v1beta1 @@ -39,24 +39,23 @@ spec: ``` -## SQLMutation Types +## SQLMutation types -The operator offers three types of SQLMutations, which can be specified by `spec.pgd.mutations[].type`, with `always` -being the default option. +The operator offers three types of SQLMutations, which you specify with `spec.pgd.mutations[].type`. The default is `always`. -- beforeSubgroupRaft -- always -- writeLeader +- `beforeSubgroupRaft` +- `always` +- `writeLeader` The `beforeSubgroupRaft` and `always` mutations are evaluated in every reconcile loop. The difference between the two mutations lies in their execution phase: -- For `always` mutations, they are run in each reconcile loop without any restrictions on the pgdgroup. -- On the other hand, `beforeSubgroupRaft` mutations are only executed if the pgdgroup has defined data nodes - and pgd proxies, and specifically before the subgroup raft becomes ready. +- For `always` mutations, they're run in each reconcile loop without any restrictions on the PGDgroup. +- `beforeSubgroupRaft` mutations are executed only if the PGDgroup has defined data nodes + and PGD proxies, and specifically before the subgroup Raft becomes ready. -Both `beforeSubgroupRaft` and `always` mutations can run on any pgd node within the pgdgroup, including witness nodes. -Therefore, they should not be used for making data changes to the application database, as witness nodes do not contain +Both `beforeSubgroupRaft` and `always` mutations can run on any PGD node in the PGDgroup, including witness nodes. +Therefore, don't use them for making data changes to the application database, as witness nodes don't contain application database data. The `writeLeader` mutation is triggered and executed after the write leader is elected. The `exec` operations diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/pg4k-pgd.v1beta1.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/pg4k-pgd.v1beta1.mdx index 3bf6a6d1b7d..1bdb2f4e32f 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/pg4k-pgd.v1beta1.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/pg4k-pgd.v1beta1.mdx @@ -1,11 +1,11 @@ --- -title: 'API Reference' +title: 'API reference' originalFilePath: 'src/pg4k-pgd.v1beta1.md' --- -

Package v1beta1 contains API Schema definitions for the pgd v1beta1 API group

+

Package v1beta1 contains API schema definitions for the pgd v1beta1 API group.

-## Resource Types +## Resource types - [PGDGroup](#pgd-k8s-enterprisedb-io-v1beta1-PGDGroup) - [PGDGroupCleanup](#pgd-k8s-enterprisedb-io-v1beta1-PGDGroupCleanup) diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/recovery.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/recovery.mdx index c1ab7eff3e9..65e66e6f133 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/recovery.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/recovery.mdx @@ -5,7 +5,7 @@ originalFilePath: 'src/recovery.md' In EDB Postgres Distributed for Kubernetes, recovery is available as a way to bootstrap a new PGD group starting from an available physical backup of a PGD node. -Recovery can't be performed in-place on an existing PGD group. +Recovery can't be performed in place on an existing PGD group. EDB Postgres Distributed for Kubernetes also supports point-in-time recovery (PITR), which allows you to restore a PGD group up to any point in time, from the first available backup in your catalog to the last archived @@ -157,7 +157,7 @@ spec: ``` !!! Important - When a `backupID` is specified, make sure to list only the related PGD node + When you specify a `backupID`, make sure to list only the related PGD node in the `serverNames` option, and avoid listing the other ones. !!! Note @@ -168,12 +168,12 @@ spec: ## Recovery from volumeSnapshot -You can also recover a pgdgroup from a volumeSnapshot backup. Stanza +You can also recover a PGDgroup from a volumeSnapshot backup. Stanza `spec.restore.volumeSnapshots` is used to define the criteria for volumeSnapshots restore candidates. The operator transparently selects the latest volumeSnapshot among the candidates. The operator requires the following annotations/labels in the volumeSnapshot. These -annotations/labels will be automatically added if volumeSnapshots are taken by the operator. +annotations/labels are automatically added if volumeSnapshots are taken by the operator. Annotations: @@ -185,12 +185,12 @@ Labels: - `k8s.enterprisedb.io/cluster` indicates the node where the volumeSnapshot is taken, crucial for fetching the serverName in the object store for WAL replaying. -- `k8s.enterprisedb.io/backupName` is the backup name of the volumeSnapshot, used to group - volumeSnapshots, when more volumes are defined in the backup. -- `k8s.enterprisedb.io/tablespaceName` represents the tablespace name of the volumeSnapshot, when +- `k8s.enterprisedb.io/backupName` is the backup name of the volumeSnapshot. Used to group + volumeSnapshots when more volumes are defined in the backup. +- `k8s.enterprisedb.io/tablespaceName` represents the tablespace name of the volumeSnapshot when the volumeSnapshot role is `PG_TABLESPACE`. -The following example illustrates a full recovery from volumeSnapshots. After the volumeSnapshot recovery, +This example shows a full recovery from volumeSnapshots. After the volumeSnapshot recovery, WAL replaying for full recovery will target server `pgdgroup-backup-vs-1`. ```yaml @@ -221,14 +221,14 @@ spec: maxParallel: 8 ``` -For more information, please see [EDB Postgres for Kubernetes recovery from volumeSnapshot objects](/postgres_for_kubernetes/latest/recovery/#recovery-from-volumesnapshot-objects). +For more information, see [Recovery from volumeSnapshot objects](/postgres_for_kubernetes/latest/recovery/#recovery-from-volumesnapshot-objects) in the EDB Postgres for Kubernetes documentation. ## PITR from volumeSnapshot -Same as when doing recovery from an object store, you can instruct PostgreSQL to halt the replay of Write-Ahead Logs (WALs) -at any specific moment during volumeSnapshot recovery. +You can instruct PostgreSQL to halt the replay of write-ahead logs (WALs) +at any specific moment during volumeSnapshot recovery. This is the same capability as when recovering from an object store. -This example demonstrates setting a time-based target for recovery using volume snapshots. +This example shows setting a time-based target for recovery using volume snapshots: ```yaml apiVersion: pgd.k8s.enterprisedb.io/v1beta1 @@ -263,4 +263,4 @@ spec: ## Recovery targets Beyond PITR are other recovery target criteria you can use. -For more information on all the available recovery targets, see [EDB Postgres for Kubernetes recovery targets](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/recovery/#point-in-time-recovery-pitr) in the EDB Postgres for Kubernetes documentation. +For more information on all the available recovery targets, see [Recovery](/postgres_for_kubernetes/latest/recovery/#point-in-time-recovery-pitr) in the EDB Postgres for Kubernetes documentation. diff --git a/tools/user/import/bareleasenotes/barelease.js b/tools/user/import/bareleasenotes/barelease.js old mode 100644 new mode 100755 index e77dfba342f..8abc39be5a7 --- a/tools/user/import/bareleasenotes/barelease.js +++ b/tools/user/import/bareleasenotes/barelease.js @@ -1,3 +1,5 @@ +#!/usr/bin/env node + import fetch from "node-fetch"; import fs from "fs"; import yargs from "yargs"; @@ -43,6 +45,8 @@ function printReleaseNotesHeader(currentMonth, currentYear) { return `--- title: Cloud Service ${getMonthName(currentMonth)} ${currentYear} release notes navTitle: ${getMonthName(currentMonth)} ${currentYear} +redirect: +- /edb-postgres-ai/cloud-service/release_notes/${currentYear}_${(currentMonth + 1).toString().padStart(2, "0")}_${getShortMonthName(currentMonth)}_rel_notes/ --- EDB Postgres® AI Cloud Service's ${getMonthName( @@ -85,6 +89,8 @@ async function fetchAndProcess(directory, currentYear, currentMonth) { const cleanLines = lines.flat().filter((item) => { return ( item !== "" && + item !== "None" && + item !== "N/A" && !item.startsWith("Improvements and updates for the cloud service") ); });