Merge pull request #6570 from EnterpriseDB/release/2025-02-28a

gvasquezvargas · web-flow · commit 9c620cb29d81 · 2025-02-28T17:46:18.000+01:00
Release: 2025-02-28a
diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/installing/complete.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/installing/complete.mdx
@@ -2,6 +2,7 @@
 title: "Completing and verifying the extension installation"
 navTitle: "Completing the installation"
 description: "Completing and verifying the installation of the AI Database and File System extensions."
+deepToC: true
 ---
 
 ### Installing the AI Database extension
@@ -15,6 +16,22 @@ CREATE EXTENSION
 edb=#
 ```
 
+#### Proxy settings
+
+If you are using a HTTP proxy, you may need to set the `HTTP_PROXY` and `HTTPS_PROXY` environment variables in Postgres's environment. You can do this by adding the following lines to the `environment` file in the `main` directory of the Postgres data directory.
+
+For example, on Ubuntu with Community Postgres, the `environment` file is located at `/etc/postgresql/16/main/environment`. Run the following commands to add the proxy settings to the `environment` file and restart the Postgres service.
+
+```bash
+echo "HTTP_PROXY = 'http://<yourproxysettings>/'" | sudo tee -a /etc/postgresql/16/main/environment
+echo "HTTPS_PROXY = 'http://<yourproxysettings>/'"  | sudo tee -a /etc/postgresql/16/main/environment
+sudo systemctl restart postgresql@16-main
+```
+
+Replace `<yourproxysettings>` with your proxy settings. If you are using a different version of Postgres, replace `16` with your version number. Consult the documentation for your Postgres distribution for the location of the `environment` file.
+
+Airgapped environments are not supported at this time.
+
 ### Installing the File System extension
 
 The File System extension is an extension that provides a set of functions to interact with the file system from within the database. The extension is installed using the `CREATE EXTENSION` command.
diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/models/using-models.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/models/using-models.mdx
@@ -8,15 +8,15 @@ Pipelines has a model registry that manages configured instances of models. Any
 
 ## Discover the preloaded models
 
-Pipelines comes with a set of pre-created models that you can use out of the box. 
+Pipelines comes with a set of pre-created models that you can use out of the box.
 
 To find them, you can run the following query:
 
 ```sql
 SELECT * FROM aidb.list_models();
 ```
 
-This will return a list of all the models that are currently created in the system. If you have not created any models, you'll see the default models that come with Pipelines.
+This will return a list of all the models that are currently configured in the system. If you have not created any models, you'll see the default models that come with Pipelines.
 
 ```text
          name          |     provider      |              options
