Merge pull request #3578 from EnterpriseDB/release/2023-01-27

Release: 2023-01-27

gatsby-config.js

@@ -5,6 +5,8 @@ const gracefulFs = require("graceful-fs");
 
 const algoliaTransformer = require("./src/constants/algolia-indexing.js");
 
+const { replacePathVersion } = require("./src/constants/gatsby-utils.js");
+
 const ANSI_BLUE = "\033[34m";
 const ANSI_GREEN = "\033[32m";
 const ANSI_STOP = "\033[0m";
@@ -201,8 +203,14 @@ module.exports = {
           allSitePage: { nodes: allPages },
           allMdx: { nodes: allMdxNodes },
         }) => {
+          const knownPaths = new Set(allPages.map((p) => p.path));
           const mapPathToTime = allMdxNodes.reduce((acc, node) => {
-            acc[node.fields.path] = { lastmod: node.fields.mtime };
+            if (knownPaths.has(node.fields.path))
+              acc[node.fields.path] = { lastmod: node.fields.mtime };
+            else
+              acc[replacePathVersion(node.fields.path)] = {
+                lastmod: node.fields.mtime,
+              };
             return acc;
           }, {});
 

product_docs/docs/epas/14/epas_guide/01_introduction/02_conventions.mdx

@@ -4,12 +4,13 @@ title: "Conventions used"
 
 <div id="conventions" class="registered_link"></div>
 
-The following is a list of conventions used throughout this document.
-
--   This guide applies to both Linux and Windows systems. Directory paths are presented in the Linux format with forward slashes. When working on Windows systems, start the directory path with the drive letter followed by a colon and substitute back slashes for forward slashes.
--   Some of the information in this document may apply interchangeably to the PostgreSQL and EDB Postgres Advanced Server database systems. The term *EDB Postgres Advanced Server* is used to refer to EDB Postgres Advanced Server. The term *Postgres* is used to generically refer to both PostgreSQL and EDB Postgres Advanced Server. When a distinction needs to be made between these two database systems, the specific names, PostgreSQL or EDB Postgres Advanced Server are used.
--   The installation directory path of the PostgreSQL or EDB Postgres Advanced Server products is referred to as *POSTGRES_INSTALL_HOME*.
-    -   For PostgreSQL Linux installations, this defaults to `/opt/PostgreSQL/x.x` for version 10 and earlier. For later versions, use the PostgreSQL community packages.
-    -   For EDB Postgres Advanced Server Linux installations accomplished using the interactive installer for version 10 and earlier, this defaults to `/opt/edb/asx.x`.
-    -   For EDB Postgres Advanced Server Linux installations accomplished using an RPM package, this defaults to `/usr/edb/asxx`.
-    -   For EDB Postgres Advanced Server Windows installations, this defaults to `C:\Program Files\edb\asxx`. The product version number is represented by `x.x` or by `xx` for version 10 and later.
+This information applies to both Linux and Windows systems. Directory paths are presented in the Linux format with forward slashes. When working on Windows systems, start the directory path with the drive letter followed by a colon and substitute back slashes for forward slashes.
+
+Some of this information might apply interchangeably to the PostgreSQL and EDB Postgres Advanced Server database systems. The term *EDB Postgres Advanced Server* is used to refer to EDB Postgres Advanced Server. The term *Postgres* is used to generically refer to both PostgreSQL and EDB Postgres Advanced Server. When a distinction needs to be made between these two database systems, the specific names&mdash;PostgreSQL or EDB Postgres Advanced Server&mdash;are used.
+
+The installation directory path of the PostgreSQL or EDB Postgres Advanced Server products is referred to as *POSTGRES_INSTALL_HOME*.
+
+-   For PostgreSQL Linux installations, the default is `/opt/PostgreSQL/x.x` for version 10 and earlier. For later versions, use the PostgreSQL community packages.
+-   For EDB Postgres Advanced Server Linux installations performed using the interactive installer for version 10 and earlier, the default is `/opt/edb/asx.x`.
+-   For EDB Postgres Advanced Server Linux installations performed using an RPM package, the default is `/usr/edb/asxx`.
+-   For EDB Postgres Advanced Server Windows installations, the default is `C:\Program Files\edb\asxx`. The product version number is represented by `x.x` or by `xx` for version 10 and later.

product_docs/docs/epas/14/epas_guide/01_introduction/03_examples_used.mdx

@@ -8,28 +8,22 @@ legacyRedirectsGenerated:
 
 <div id="examples_used" class="registered_link"></div>
 
-The examples in this guide are shown in the type and background illustrated below.
+The examples use the sample tables `dept`, `emp`, and `jobhist`, whcih are created and loaded when EDB Postgres Advanced Server is installed.
 
-Examples and output from examples are shown in fixed-width, white font on a black background.
-
-The examples use the sample tables, `dept, emp`, and `jobhist`, created and loaded when EDB Postgres Advanced Server is installed.
-
-The tables and programs in the sample database can be re-created at any time by executing the following script:
+You can re-create the tables and programs in the sample database at any time by executing the following script:
 
 ```text
 /usr/edb/asxx/share/pg-sample.sql
 ```
 
-where `xx` is the EDB Postgres Advanced Server version number.
-
-In addition there is a script in the same directory containing the database objects created using syntax compatible with Oracle databases. This script file is `edb-sample.sql`.
+Where `xx` is the EDB Postgres Advanced Server version number.
 
-The script:
+In addition, a script in the same directory contains the database objects created using syntax compatible with Oracle databases. This script file is `edb-sample.sql`. The script:
 
 -   Creates the sample tables and programs in the currently connected database.
 -   Grants all permissions on the tables to the `PUBLIC` group.
 
-The tables and programs are created in the first schema of the search path in which the current user has permission to create tables and procedures. You can display the search path by issuing the command:
+The tables and programs are created in the first schema of the search path in which the current user has permission to create tables and procedures. You can display the search path using the command:
 
 ```text
 SHOW SEARCH_PATH;
@@ -45,7 +39,7 @@ Each employee has an identification number, name, hire date, salary, and manager
 
 The sample company is regionally diverse, so it tracks the locations of its departments. Each company employee is assigned to a department. Each department is identified by a unique department number and a short name. Each department is associated with one location. All department-related information is stored in the `dept` table.
 
-The company also tracks information about jobs held by the employees. Some employees have been with the company for a long time and have held different positions, received raises, switched departments, etc. When a change in employee status occurs, the company records the end date of the former position. A new job record is added with the start date and the new job title, department, salary, and the reason for the status change. All employee history is maintained in the `jobhist` table.
+The company also tracks information about jobs held by the employees. Some employees have been with the company for a long time and have held different positions, received raises, switched departments, and so on. When a change in employee status occurs, the company records the end date of the former position. A new job record is added with the start date and the new job title, department, salary, and the reason for the status change. All employee history is maintained in the `jobhist` table.
 
 The following is the `pg-sample.sql` script:
 

product_docs/docs/epas/14/epas_guide/01_introduction/index.mdx

@@ -16,7 +16,7 @@ See the [release notes](../../epas_rel_notes) for the features added in EDB Post
 
 ## Hard limits
 
-The following table describes various hard limits of PostgreSQL. However, practical limits such as performance limitations or available disk space may apply before absolute hard limits are reached.
+The following table describes various hard limits of PostgreSQL. However, practical limits such as performance limitations or available disk space might apply before absolute hard limits are reached.
 
 | Item                     | Upper limit                                                           | Comment                                                                |
 | ------------------------ | --------------------------------------------------------------------- | ---------------------------------------------------------------------- |
@@ -33,6 +33,6 @@ The following table describes various hard limits of PostgreSQL. However, practi
 | `partition keys`         | 32                                                                    | can be increased by recompiling PostgreSQL                             |
 
 !!! Note
-    -   The maximum number of columns for a table is further reduced as the tuple being stored must fit in a single 8192-byte heap page. For example, excluding the tuple header, a tuple made up of 1600 `int` columns would consume 6400 bytes and could be stored in a heap page, but a tuple of 1600 `bigint` columns would consume 12800 bytes and would therefore not fit inside a heap page. Variable-length fields of types such as `text`, `varchar`, and `char` can have their values stored out of line in the table's `TOAST` table when the values are large enough to require it. Only an 18-byte pointer must remain inside the tuple in the table's heap. For shorter length variable-length fields, either a 4-byte or 1-byte field header is used and the value is stored inside the heap tuple.
+    -   The maximum number of columns for a table is further reduced as the tuple being stored must fit in a single 8192-byte heap page. For example, excluding the tuple header, a tuple made up of 1600 `int` columns consumes 6400 bytes and can be stored in a heap page. But a tuple of 1600 `bigint` columns consumes 12800 bytes and therefore doesn't fit inside a heap page. Variable-length fields of types such as `text`, `varchar`, and `char` can have their values stored out of line in the table's `TOAST` table when the values are large enough to require it. Only an 18-byte pointer must remain inside the tuple in the table's heap. For shorter length variable-length fields, either a 4-byte or 1-byte field header is used, and the value is stored inside the heap tuple.
 
-    -   Columns that have been dropped from the table also contribute to the maximum column limit. Moreover, although the dropped column values for newly created tuples are internally marked as null in the tuple's null bitmap, the null bitmap also occupies space.
+    -   Columns that were dropped from the table also contribute to the maximum column limit. Moreover, although the dropped column values for newly created tuples are internally marked as null in the tuple's null bitmap, the null bitmap also occupies space.