@@ -27,7 +27,15 @@ This will return a list of all the models that are currently created in the syst
  dummy                 | dummy             | {"config={}"}
 ```
 
-The `bert`, `clip`, and `t5` models are all pre-created and ready to use. The `dummy` model is a placeholder model that can be used for testing purposes.
+The `bert`, `clip`, and `t5` models are all pre-configured and ready to use. The `dummy` model is a placeholder model that can be used for testing purposes.
+
+!!! note First use of local models
+The first time you use any of the local models, the model will be downloaded from [HuggingFace](https://huggingface.co/).  The model is then run locally.
+Subsequent uses of the model will be faster, as the model will be cached locally.
+
+If you use a proxy, ensure that it is [configured on the Postgres server](../installing/complete#proxy-settings).
+
+!!!
 
 ## Creating a Model
 
diff --git a/advocacy_docs/pg_extensions/extensionrefs.json b/advocacy_docs/pg_extensions/extensionrefs.json
@@ -102,6 +102,7 @@
     "edbspl": "https://www.enterprisedb.com/docs/epas/latest/application_programming/epas_compat_spl/02_spl_programs/",
     "spl_check": "https://www.enterprisedb.com/docs/pg_extensions/spl_check/",
     "parallel_clone": "undefined",
+    "pg_global_temporary_tables_(pgtt)":"https://www.enterprisedb.com/docs/pg_extensions/pgtt/",
     "pglogical_3.x": "https://www.enterprisedb.com/docs/pgd/3.7/pglogical/",
     "refdata": "https://www.enterprisedb.com/docs/pg_extensions/advanced_storage_pack/",
     "postgis": "https://www.enterprisedb.com/docs/postgis/latest/",
diff --git a/advocacy_docs/pg_extensions/index.mdx b/advocacy_docs/pg_extensions/index.mdx
diff --git a/advocacy_docs/pg_extensions/index.mdx.in b/advocacy_docs/pg_extensions/index.mdx.in
@@ -10,6 +10,7 @@ navigation:
     - query_advisor
     - wait_states
     - pgaudit
+    - pgtt
     - pg_failover_slots
     - pgRouting
     - pg_squeeze
diff --git a/advocacy_docs/pg_extensions/ldap_sync/installing.mdx b/advocacy_docs/pg_extensions/ldap_sync/installing.mdx
@@ -22,7 +22,7 @@ Before you begin the installation process:
 
 - Install [pg_cron](https://github.com/citusdata/pg_cron)
 
-- Install plpython3u utility to run ldap2pg
+- Install the [plpython3u](https://www.postgresql.org/docs/current/plpython.html) procedural language to run ldap2pg. Note that `plpython3u` is a potential security risk as it's an “untrusted” language. 
 
 - Install [ldap2pg](https://ldap2pg.readthedocs.io/en/latest/).
 
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
@@ -15,7 +15,9 @@ 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.1](pg_failover_slots_1.0.1_rel_notes) | 07 Jun 2023 |
 | [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.0.1_rel_notes.mdx b/advocacy_docs/pg_extensions/pg_failover_slots/rel_notes/pg_failover_slots_1.0.1_rel_notes.mdx
@@ -0,0 +1,13 @@
+---
+title: Release notes for PG Failover Slots version 1.0.1
+navTitle: "Version 1.0.1"
+---
+
+This release of PG Failover Slots includes:
+
+|  Type   |               Description               |
+| ------- | --------------------------------------- |
+| Bug fix | Fix support for PG13 and older.  The missing interfaces caused either disconnects or outright crashes on PG13 and older. |
+| Improvement | Test compatibility improvements.  Tests now work on PG11, and are more resilient to testing on slower machines. |
+| Improvement | PG16 compatibility improvements |
+| General | Various minor cleanups |
diff --git a/advocacy_docs/pg_extensions/pgrouting/configuring.mdx b/advocacy_docs/pg_extensions/pgrouting/configuring.mdx
@@ -3,10 +3,12 @@ title: Configuring pgRouting
 navTitle: Configuring
 ---
 !!! Note
-    `pgRouting` depends on PostGIS.  To install PostGIS, see [EDB PostGIS](https://www.enterprisedb.com/docs/postgis/latest/)
+    pgRouting depends on PostGIS.  To install PostGIS, see [EDB PostGIS](https://www.enterprisedb.com/docs/postgis/latest/)
 
-To enable `pgRouting`, create the extension.  
+To enable pgRouting, create the extension:
 
+```
 CREATE EXTENSION pgrouting;
+```
 
-For additional configuration information, see the [Configuring pgRouting](https://docs.pgrouting.org/latest/en/pgRouting-installation.html#configuring) in the official documentation.
+For additional configuration information, see [Configuring pgRouting](https://docs.pgrouting.org/latest/en/pgRouting-installation.html#configuring) in the official pgRouting documentation.
diff --git a/advocacy_docs/pg_extensions/pgrouting/index.mdx b/advocacy_docs/pg_extensions/pgrouting/index.mdx
@@ -10,11 +10,11 @@ directoryDefaults:
   product: pgRouting
 ---
 
-`pgRouting` is an extension released as open source software under the PostgreSQL License. 
+pgRouting is an extension released as open source software under the PostgreSQL License. 
 
-`pgRouting` provides geospatial routing functionality.
+pgRouting provides geospatial routing functionality.
 
-For more information about `pgRouting`, see:
+For more information about pgRouting, see:
 
 - [Installing pgRouting](installing.mdx)
 - [Configuring pgRouting](configuring.mdx)
diff --git a/advocacy_docs/pg_extensions/pgrouting/installing.mdx b/advocacy_docs/pg_extensions/pgrouting/installing.mdx
@@ -3,7 +3,7 @@ title: Installing pgRouting
 navTitle: Installing
 ---
 
-`pgRouting` is supported on the same platforms as the Postgres distribution you're using. Support for `pgRouting` starts with Postgres 13. For details, see:
+pgRouting is supported on the same platforms as the Postgres distribution you're using. Support for pgRouting starts with Postgres 13. For details, see:
 
 - [EDB Postgres Advanced Server Product Compatibility](https://www.enterprisedb.com/platform-compatibility#epas)
 - [PostgreSQL Product Compatibility](https://www.enterprisedb.com/resources/platform-compatibility#pg)
diff --git a/advocacy_docs/pg_extensions/pgrouting/using.mdx b/advocacy_docs/pg_extensions/pgrouting/using.mdx
@@ -3,4 +3,4 @@ title: Using pgRouting
 navTitle: Using
 ---
 
-For more information on using `pgRouting`, see [Getting Started](https://github.com/pgRouting/pgRouting?tab=readme-ov-file#getting-started) in the `pgRouting` official documentation.
+For more information on using pgRouting, see [Getting Started](https://github.com/pgRouting/pgRouting?tab=readme-ov-file#getting-started) in the pgRouting official documentation.
diff --git a/advocacy_docs/pg_extensions/pgtt/configuring.mdx b/advocacy_docs/pg_extensions/pgtt/configuring.mdx
@@ -0,0 +1,12 @@
+---
+title: Configuring pgtt 
+navTitle: Configuring
+---
+
+To enable `pgtt`, create the extension in the database:
+
+```sql
+CREATE EXTENSION pgtt;
+```
+
+For additional configuration information after enabling the extension, see the [pgtt official documentation](https://github.com/darold/pgtt?tab=readme-ov-file#configuration).
diff --git a/advocacy_docs/pg_extensions/pgtt/index.mdx b/advocacy_docs/pg_extensions/pgtt/index.mdx
@@ -0,0 +1,21 @@
+---
+title: 'pgtt'
+indexCards: none
+navigation:
+   - rel_notes
+   - installing
+   - configuring
+   - using
+directoryDefaults:
+  product: pgtt
+---
+
+`pgtt` is an extension released as open source software under the PostgreSQL License. 
+
+`pgtt` provides the ability to create, manage and use Oracle-style Global Temporary Tables.  
+
+For more information about `pgtt`, see:
+
+- [Installing pgtt](installing.mdx)
+- [Configuring pgtt](configuring.mdx)
+- [Using pgtt](using.mdx)
diff --git a/advocacy_docs/pg_extensions/pgtt/installing.mdx b/advocacy_docs/pg_extensions/pgtt/installing.mdx
@@ -0,0 +1,66 @@
+---
+title: Installing pgtt 
+navTitle: Installing
+---
+
+`pgtt` is supported on the same platforms as the Postgres distribution you're using. Support for `pgtt` starts with Postgres 12. For details, see:
+
+- [EDB Postgres Advanced Server Product Compatibility](https://www.enterprisedb.com/platform-compatibility#epas)
+- [PostgreSQL Product Compatibility](https://www.enterprisedb.com/resources/platform-compatibility#pg)
+- [EDB Postgres Extended Server Product Compatibility](https://www.enterprisedb.com/resources/platform-compatibility#epas_extended)
+
+## Installation
+
+Before you begin the installation process:
+
+- Install Postgres. See: 
+
+  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+  - [Installing PostgreSQL](https://www.postgresql.org/download/) 
+
+  - [Installing EDB Postgres Extended Server](/pge/latest/installing/)
+
+- Set up the repository.
+
+  Setting up the repository is a one-time task. If you've already set up your repository, you don't need to perform this step.
+
+  To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there.
+
+## Install the package
+
+The syntax for the package install command is:
+
+```shell
+# For SLES, CentOS, RHEL and its derivatives
+sudo <package-manager> -y install edb-<postgres><postgres_version>-pgtt0
+
+# For Debian and Ubuntu
+sudo <package-manager> -y install edb-<postgres><postgres_version>-pgtt-0
+```
+
+Where: 
+- `<package-manager>`is the package manager used with your operating system:
+
+  | Package manager |             Operating system     |
+  | --------------- | -------------------------------- |
+  | dnf             | RHEL 8/9 and derivatives         |
+  | yum             | RHEL 7 and derivatives, CentOS 7 |
+  | zypper          | SLES                             |
+  | apt-get         | Debian and derivatives           |
+
+- `<postgres>` is the distribution of Postgres you're using:
+
+ |    Postgres distribution     |   Value    |
+ | ---------------------------- | ---------- |
+ | PostgreSQL                   | pg         |
+ | EDB Postgres Advanced Server | as         |
+ | EDB Postgres Extended Server | postgresextended |
+
+- `<postgres_version>` is the version of Postgres you're using.
+
+For example, to install pgtt for EDB Postgres Advanced Server 15 on a RHEL 8 platform:
+
+```shell
+sudo dnf -y install edb-as15-pgtt0
+```
diff --git a/advocacy_docs/pg_extensions/pgtt/rel_notes/index.mdx b/advocacy_docs/pg_extensions/pgtt/rel_notes/index.mdx
@@ -0,0 +1,10 @@
+---
+title: 'pgtt release notes'
+navTitle: "Release notes"
+indexCards: none
+---
+The `pgtt` documentation describes the latest version of `pgtt`, including minor releases and patches. These release notes cover what was new in each release. For new functionality introduced in a minor or patch release, there are also indicators in the content about the release that introduced the feature.
+
+|               Version               | Release Date |
+| ----------------------------------- | ------------ |
+| [4.0](pgtt_4.0_rel_notes) | 30 May 2024  |
diff --git a/advocacy_docs/pg_extensions/pgtt/rel_notes/pgtt_4.0_rel_notes.mdx b/advocacy_docs/pg_extensions/pgtt/rel_notes/pgtt_4.0_rel_notes.mdx
@@ -0,0 +1,6 @@
+---
+title: Release notes for pgtt
+navTitle: "Version 4.0"
+---
+
+For `pgtt` release notes, see the [pgtt official change log](https://github.com/darold/pgtt/releases).
diff --git a/advocacy_docs/pg_extensions/pgtt/using.mdx b/advocacy_docs/pg_extensions/pgtt/using.mdx
@@ -0,0 +1,6 @@
+---
+title: Using pgtt
+navTitle: Using
+---
+
+For more information on using `pgtt`, see [Use of the extension](https://github.com/darold/pgtt?tab=readme-ov-file#use-of-the-extension) in the `pgtt` official documentation.
diff --git a/advocacy_docs/pg_extensions/query_advisor/installing.mdx b/advocacy_docs/pg_extensions/query_advisor/installing.mdx
@@ -3,7 +3,7 @@ title: Installing Query Advisor
 navTitle: Installing
 ---
 
-EDB Query Advisor is supported on the same platforms as the Postgres distribution you're using. Support for EDB Query Advisor starts with Postgres 12. For details, see:
+EDB Query Advisor is supported on the same platforms as the Postgres distribution you're using. Support for EDB Query Advisor starts with Postgres 13. For details, see:
 - [EDB Postgres Advanced Server Product Compatibility](https://www.enterprisedb.com/platform-compatibility#epas)
 
 - [PostgreSQL Product Compatibility](https://www.enterprisedb.com/resources/platform-compatibility#pg)
diff --git a/advocacy_docs/pg_extensions/query_advisor/rel_notes/index.mdx b/advocacy_docs/pg_extensions/query_advisor/rel_notes/index.mdx
@@ -3,6 +3,7 @@ title: 'EDB Query Advisor release notes'
 navTitle: "Release notes"
 indexCards: none
 navigation:
+- query_advisor_1.2.0_rel_notes
 - query_advisor_1.1.1_rel_notes
 - query_advisor_1.0.0_rel_notes
 ---
@@ -14,6 +15,7 @@ about the release that introduced the feature.
 
 | Version                                | Release Date |
 |----------------------------------------|--------------|
+| [1.2.0](query_advisor_1.2.0_rel_notes) | 28 Feb 2025  |
 | [1.1.1](query_advisor_1.1.1_rel_notes) | 12 Sep 2024  |
 | [1.0.0](query_advisor_1.0.0_rel_notes) | 10 May 2023  |
 
diff --git a/advocacy_docs/pg_extensions/query_advisor/rel_notes/query_advisor_1.2.0_rel_notes.mdx b/advocacy_docs/pg_extensions/query_advisor/rel_notes/query_advisor_1.2.0_rel_notes.mdx
@@ -0,0 +1,10 @@
+---
+title: Release notes for Query Advisor version 1.2.0
+navTitle: "Version 1.2.0"
+---
+
+This release of Query Advisor includes:
+
+|  Type       |                                Description                                                                                                                                                                |
+| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Enhancement |  New columns are added to the output of the `query_advisor_index_recommendations` and `query_advisor_statistics_recommendations` functions. For more information, see [using query advisor](../using.mdx).|
diff --git a/advocacy_docs/pg_extensions/query_advisor/using.mdx b/advocacy_docs/pg_extensions/query_advisor/using.mdx
@@ -8,23 +8,23 @@ EDB Query Advisor defines functions and views.
 ## Functions
 
 ### query_advisor_index_recommendations(min_filter, min_selectivity)
+
 Performs a global index suggestion. 
 
 By default, only predicates filtering at least 1000 rows and 30% of the rows in average are considered. You can use the `min_filter` and `min_selectivity` parameters to override the default. 
 
-The function generates the one- and two-column index candidates based on the predicates it collects. It replans all related workload queries in the presence of the hypothetical index with respect to each candidate. It recommends the list of indexes that bring the most value to the workload. It also shows the estimated index size and percentage cost reduction in the workload queries. You can decide, based on the size and benefit ratio, which indexes are the most useful for you.
+The function generates the one- and two-column index candidates based on the predicates it collects. It replans all related workload queries in the presence of the hypothetical index with respect to each candidate. It recommends the list of indexes that bring the most value to the workload. It also shows the estimated index size, estimated percentage cost reduction, total cost, absolute benefit and query ID's of the benefited queries in the workload. You can decide, based on the size and benefit ratio, which indexes are the most useful for you.
 
 For example:
 
 ```sql
 # running as postgres user
-select * from query_advisor_index_recommendations(0,0);
+select * from query_advisor_index_recommendations();
 __OUTPUT__
-|                             index                             | estimated_size_in_bytes | estimated_pct_cost_reduction |
-+---------------------------------------------------------------+-------------------------+------------------------------+
-| CREATE INDEX ON nation USING btree (n_name);                  | 8192                    | 14.619857                    |
-| CREATE INDEX ON supplier USING btree (s_suppkey,s_nationkey); | 933888                  | 0.63003576                   |
-| CREATE INDEX ON partsupp USING btree (ps_suppkey);            | 50159616                | 13.254544                    |
+                     index                     | estimated_size_in_bytes | estimated_pct_cost_reduction | total_cost | abs_benefit |   benefited_queryids   
+-----------------------------------------------+-------------------------+------------------------------+------------+-------------+------------------------
+ CREATE INDEX ON public.test USING btree (a);  |                 2605056 |                     49.87271 |       3386 |     1688.69 | {-4599253246525795071}
+ CREATE INDEX ON public.test1 USING btree (a); |                 2605056 |                     49.87271 |       3386 |     1688.69 | {28196068180564065}
 (3 rows)
 ```
 ### query_advisor_statistics_recommendations(min_err_estimate_num, min_err_estimate_ratio)
@@ -35,19 +35,20 @@ By default, `min_err_estimate_num` and `min_err_estimate_ratio` are set to `0`.
 
 The function generates potential candidates from the multi-column filters of your queries. Then, these candidates are processed by exploring different possible combinations. Currently the focus is on statistics for two columns at a time. 
 
-It also shows the weights to each candidate. Weights are based on how many queries would benefit from those extended statistics and what the execution cost of the queries would be.
+It also shows the weights to each candidate. Weights are based on how many queries would benefit from those extended statistics and what the execution cost of the queries would be. It shows query ID's of the benefited queries for which the recommendations are beneficial.
 
 For example:
 
 ```sql
 # running as postgres user
 select * from query_advisor_statistics_recommendations();
 __OUTPUT__
-|                             statistics                                                 |       weight       |
-+----------------------------------------------------------------------------------------+--------------------+
-| CREATE STATISTICS part_p_brand_p_container ON p_brand, p_container FROM public.part;   | 4940012.436935346  |
-| CREATE STATISTICS part_p_brand_p_type ON p_brand, p_type FROM public.part;             | 306202.2549564565  |
-| CREATE STATISTICS part_p_brand_p_size ON p_brand, p_size FROM public.part;             | 2879764.4054564573 |
+                       statistics                       |  weight  |                       benefited_queryids                       
+--------------------------------------------------------+----------+----------------------------------------------------------------
+ CREATE STATISTICS test1_a_b ON a, b FROM public.test1; |  7506.09 | {238391330592834993}
+ CREATE STATISTICS test_a_b ON a, b FROM public.test;   | 15012.09 | {6121296315499460229,-4518452432473118207,238391330592834993}
+ CREATE STATISTICS test_a_c ON a, c FROM public.test;   | 15012.09 | {-3664340941915161122,-4518452432473118207,238391330592834993}
+ CREATE STATISTICS test_b_c ON b, c FROM public.test;   | 11384.09 | {-4518452432473118207,238391330592834993}
 (3 rows)
 ```
 
diff --git a/advocacy_docs/pg_extensions/wait_states/index.mdx b/advocacy_docs/pg_extensions/wait_states/index.mdx
diff --git a/advocacy_docs/pg_extensions/wait_states/using.mdx b/advocacy_docs/pg_extensions/wait_states/using.mdx
diff --git a/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx b/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx
diff --git a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx
diff --git a/product_docs/docs/migration_toolkit/55/installing/installing_jdbc_driver.mdx b/product_docs/docs/migration_toolkit/55/installing/installing_jdbc_driver.mdx
diff --git a/product_docs/docs/pgd/5.6/backup.mdx b/product_docs/docs/pgd/5.6/backup.mdx
diff --git a/product_docs/docs/pgd/5.6/cli/index.mdx b/product_docs/docs/pgd/5.6/cli/index.mdx
diff --git a/product_docs/docs/pgd/5.6/decoding_worker.mdx b/product_docs/docs/pgd/5.6/decoding_worker.mdx
diff --git a/product_docs/docs/tde/15/secure_key/passphrase.mdx b/product_docs/docs/tde/15/secure_key/passphrase.mdx
