diff --git a/README.md b/README.md index 569ae835259..9a659fcd2f6 100644 --- a/README.md +++ b/README.md @@ -45,7 +45,7 @@ At this point you have a couple options. 1. Run `npm run start`. The application will start in the background and take a few minutes to load. -1. You can view logs and monitor the startup process by running `npm run logs`. Once it's finished it can be accessed at `http://localhost:8000/`. +1. You can view logs and monitor the startup process by running `npm run logs`. Once it's finished it can be accessed at [http://localhost:8000/](http://localhost:8000). #### Additional Commands and Options for the Docker Environment @@ -63,7 +63,7 @@ At this point you have a couple options. If you find that the container crashes frequently or see that your container has exited with code 137, increasing the Docker memory should help. Allocating at least 4GB is recommended. -1. open Docker Desktop +1. Open Docker Desktop 1. Go to Preferences (gear icon in the top right corner) @@ -283,7 +283,7 @@ If you need to setup a redirect from Docs 1.0 to Docs 2.0 manually, this is the # MDX Format -Documentation must be formatted as an [MDX file](https://www.gatsbyjs.com/docs/mdx/writing-pages/) with the `.mdx` extension. MDX is a superset of [Markdown](https://www.markdownguide.org/). +Documentation must be formatted as an [MDX file](https://www.gatsbyjs.com/docs/how-to/routing/mdx/) with the `.mdx` extension. MDX is a superset of [Markdown](https://www.markdownguide.org/). See [What is MDX?](https://mdxjs.com/docs/what-is-mdx/) for a detailed explanation of the format. ## Frontmatter diff --git a/advocacy_docs/community/contributing/index.mdx b/advocacy_docs/community/contributing/index.mdx index 7c09679cf3e..1144730282a 100644 --- a/advocacy_docs/community/contributing/index.mdx +++ b/advocacy_docs/community/contributing/index.mdx @@ -1,25 +1,27 @@ --- -title: We love feedback! -navTitle: Feedback +title: Contributing Feedback and More +navTitle: Contributing description: Guidelines for offering feedback to EDB Docs. iconName: IdeaSharing --- All feedback is welcome: -1. an idea for something new -2. you feel there's something missing -3. a mistake +Is it a simple edit for a typo? Use the **Suggest Edits** button and you can make a change to the docs which we'll review before including in the next docs update. -Github Issues is the fastest way to get that feedback in front of us. +If, on the other hand you: -[Open an issue on Github →](https://github.com/rocketinsights/edb_docs_advocacy/issues) +1. have an idea for something new +2. you feel there's something missing +3. you can see a mistake thats more than a typo ---- +Then Github Issues is the fastest way to get that feedback in front of us. -### Have code or content to contribute? +[Open an issue on Github →](https://github.com/EnterpriseDB/docs/issues) -The only things we love more than feedback are pull requests. Check out [the README on Github](https://github.com/EnterpriseDB/docs) to get started. +### Have code or content to contribute? +The only things we love more than feedback are pull requests. +Check out [the README on Github](https://github.com/EnterpriseDB/docs) to get started. diff --git a/advocacy_docs/community/contributing/repo.mdx b/advocacy_docs/community/contributing/repo.mdx index 879e228bd52..36c5d4ad8be 100644 --- a/advocacy_docs/community/contributing/repo.mdx +++ b/advocacy_docs/community/contributing/repo.mdx @@ -88,4 +88,4 @@ You'll make edits and additions via your IDE (VS Code). We recommend using [Gith ## Further reading -- [Format & Style](/community/contribute/style) +- [Format & Style](/community/contributing/styleguide) diff --git a/advocacy_docs/community/contributing/styleguide.mdx b/advocacy_docs/community/contributing/styleguide.mdx new file mode 100644 index 00000000000..6ea7ba2c3d9 --- /dev/null +++ b/advocacy_docs/community/contributing/styleguide.mdx @@ -0,0 +1,530 @@ +--- +title: Documentation Style Guide +navTitle: Documentation Style Guide +iconName: Docs +description: Our style guide to help you get your writing right +indexdepth: 3 +rootisheading: true +deepToC: true +--- + + +## Introduction + +EDB docs follow the 5 Cs of technical writing: + +* Clear + +* Correct + +* Concise + +* Complete + +* Consistent + + +Follow these guidelines to ensure consistency. + +Included in this guide: + +* 1 [Language and tone](#language-and-tone) + * 1.1 [Tense and voice](#tense-and-voice) + * 1.2 [Person](#person) + * 1.3 [Sentence length](#sentence-length) + * 1.4 [Contractions](#contractions) + * 1.5 [Latin abbreviations](#latin-abbreviations) + * 1.6 [Em-dashes and en-dashes](#em-dashes-and-en-dashes) + * 1.7 [Numbers](#numbers) +* 2 [Capitalization and punctuation](#capitalization-and-punctuation) +* 3 [Topic structure](#topic-structure) +* 4 [Verbiage](#verbiage) + * 4.1 [Future and conditional tenses](#future-and-conditional-tenses) + * 4.2 [Empty phrases](#empty-phrases) + * 4.3 [Weak sentence starters](#weak-sentence-starters) + * 4.4 [“This” without a noun](#this-without-a-noun) + * 4.5 [Misplaced modifiers](#misplaced-modifiers) + * 4.6 [Hyphen use](#hyphen-use) + * 4.6.1 [With a prefix](#with-a-prefix) + * 4.6.2 [With compound adjectives](#with-compound-adjectives) + * 4.7 [Directing users up and down through a topic](#directing-users-up-and-down-through-a-topic) + * 4.8 [Select versus click](#select-versus-click) +* 5 [Common errors/words to avoid](#common-errors/words-to-avoid) + * 5.1 [Login and log in](#login-and-log-in) + * 5.2 [Setup and set up](#setup-and-set-up) + * 5.3 [Words to avoid](#words-to-avoid) +* 6 [Headings](#headings) +* 7 [Font treatments](#font-treatments) + * 7.1 [Bold (\*\*text\*\*)](#bold-text)) + * 7.2 [Courier aka code or monospace ('text')](#courier-aka-code-or-monospace-text) + * 7.3 [Italics (*text*)](#italics-text) + * 7.4 [Underline](#underline) +* 8 [Links](#links) +* 9 [Admonitions: notes, tips, and warnings](#admonitions:-notes,-tips,-and-warnings) + * 9.1 [Notes](#notes) + * 9.2 [Tips](#tips) + * 9.3 [Warnings](#warnings) + * 9.4 [Code](#inlinextensionCode) + * 9.4.1 [Inline code](#inline-code) + * 9.4.2 [Code blocks](#code-blocks) +* 10 [Tables](#tables) + * 10.1 [Markdown](#markdown) +* 11 [Lists](#lists) +* 12 [Images](#images) +* 13 [Dates](#dates) + +## Language and tone + +EDB docs are helpful, humble, positive, and friendly. To achieve this, write topics that are factual and free of hyperbole and wordiness. + +Where possible, use active voice instead of passive. + +### Tense and voice + +For reference and general task-based docs, use the second-person [imperative present tense](https://en.wikipedia.org/wiki/Imperative_mood), also known as "imperative mood." These docs should be straightforward and conventional. + +**Example:** Use the following command to create a user: + +`CREATE USER john IDENTIFIED BY abc;`  + +For tutorials, the docs can be more casual and conversational but must also be straightforward and clear. + +**Example:** In this lab, start with a fresh cluster. Make sure to stop and clean up the cluster from the previous labs. + +### Person + +Use second person (you) when referring to the user. Don’t use “the user,” which is third person, unless you are talking about the customer’s user. + +Use first person plural (we) to refer to EDB. For example, use: + +We recommend that you restart your server. + +Instead of + +EDB recommends that you restart your server. + +However, don’t use first person plural when talking about how the software works or in an example. For example: + +Instead of: + +Next, we process the instruction. + +Use: + +Next, Barman processes the instruction. + +Instead of: + +Next, we enter the following the information: + +Use: + +Enter the following information: + +### Sentence length + +Use simple and direct language and keep your sentences short. Avoid combining sentences, which makes the content complicated. Maximum sentence length is 26 words when possible. + +### Contractions + +In keeping with the casual and friendly tone, use contractions. However, use common contractions (isn’t, can’t, don’t). Don't use contractions that are unclear or difficult to pronounce (there’ll). + +### Latin abbreviations + +Don’t use the Latin abbreviations i.e. and e.g. Use “that is” and “for example” instead. + +### Em-dashes and en-dashes + +Avoid using em-dashes to set off phrases within a sentence, which creates a complicated sentence structure and can be difficult to translate. You can use em-dashes for definition lists such as: + +* Autonomous — Use to create autonomous calls to the server. + + +Use spaces around em-dashes in a definition list. Otherwise, don't put spaces around em-dashes. + +To create an em-dash, use the character entity —. + +Use en-dashes to mean “through,” for example, items 1–10. Don’t use en-dashes otherwise. (There's only one other use of en-dashes that doesn’t typically come up in technical writing.). To create an en-dash, use the character entity –. + +### Numbers + +Spell out numbers zero through nine. Use digits for numbers 10 and greater. Spell out any number that starts a sentence. For this reason, avoid starting a sentence with a long or complex number. + +Capitalization and punctuation +------------------------------ + +Capitalization rules: + +* Use sentence-case for headings (including column headings in tables). + +* Capitalize the first letter in each list item except for function and command names that are naturally lower case + +* Capitalize link labels to match the case of the topic you're linking to. + +* Capitalize proper nouns and match the case of UI features: + + **Examples:** EDB, the Overview dashboard, the SQL Queries graph + +* Don’t capitalize the words that make up an initialization unless they're part of proper noun. For example, single sign-on is not a proper noun even though it is usually written as the initialism SSO. + + +Punctuation rules: + +* Avoid semicolons. Instead, use two sentences. + +* Don’t join related sentences using a comma. This syntax is incorrect. + +* Don't end headings with a period or colon + +* Use periods at the end of list items that are a sentence or that complete a sentence. If one item in a list uses a period, use a period for all the items in that list. + +* Use the [Oxford (a.k.a. serial) comma](https://en.wikipedia.org/wiki/Serial_comma). + + +Topic structure +--------------- + +* Procedure headings use gerunds, for example, _Modifying your cluster_. + +* Use a stem sentence to introduce a procedure only if multiple paragraphs of text fall between the head and the start of the procedure. The stem sentence helps to reorient the user when the heading might have scrolled of the screen. A stem sentence starts with “To” and ends with a colon: + To modify your cluster: + +* In general, include text between a heading and any subheadings. However, if such text is superfluous, a subhead can directly follow the head. + + +See also [Headings](https://enterprisedb.atlassian.net/wiki/spaces/DCBC/pages/2387870239/Documentation+Style+Guide#Headings). + +## Verbiage + +Use language that's precise and informative. + +### Future and conditional tenses + +Avoid future tense (will) and conditional tenses (would, could, should). These tenses lack precision and can create passive voice. You can use future tense when an action occurs in the future, for example, “This feature will be removed in a future release.” + +### Empty phrases + +Phrases like, “This section tells you about how to \[do something\]” are empty and don’t impart any real information. The title of the chapter or section tells you what the section is about. These phrases describe the documentation (documenting the documentation) rather than the product or user actions. + +Replace these empty phrases with wording that focuses on the product or process. So instead of: + +This chapter is divided into five sections. Each section tells you about part of the process. + +Write: + +To complete the process, perform these five steps: + +You can then link to each of the sections. + +### Weak sentence starters + +“There is” and “there are” are [weak sentence starters](http://www2.ensc.sfu.ca/~whitmore/courses/style/templates/sentence.html). Avoid starting sentences this way. + +### “This” without a noun + +Avoid using “this” without a noun following. Doing so can lead to ambiguity. For example, instead of: + +This happens when… + +Write: + +This error happens when… + +### Misplaced modifiers + +Make sure the word “only” precedes the word or expression you mean to modify. For example, instead of: + +This condition only happens after you select **Okay**. + +Write: + +This condition happens only after you select **Okay**. + +### Hyphen use + +#### With a prefix + +Don't use hyphens with prefixes such as re, non, multi, and pre unless needed for readability or to eliminate ambiguity. Often, when two vowels end up up together, a hyphen is needed, for example, multi-instance. However, preexisting is a legitimate word; don’t hyphenate it. Re-create (create again) requires a hyphen to avoid confusion with recreate (play). You can check many words using a spell checker. For example, nonexistent is not flagged by the spell checker. + +If you're unsure whether to include a hyphen, check with your editor or google the word without the hyphen + +#### With compound adjectives + +A compound adjective is formed when two words together describe a noun, for example, _red-bellied warbler_. Don’t use a hyphen when and adverb and a verb together describe a noun. The adverb describes the verb and doesn’t need a hyphen to create the relationship between the words. An example is _finely tuned settings_. + +### Directing users up and down through a topic + +Don’t use words like “below” and “above” to refer to previous and following sections. Link to the section instead. + +It also isn't necessary to use the words “the following” to refer to list items. These words are empty. So, for example, instead of: + +The palette includes the following colors: + +Write: + +The color palette includes: + +### Select versus click + +House style is to use “select” instead of “click” to allow for mobile-device use. + +Common errors/words to avoid +---------------------------- + +Avoid these common errors and wording issues. + +### Login and log in + +The verb form is “log in”: + +To log in to the system… + +The adjective form is “login”: + +At the login screen, enter your username. + +### Setup and set up + +The verb form is “set up”: + +To set up your environment… + +The noun form is “setup”: + +Check your setup for errors. + +### Words to avoid + +Don't use: + +* Please + +* Note that + +* In order to (just use “to”) + + +## Headings + +Use headings to create a hierarchy for readers to navigate to more easily find information. + +In Markdown, headings are denoted by number signs (`#`) followed by one space. Enter a line break between a heading and its content. EDB docs use Heading 2 (`##`), Heading 3 (`###`) and Heading 4 (`####`). Use Heading 4 sparingly. + +Heading 1 is reserved for page titles. You can denote anything below Heading 4 using bold text or other layout options. (Consider redesigning the material.) + +Examples: + +* `## This is heading 2` + +* `### This is heading 3` + +* `## Step 2. This is a step in a tutorial` + + +## Font treatments + +Don’t use any font treatments for: + +* Roles + +* User names (e.g. edb_admin) + +* Permissions + +* Window or dialog box names + + +### Bold (\*\*text\*\*) + +Use for UI elements. For menu items, include a greater-than sign: Select **File > Save**. + +### Courier aka code or monospace (`'text'`) + +Use for text entered in text boxes, parameters, commands, text in configuration files, and file paths. Don’t use for utility names. + +If you need to enter a `value in a field`, type the `ls` or `dd` command, add a setting to a `configuration=file` or just refer to `/etc/passwd`, then this is the font treatment to use. + +See [Code](#code) for more information. + +### Italics (*_text_*) + +Use for book titles and first instance of terms. Do not use Italics for keywords. + +### Underline + +Do not use underlined text in EDB docs. + +## Links + +Whenever an EDB feature is referenced, provide a link to the relevant documentation. For example, “BDR (Bi-Directional Replication) dashboards and probes to monitor status and activities for Admin, Nodes, and Groups. See [Monitoring BDR Nodes](http://localhost:8000/pem/latest/pem_ent_feat/17_monitoring_BDR_nodes/).” + +Avoid using the URL as the label. For example, + +**Best practice:** For information about the platforms and versions supported by PEM, see [Product Compatibility](https://www.enterprisedb.com/services-support/edb-supported-products-and-platforms) on the EnterpriseDB website**.** + +**Avoid:** For information about the platforms and versions supported by PEM, visit the EnterpriseDB website at: [https://www.enterprisedb.com/services-support/edb-supported-products-and-platforms](https://www.enterprisedb.com/services-support/edb-supported-products-and-platforms). + +You can also provide links to external resources, but only if the resource is vetted and no EDB documentation covers the topic. For example: “Information about managing authentication is also available in the [Postgres core documentation](https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html).” + +If you're referring to a guide on Docs 2.0, the label is the name of the guide and in italics. For example, “For information about modifying the `pg_hba.conf` file, see the [_PEM Administrator's Guide_](https://www.enterprisedb.com/docs/pem/latest/pem_admin/).” + +Link capitalization can be either title- or sentence-case: + +* **Use title-case** and _italics_ when referring to the linked doc by name. For example. “For information about modifying the `pg_hba.conf` file, see the [_PEM Administrator's Guide_](https://www.enterprisedb.com/docs/pem/latest/pem_admin/).”). + +* **Use sentence-case** when linking in the middle of a sentence. For example, “\[…\] follow the identifier rules when creating \[…\]“). + + +Addresses are relative. In these examples of links to topics, “folder” means the folder in the repo such as the product folder or the guide folder. For the destination topic, use the name of the file without the .mdx extension. If the destination includes a topic\_identifier (sub-section of a file), include the topic\_identifier prefixed with a # sign, such as in “/09\_controlling\_logging/#enabling_syslog.” + +| | | | | | +| --- | --- | --- | --- | --- | +| **Link type** | **Syntax** | **Example** | **Source path** | **Destination path** | + +| | | | | | +| --- | --- | --- | --- | --- | +| **Link type** | **Syntax** | **Example** | **Source path** | **Destination path** | +| Another topic in the same folder | `[here](file_name)` | `[Using the EFM Utility](07_using_efm_utility/#using_efm_utility)` | /efm/4.2/efm\_user/07\_using_efm.mdx | /efm/4.2/efm\_user/07\_using\_efm\_utility.mdx | +| Another topic in a different folder at the same level | `[here](../dest_folder_name/file_name)` | \[The ERD Tool\](../pem\_ent\_feat/04\_pem\_erd_tool/) | /pem/8/pem\_rel\_notes/08\_810\_rel_notes.mdx | /pem/8/pem\_ent\_feat04\_pem\_erd_tool/ | +| Another topic in a different folder at a different level | `[here](../../folder_name/file_name`) | \[Enabling syslog Log File Entries\](../../09\_controlling\_logging/#enabling_syslog) | /efm/4.2/efm\_user/04\_configuring\_efm/01\_cluster_properties/index.mdx | /efm/4.2/efm\_user/09\_controlling\_logging.mdx/enabling\_syslog | + +* To link to a specific heading on another page, use the name of the file plus the heading. + + **Example:** `[xyz](file_name#heading-on-page)` + +* To link to a specific heading on the current page, use just the heading. + + **Example:** `[xyz](#heading-on-page)` + +* To link to a specific location on a page that isn't a heading (for example, a specific command-line flag in a table), add a manual anchor and use the `id` parameter: + + **Example:** + + ``# Anchor: `--max-offset` # Link: [--max-offset](#flags-max-offset)`` + + +## Admonitions: notes, tips, and warnings + +Our docs currently use notes, tips, and warnings. + +See [https://github.com/EnterpriseDB/docs/blob/develop/README.md](https://github.com/EnterpriseDB/docs/blob/develop/README.md) for more information on admonitions. + +For multiple, consecutive admonitions, use separate admonitions. If there are more than two consecutive admonitions, consider adding a subsection called **Additional notes** or **Additional information**. Admonitions can contain bullets and code, but consider instead adding a subsection (or whether an admonition is the appropriate mechanism) to keep the formatting simple. + +### Notes + +Use notes to call attention to a piece of clarifying information. This information isn't crucial to accomplishing the task in the document. + +For example, you might use a note to let users know that the `DELETE` command deletes only rows and that to delete columns you must use `ALTER TABLE`. This information helps to clarify the command's purpose and point users to the right place. + +### Tips + +Use for indicating a new version added in a particular release when working in the major version of the documentation for products that are adhering to semantic versioning. See the PEM documentation for examples. Also can use for information that might improve productivity. + +### Warnings + +Use warning to express that a piece of information is critical to preventing unexpected things from happening. + +For example, you might include a warning that using `CASCADE` in `DROP INDEX` drops dependent objects without warning. This is critical to prevent users from unexpectedly losing constraints or additional indexes. + +## Code + +Code can be shown inline or as a code block. + +### Inline code + +Inline `code` has `back-ticks (``) around` it and is used when referring to code, commands, or other technical syntax within a sentence. + +Example: The `CREATE TABLE` statement creates a new table in a database. + +### Code blocks + +Code blocks provide executable code samples, marked with an opening and closing set of three backticks (` ``` `). Code blocks can support syntax highlighting if you add the language name immediately after the first line of backticks. Use one returned line before and after a code block for better Markdown readability. For example: + +`This is a sample line of text. ``` {% include copy-clipboard.html %} ~~~shell $ go get -u github.com/lib/pq ~~~ ``` This is more sample text.` + +Use syntax highlighting for configuration file , shell, and SQL commands, where appropriate, as follows. + +**Shell code samples** + +Start shell code samples with ` ```shell` followed by a line break. Use the terminal marker `$` as the first character of the next line. For multi-line shell commands, use a backslash (`\`) at the end of each line to indicate a line break. + +**SQL code samples** + +SQL code samples are broken into two sections: commands and responses. + +* **Commands** (e.g., `SELECT`, `CREATE TABLE`) begin with ` ```sql` followed by a line break. The first character of the next line should be the terminal marker `>`. Capitalize commands properly. Use only one command per code sample. + +* **Responses** (e.g., retrieved tables) add (_ _ 0UTPUT _ _) on a line between the command and the output, you'll get highlights for the code but not the output. For example, + + ` + ```sql SELECT slot_name, slot_type, database, active FROM pg_replication_slots ORDER BY 1; __OUTPUT__ slot_name | slot_type | database | active -------------+-----------+-----------+-------- xdb_47877_5 | logical | MMRnode_a | t xdb_47878_5 | logical | MMRnode_b | t xdb_47879_5 | logical | MMRnode_c | t (3 rows) ``` ` + +``` +sql SELECT slot_name, slot_type, database, active FROM pg_replication_slots ORDER BY 1; __OUTPUT__ slot_name | slot_type | database | active -------------+-----------+-----------+-------- xdb_47877_5 | logical | MMRnode_a | t xdb_47878_5 | logical | MMRnode_b | t xdb_47879_5 | logical | MMRnode_c | t (3 rows) +``` + + +**Configuration file samples** + +For files that have key-value pairs use ` ```ini`. For example: + +` ```ini promotable=false auto.reconfigure=false ``` ` + +Tables +------ + +Use tables to display structured information in an easy-to-read format. There are two types of tables we use: Markdown and HTML. + +## Markdown + +If table formatting can be kept simple (e.g., basic text formatting and using `
` tags for paragraph breaks), create a table using Markdown. This is the preferred table format. + +To create a table, use pipes (`|`) between columns and at least 3 dashes (`-`) separating the header cells from the body cells. A return denotes the start of the next row. The text within each column does not need to align in order to be rendered correctly, and you can inline Markdown or HTML. + +We don’t use outer pipes. + +Example: + +``` +Term | Description | Example ----------|-----------------------------|---------------- `term_1` | This is a description. | `3.14` `term_2` | This is also a description. | `"lola mcdog"` +``` + +## Lists + +EDB docs uses two types of lists: + +* **Numbered** (ordered) — Use to list information that should appear in order, like tutorial steps. + + **Bulleted** (unordered) — Use to list related information in an easy-to-read way. + + Introduce lists with a sentence and a colon. Use periods at the end of list items if it is a sentence or completes a sentence. + + +For each item of a **numbered list**, use `1.` followed by a period and a space, for example,`1. This is a numbered list`. Markdown renders the steps in the correct order. + +For each item of a **bulleted list**, use one dash followed by one space to denote a list item, e.g., `- This is a bulleted list`. + +## Images + +Use images to clarify a topic, but use them only as needed. Images are either: + +* **Screenshots** — Provide a UI visual. Don’t use to show dialog boxes and parts of the UI a user can see for themselves, as these are hard to maintain and don’t provide useful information. If a screenshot needs an annotation, use a red box. + +* **Diagrams** — Provide a visual of a complicated theory. Diagrams must be simple and easy to read. + + +**Syntax:** + +! \[Alternate\_text\](<path\_to\_image\_file>/<image_filename.png>) + +**Example:** + +`![PEM Architecture](../images/pem_architecture.png)` + +## Dates + +When specifying dates for human readability, use the DD mmm YYYY format with a short month name in English. Where the date is being used in a column in a table, use a leading 0 on the day of month, e.g. 01 Jan 2024, for easier alignment. + +When specifying dates as solely numbers, use [ISO8601](https://www.iso.org/iso-8601-date-and-time-format.html) format; YYYY/MM/DD. This is the internationally accepted, disambiguous format and should be used where you may expect the date to be read by automated systems. + diff --git a/advocacy_docs/community/index.mdx b/advocacy_docs/community/index.mdx new file mode 100644 index 00000000000..6d5c00feeab --- /dev/null +++ b/advocacy_docs/community/index.mdx @@ -0,0 +1,12 @@ +--- +title: Community +navTitle: Community +description: The EDB Docs Community +iconName: IdeaSharing +--- + +All guides, notes and documentation for anyone working in the community of EDB documenters. + +* [Contributing Documentation](contributing) + + diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx index 9ec0f28b705..d6abe7d2c7b 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx @@ -1,6 +1,6 @@ --- title: 'Partner information' -description: 'Details for Commvault Backup & Recovery' +description: 'Details of the Partner' --- |   |   | @@ -8,5 +8,5 @@ description: 'Details for Commvault Backup & Recovery' | **Partner Name** | Commvault | | **Partner product** | Commvault Backup & Recovery | | **Website** | https://www.commvault.com/ | -| **Version** | Commvault Backup & Recovery 11.24 | -| **Product description** | Wherever your data resides, ensure availability by way of a single interface with Commvault Backup & Recovery. It offers domprehensive workload coverage, files, apps, and databases, including EDB Postgres Advanced Server and EDB Postgres Extended Server, from a single extensible platform and user interface. Commvault Backup & Recovery provides a comprehensive backup and archiving solution for your trusted recovery, ransomware protection, and security. | +| **Version** | Commvault Backup & Recovery 11.32 | +| **Product description** | Wherever your data resides, ensure availability by way of a single interface with Commvault Backup & Recovery. It offers domprehensive workload coverage, files, apps, and databases, including EDB Postgres Advanced Server, EDB Postgres Extended Server and PostgreSQL, from a single extensible platform and user interface. Commvault Backup & Recovery provides a comprehensive backup and archiving solution for your trusted recovery, ransomware protection, and security. | diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx index 4c81ede5ab6..0839f8fc321 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/03-SolutionSummary.mdx @@ -1,6 +1,6 @@ --- title: 'Solution summary' -description: 'Brief explanation of the solution and its purpose' +description: 'Explanation of the solution and its purpose' --- Commvault enables your business to streamline management of its continuously evolving data environment, whether the data is on premises or in the cloud. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx index 5e629a4d158..db7372a2446 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/04-ConfiguringCommvaultBackupandRecovery.mdx @@ -1,24 +1,27 @@ --- title: 'Configuring' -description: 'Walkthrough of configuring Commvault Backup & Recovery' +description: 'Walkthrough of configuring the integration' redirects: - /partner_docs/CommVaultGuide/04-ConfiguringCommvaultBackupandRecovery/ --- -Implementing Commvault Backup & Recovery with an EDB database requires the following components: +Implementing Commvault Backup & Recovery with an EDB Postgres Advanced Server, EDB Postgres Extended Server or PostgreSQL Server database requires the following components: -- EDB Postgres Advanced Server or EDB Postgres Extended Server +- EDB Postgres Advanced Server, EDB Postgres Extended Server or PostgreSQL Server - Commvault Backup & Recovery software +!!! Note + We refer to the EDB Postgres Advanced Server, EDB Postgres Extended Server, and PostgreSQL Server products as Postgres distribution. The specific distribution type depends on your needs and preferences. + ## Prerequisites -- A running EDB Postgres Advanced Server or EDB Postgres Extended Server instance +- A running Postgres distribution - Commvault Backup & Recovery installed -- EDB Postgres Advanced Server or EDB Postgres Extended Server application path and library directory path, for example, `c:\Program Files\edb\as13\bin` and `c:\Program Files\edb\as13\lib` -- The login credentials used to access the EDB Postgres Advanced Server or EDB Postgres Extended Server database -- EDB Postgres Advanced Server or EDB Postgres Extended Server archive log directory configured +- Postgres distribution application path and library directory path, for example, `c:\Program Files\edb\as15\bin` and `c:\Program Files\edb\as15\lib` +- The login credentials used to access the Postgres distribution database +- Postgres distribution archive log directory configured -## Configure Commvault Backup & Recovery for EDB Postgres Advanced Server or EDB Postgres Extended Server +## Configure Commvault Backup & Recovery for Postgres distribution ### Set up a disk storage pool @@ -42,11 +45,11 @@ Next, create a server backup plan in Core Setup. To create a server backup plan ![Creating a Server Backup Plan in Core Setup](Images/BackupPlanConf.png) -### Install a client on an EDB database +### Install a client on a Postgres distribution database 1. From the Navigation pane of the Commvault Backup & Recovery's Command Center, select **Protect > Databases**. 2. Select **Add server**. -3. Select the database type for EDB database, which in this case is **PostgreSQL**. +3. Select the database type for the Postgres distribution database, which in this case is **PostgreSQL**. ![Creating a Server Backup Plan in Core Setup](Images/ServerAdd1.png) @@ -66,7 +69,7 @@ Next, create a server backup plan in Core Setup. To create a server backup plan ![Creating a Server Backup Plan in Core Setup](Images/ServerAdd6.png) -### Configure the EDB database instances to back up and protect +### Configure the Postgres distribution instances to backup and protect 1. From the navigation pane, select **Protect > Databases > DB Instances**. 2. Select **Add instance**, and then select **PostgreSQL**. @@ -74,18 +77,18 @@ Next, create a server backup plan in Core Setup. To create a server backup plan ![Creating a Server Backup Plan in Core Setup](Images/CreateInstance1.png) 3. From the **Server name** list, select the server where you want to create the new instance. -4. In the **Instance Name** box, enter the EDB database instance name. -5. From the **Plan** list, select the server plan you set up for use with your EDB database. +4. In the **Instance Name** box, enter the Postgres distribution database instance name. +5. From the **Plan** list, select the server plan you set up for use with your Postgres distribution database. 6. Under **Connection details**, enter the following information. - - In the **Database user** box, enter the user name to access the EDB database instance. - - In the **Password** box, enter the EDB database user account password. - - In the **Port** box, enter the port to open the communication between the EDB database and the clients. + - In the **Database user** box, enter the user name to access the Postgres distribution database instance. + - In the **Password** box, enter the Postgres distribution database user account password. + - In the **Port** box, enter the port to open the communication between the Postgres distribution and the clients. - In the **Maintenance DB** box, enter the name of a system database that's used as a maintenance database. - In the **PostgreSQL** section, enter paths for **Binary Directory**, **Lib Directory**, and **Archive Log Directory**. ![Creating a Server Backup Plan in Core Setup](Images/CreateInstance2.png) - Your database instance to back up is now created. You can view its configuration. + Your Postgres distribution database instance to back up is now created. You can view its configuration. ![Creating a Server Backup Plan in Core Setup](Images/CreateInstance3.png) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx index e24f6da2ed0..876a5d237cf 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/05-UsingCommvaultBackupandRecovery.mdx @@ -1,27 +1,25 @@ --- title: 'Using' -description: 'Walkthroughs of multiple Commvault Backup & Recovery usage scenarios' -redirects: - - /partner_docs/CommVaultGuide/05-UsingCommvaultBackupandRecovery/ +description: 'Walkthrough of example usage scenarios' --- -You can back up and restore an EDB database using Commvault Backup & Recovery. +You can back up and restore a Postgres distribution database using Commvault Backup & Recovery. ## Using Commvault Backup & Recovery -Commvault provides two methods of taking the backup from an EDB database and restoring it: +Commvault provides two methods of taking the backup from a Postgres distribution database and restoring it: - DumpBasedBackupSet backup and restore - FSBasedBackupSet backup and restore !!! Note - At this time there's a known issue with FSBased Restore that doesn't allow for proper restoration of the database. See [Known issues](#known-issues) for more information. + At this time there is a known issue with FSBased Incremental/PITR Restore that does not allow for proper restoration of the database using the defined process. See the known issues section of the guide for more information and workaround. -### DumpBasedBackupSet backup and restore +### DumpBasedBackupSet Backup and Restore Dump-based backup uses the pg_dump utility to take the backup. -#### Taking DumpBasedBackupSet backup +## Taking DumpBasedBackupSet backup 1. Open the Commvault Backup & Recovery's Command Center. From the navigation pane, select **Protect > Databases**. @@ -53,7 +51,7 @@ Dump-based backup uses the pg_dump utility to take the backup. ![Backup Job](Images/Dumpbackup7.png) -#### Restoring DumpBasedBackupSet backup +## Restoring DumpBasedBackupSet backup You can use DumpBasedBackupSet to restore the individual databases. @@ -79,7 +77,7 @@ You can use DumpBasedBackupSet to restore the individual databases. ![Restore Job](Images/Dumprestore5.png) -8. When the Restore has completed successfully, log in to the EDB database and check that the restore operation recovered the data. This example connected to an EDB Postgres Advanced Server instance: +8. When the Restore has completed successfully, log in to the Postgres distribution database and check that the restore operation recovered the data. This example connected to an EDB Postgres Advanced Server instance: ```bash edb=# @@ -160,5 +158,74 @@ epas13_test=# ``` -## Known issues -FSBaseBackupSet restore has an issue if the default edb directory, for example, `*:\Program files\edb`, was lost or deleted. If this occurs, then after a restore is performed, the permissions on the restored directories aren't recovered. Instead, the directory inherits the permissions from the parent directory, which doesn't allow EDB Postgres Advanced Server services to start on the restored directory. We're working with Commvault to resolve the issue. +### FSBasedBackupSet Backup and Restore +A file system backup backs up data that resides on a Windows or UNIX computer. + +## Taking FSBasedBackupSet Backup +1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to **Protect > Databases**. + +2. Click on the required instance. + +3. In the **Backup sets** section, click on **FSBasedBackupSet** backup set. + +4. In the **Database groups** section, click the database group that you want to back up. In this case it is **default**. + +5. In the **Backup** section, click **Back up**. + +6. Choose between a Full or Incremental backup in the **Select Backup Level** screen, this example chose an incremental backup. + + ![Select FSBased Backup Type](Images/SelectFSBasedBackupType.png) + +7. A job will be created to take the backup, which you can view by clicking on the **Job ID** for that backup. + + ![FSBased Backup Job](Images/FSBasedBackupJob.png) + +8. When the job is complete, the information about the job can be found on the job's page. + + ![FSBased Backup Job Details](Images/FSBasedBackupJobDetails.png) + +## Restoring FSBasedBackupSet Full Backup +Backed up data can be restored for a subclient or an entire backup set with either an in-place restore, out-of-place restore or for a Linux file server to a standalone file server. + +1. Ensure that your Postgres distribution instance is stopped. + +2. Delete or rename the WAL directory and data directory. + +3. From the Commvault navigation pane, go to **Protect > Databases**. + +4. Click the instance you want to restore. + +5. In the **Recovery Points** calender, select **FSBasedBackupSet**. + +6. Select a date where a full FSBasedBackupSet was taken and click **Restore**. + +7. The **Backup Content** screen will display the databases to be restored, select the required database to restore or select all of them to restore all. + + ![FSBased Backup Restore Databases](Images/FSBasedFullRestoreDatabases.png) + +8. Click **Restore**. + +9. From the **Restore Options** screen, select where you want the restore to complete, in-place, out-of-place or restore to disk for a Linux server. + + ![FSBased Backup Restore Details](Images/FSBasedFullRestoreOptions.png) + +10. Select the **Destination Server** and **Destination Instance** and click on submit. + +11. A Job will be created to restore the backup. + +12. When the Restore has completed successfully, Commvault will automatically start the server using the pg_ctl utility. + +13. You can check that the server was started successfully with a command like, `"C:\Program Files\edb\as15\bin\pg_ctl" -U enterprisedb status -D "C:\Program Files\edb\as15\data"` and it should return a message that the server is running. + +```bash +C:\Program Files\edb\as15>"C:\Program Files\edb\as15\bin\pg_ctl" -U enterprisedb status -D "C:\Program Files\edb\as15\data" +pg_ctl: server is running (PID: 20896) +C:/Program Files/edb/as15/bin/edb-postgres.exe "-D" "C:\Program Files\edb\as15\data" +``` + +14. If you would like the server to be controlled by a Services utility you will need to stop it with the pg_ctl utility and start it again in your Services utility, for example Services(Local) in Windows or systemctl in UNIX. + +15. After you have started the service with your utility of choice, login to your EDB database and check that the restore operation recovered the data. + +## Known Issues +FSBaseBackupSet Incremental or Point-In-Time(PITR) Restore has issues with PostgreSQL server, EDB Postgres Advanced Server and EDB Postgres Extended versions 13 and onward. The behavior is due to a change that was made in Postgres version 13. From the release notes, `Generate an error if recovery does not reach the specified recovery target`. While Commvault does provide a time target for the recovery, the recovery is performed entirely by Postgres and Postgres does not know how to reach that time target, therefore it fails. This can happen when there are no transactions between backup jobs. A workaround for this solution is to always introduce a transaction scenario, such as a create and drop database, before doing a log backup. Another workaround is to use `recovery_target_lsn` in the postgresql.conf file instead of uisng `recovery_target_time`. Commvault is aware of this error on their side and is working on a fix. diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx index 5624b0b1107..772fe4e5b5c 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/06-CertificationEnvironment.mdx @@ -1,11 +1,11 @@ --- title: 'Certification environment' -description: 'Overview of the certification environment used in the certification of Commvault Backup & Recovery' +description: 'Overview of the certification environment' --- |   |   | | ----------- | ----------- | -| **Certification test date** | June 16, 2022 | -| **EDB Postgres Advanced Server** | 11, 12, 13, 14 | -| **EDB Postgres Extended Server** | 11, 12, 13 | -| **Commvault Backup & Recovery** | 11.24 | +| **Certification Test Date** | August 22, 2023 | +| **EDB Postgres Advanced Server** | 12, 13, 14, 15 | +| **EDB Postgres Extended Server** | 12, 13 | +| **Commvault Backup & Recovery** | 11.32 | diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx new file mode 100644 index 00000000000..303d6c2bb43 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx @@ -0,0 +1,42 @@ +--- +title: 'Support and Logging Details' +description: 'Details of the support process and logging information' +--- + +## Support + +Technical support for the use of these products is provided by both EDB and Commvault. A proper support contract is required to be in place at both EDB and Commvault. A support ticket can be opened on either side to start the process. If it is determined through the support ticket that resources from the other vendor is required, the customer should open a support ticket with that vendor through normal support channels. This will allow both companies to work together to help the customer as needed. + +## Logging + +**EDB Postgres Advanced Server Logs:** + +Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance and from here you can navigate to `log`, `current_logfiles` or you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs. + +**EDB Postgres Extended Server Logs** + +Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance and from here you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options. An example of the full path to view EDB Postgres Extended logs: `/var/lib/edb-pge/15/data/log`. + +**PostgreSQL Server Logs** + +The default log directories for PostgreSQL logs vary depending on the operating system: + +- Debian-based system: `/var/log/postgresql/postgresql-x.x.main.log. X.x.` + +- Red Hat-based system: `/var/lib/pgsql/data/pg_log` + +- Windows: `C:\Program Files\PostgreSQL\9.3\data\pg_log` + +** Commvault Logs** + +Commvault logs can be found a few ways. A first way is within the Content Store directory/folder in the Commvault folder on your system. For example if on a Windows system the Log File path would be `C:\Program Files\Commvault\ContentStore\LogFiles` where you can then see all of the differnt types of logs Commvault collects. + +You can also gather some job specific logs within the Commvault interface. + +1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to `Jobs > Job History`. + +2. Find the specific job you would like to view logs for and click on the `...` beside that job. + +3. Select `View Logs`. + + ![View Job Logs](Images/CommvaultViewLogsForJob.png) diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/CommvaultViewLogsForJob.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/CommvaultViewLogsForJob.png new file mode 100644 index 00000000000..ed1093daafa --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/CommvaultViewLogsForJob.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db6a73932cd532dad2bef06a09ba99f4e7c8184ae74ce204e2fab6747e270333 +size 1146108 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJob.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJob.png new file mode 100644 index 00000000000..e4995df8065 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJob.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d43db9e5db0f0b0421541273f52d87736ae12e6879aee84bc8700a568d105691 +size 129298 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJobDetails.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJobDetails.png new file mode 100644 index 00000000000..2676007aa44 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedBackupJobDetails.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5da67b5742886735b8f41fc1c46f4d67483a70f405eb4f80c2e5b0740a6e7c9a +size 140432 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreDatabases.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreDatabases.png new file mode 100644 index 00000000000..e537f6ca6af --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreDatabases.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:913d3eb2f127a84517ddab7039323da6ff2ac3eb67ec05a84a94cb993c40f6bf +size 87505 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreOptions.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreOptions.png new file mode 100644 index 00000000000..ae4a2a7023d --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/FSBasedFullRestoreOptions.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2827c237d4db8cb80a94b996c367c34e26df54a0d9447b1334055bf9ca04791 +size 755537 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/SelectFSBasedBackupType.png b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/SelectFSBasedBackupType.png new file mode 100644 index 00000000000..5f3f1924352 --- /dev/null +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/Images/SelectFSBasedBackupType.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68bc5a3f22590ee1e7068157679cb258506d757aa1f8cf6c14a1431925c2593c +size 117372 diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx index c4c8905d918..87c365f7f4b 100644 --- a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx +++ b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/index.mdx @@ -9,3 +9,5 @@ directoryDefaults:

EDB GlobalConnect Technology Partner Implementation Guide

Commvault Backup & Recovery

+ +

This document is intended to augment each vendor’s product documentation to guide you in getting the products working together. It isn't intended to show the optimal configuration for the certified integration.

\ No newline at end of file diff --git a/advocacy_docs/pg_extensions/advanced_storage_pack/rel_notes/index.mdx b/advocacy_docs/pg_extensions/advanced_storage_pack/rel_notes/index.mdx index 8dcbf2d9680..1802a3e9ad8 100644 --- a/advocacy_docs/pg_extensions/advanced_storage_pack/rel_notes/index.mdx +++ b/advocacy_docs/pg_extensions/advanced_storage_pack/rel_notes/index.mdx @@ -11,7 +11,7 @@ about the release that introduced the feature. | Version | Release Date | | --------------------------- | ------------ | -| [1.0.0](asp_1.0.0_rel_notes) | 2022 Nov 30 | +| [1.0.0](asp_1.0.0_rel_notes) | 30 Nov 2022 | diff --git a/advocacy_docs/pg_extensions/ldap_sync/rel_notes/index.mdx b/advocacy_docs/pg_extensions/ldap_sync/rel_notes/index.mdx index 8d55874c4a2..363bad1651c 100644 --- a/advocacy_docs/pg_extensions/ldap_sync/rel_notes/index.mdx +++ b/advocacy_docs/pg_extensions/ldap_sync/rel_notes/index.mdx @@ -11,7 +11,7 @@ about the release that introduced the feature. | Version | Release Date | | --------------------------- | ------------ | -| [1.0.0](ldap_sync_1.0.0_rel_notes) | 2022 Nov 30 | +| [1.0.0](ldap_sync_1.0.0_rel_notes) | 30 Nov 2022 | 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 52e15d35198..4d6373b08ca 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 @@ -11,7 +11,7 @@ about the release that introduced the feature. | Version | Release Date | | --------------------------- | ------------ | -| [1.0.0](pg_failover_slots_1.0.0_rel_notes) | 2023 Mar 31 | +| [1.0.0](pg_failover_slots_1.0.0_rel_notes) | 31 Mar 2023 | diff --git a/advocacy_docs/pg_extensions/pg_tuner/rel_notes/index.mdx b/advocacy_docs/pg_extensions/pg_tuner/rel_notes/index.mdx index 0669deef032..1fcdf91696d 100644 --- a/advocacy_docs/pg_extensions/pg_tuner/rel_notes/index.mdx +++ b/advocacy_docs/pg_extensions/pg_tuner/rel_notes/index.mdx @@ -14,8 +14,8 @@ about the release that introduced the feature. | Version | Release Date | | --------------------------- | ------------ | -| [1.1.0](pg_tuner_1.1.0_rel_notes) | 2023 Feb 10 | -| [1.0.0](pg_tuner_1.0.0_rel_notes) | 2022 Nov 30 | +| [1.1.0](pg_tuner_1.1.0_rel_notes) | 10 Feb 2023 | +| [1.0.0](pg_tuner_1.0.0_rel_notes) | 30 Nov 2022 | diff --git a/advocacy_docs/pg_extensions/query_advisor/rel_notes/index.mdx b/advocacy_docs/pg_extensions/query_advisor/rel_notes/index.mdx index 8560ac96b8e..2cb1d75b6c1 100644 --- a/advocacy_docs/pg_extensions/query_advisor/rel_notes/index.mdx +++ b/advocacy_docs/pg_extensions/query_advisor/rel_notes/index.mdx @@ -11,7 +11,7 @@ about the release that introduced the feature. | Version | Release Date | | --------------------------- | ------------ | -| [1.0.0](query_advisor_1.0.0_rel_notes) | 2023 May 10 | +| [1.0.0](query_advisor_1.0.0_rel_notes) | 10 May 2023 | diff --git a/docs/agreements/product-version-fork.md b/docs/agreements/product-version-fork.md new file mode 100644 index 00000000000..e27b3b9cf6c --- /dev/null +++ b/docs/agreements/product-version-fork.md @@ -0,0 +1,108 @@ +# Docs repository product version forking strategy + +## Version forking in brief + +"Forking" is currently (and traditionally) our strategy for handling product versions in the documentation for EDB products. In short, "forking" means that when a new (major) version of a product is released, a new set of documentation is released along with it, based on the documentation for the previous version but with updates to reflect the changes present in the new version of the product. + +For example: when EDB Postgres Advanced Server 14 was released, a new version of the documentation was created in this repo at product_docs/docs/epas/14/ - this was based on the documentation at product_docs/docs/epas/13/, but contains several key differences. + +There are other strategies for handling product versioning in documentation, but forking is the one we've used for most of EDB's history. Of particular interest is the contrast with the approach used by PGDG for the PostgreSQL documentation, which maintains a branch for each major release that can be updated both independently and also allows for backporting corrections from the latest release into past versions. + +## The problems with forked versions + +There are quite a few tradeoffs between various versioning strategies for documentation, but our current approach suffers from two major flaws: + +1. **It is difficult to share concurrent changes between versions.** There are many cases where a change should be made to documentation for more than one product version: + +- Errors present in more than one version should ideally be corrected in all of them. +- Structural changes made to facilitate navigation or comprehension should be applied consistently. +- Updates to the product itself in one version will likely need to be noted for subsequent versions as well if they affect how the product can be used. In many cases, a minor version update will be backported to previous versions of a product and such changes should also be reflected in the documentation. +- Work must begin on a new version's documentation while major updates are still expected for the last version's documentation; in some cases, documentation for new features in one version will not be complete before the documentation must be forked. + +In all of these cases, changes must be manually copied from one subtree to another. While there are tools to make this somewhat easier, it remains a tedious and error-prone process. + +2. **Past version control history is lost when files are copied**. Technically, git does offer copy detection... But it is slow and doesn't always work. By default, tools like `git log` and `git blame` don't use it. Thus, practically speaking, it is difficult to trace back to the origin of a change after a file has been forked. Over multiple releases, the context for most changes slowly disappears from view - thus negating much of the value of using source control! + +The forking strategy outlined below _partially_ mitigates these problems. + +## Our forking strategy + +We recognize that the critical period for changes comes between the time when work has started on documentation for the next major version of a product and the time when that version has been released. During this period, work is split between the two versions - the current latest (_vLatest_) and the yet-to-be-released next version (_vNext_). Prior to the start of this period, most work on product documentation will focus on _vLatest_; after the end of this period, _vNext_ has **become** _vLatest_ and work continues to focus primarily on _vLatest_. + +Therefore, our strategy aims to minimize unnecessary differences between the two sets of documentation. + +### Initializing the branch + +When work is begun on the next version of a product, [a long-lived future release documentation branch](branch-and-release.md#future-release-documentation) should be created. All changes _specific to the next version_ should be made in this branch (either directly, or via PRs that are merged into it). Changes that apply to both _vLatest_ and _vNext_ should be made to _vLatest_ - once merged, the _vNext_ branch can be rebased to incorporate them. For this to be possible, the branch should be initialized by **renaming** the _vNext_ subdirectory and then **restoring** the current _vNext_ subdirectory prior to merging - essentially a variation on [Robert Pollak's technique for tracking copies](https://stackoverflow.com/questions/1043388/record-file-copy-operation-with-git/46484848#46484848), with an extended delay between steps \#2 and \#3 where all the work happens. + +1. Create the new branch +2. _Rename_ the subdirectory corresponding to the latest version of the product to reflect the new version. (e.g., `git mv product_docs/docs/epas/14/ product_docs/docs/epas/15/`) +3. Commit the version rename to the branch and push to the docs repo. (e.g., `git commit -m "begin fork of epas 15 docs"`) +4. Create a PR for the branch in which you note the purpose and provide instructions as follows (replace all placeholders that appear in square brackets): + + > # Documentation for [Product] [vNext] + > + > This is a future release branch - specific instructions must be followed when merging, [see below](#merging-this-branch). + > **This branch shall not be merged until [Product] [vNext] is released!** + > + > Please use this branch _only_ for changes specific to version [vNext] - + > changes and corrections that apply to [vLatest] should be made in short-lived + > branches that can be merged into develop and released promptly. + > + > ## Working on this branch + > + > Other people may be editing and altering this branch. Be sure to pull latest before + > beginning work - and be aware that this branch may be rebased on a regular basis to + > incorporate changes from the previous version. We recommend using `git pull --rebase` or + > setting `pull.rebase` to `true` in git config to avoid mistakes, + > e.g. run `git config pull.rebase true` on your local clone. + > + > This branch will live for months, but try to merge and delete your branches within hours or days. + > + > For changes that need review or feedback, create a branch based on this branch and + > request feedback on a PR before merging your changes into this branch. See: + > + > Please use descriptive messages and comments for your commits and PRs - this allows + > other people working on this PR to see at a glance what is changing. + > + > Good: "updated version to 15 in index.mdx" / "correct misspelled option in CLI reference" + > Bad: "updated index.mdx" / "fixed typos" + > + > ## Incorporating [vLatest] updates + > + > To bring in applicable changes that have been made to [Product] [vLatest], rebase + > this branch against develop and force-push. Be sure to review changes for areas + > that should be updated for [vNext]. When resolving conflicts, defer to [vLatest] + > except when changes in this branch are necessary to support [vNext]. + > + > ## Merging this branch + > + > When [Product] [vNext] is released, follow this procedure to complete the separation of + > documenation for [vLatest] and [vNext]: + > + > 1. Rebase one last time (see above) + > 2. Bring the [vLatest] subdirectory back into the source tree: + > ``` + > git checkout develop product_docs/docs/[product]/[vLatest]/ + > git commit -m "restore [product] [vLatest] docs" + > git push + > ``` + > 3. Immediately merge this branch into develop. + +5. Ensure all contributors are made aware of the branch and have read the instructions for use. + +### Merging the branch + +When the time comes to merge, follow the instructions noted in the template above: + +1. Rebase the branch - this ensures that the _vNext_ changes are built on top of the most up-to-date _vLatest_ changes and avoids conflicts when merging. +2. Restore the latest version files by checking them out from the most recent develop branch commit and then committing them on the future branch. + This ensures that no changes are lost, as when the future branch is merged all unincorporated commits for _vLatest_ will be merged into _vNext_. +3. Merge the branch without delay after step \#2 - any interim commits to _vLatest_ will be lost (from the _vLatest_ directory). + +## The downsides of our mitigation + +The biggest downside is simply that it only works _before_ the next version of documentation is released - after that, we're back to having to patch each version independently. + +A smaller downside is the inability to work on both _vLatest_ and _vNext_ in the same branch. We should try to avoid that anyway, +but it is sometimes useful. diff --git a/docs/agreements/release-notes-guidelines.md b/docs/agreements/release-notes-guidelines.md index 73bedfef8f1..9a8d80482f4 100644 --- a/docs/agreements/release-notes-guidelines.md +++ b/docs/agreements/release-notes-guidelines.md @@ -1,6 +1,28 @@ -# Guidelines for wording release notes +# Guidelines for release notes -## General guidelines +## Structural guidelines + +Release notes start with the name of the product, the version number being released and the words "release notes". +This should be the setting for the frontmatter title field. The frontmatter will also need a short navigation title +(navTitle). This should just be the version number, preceded by the word "Version". + +This is followed, in the body of the content, by a date of release in the `Released: DD mmm YYYY` format: + +``` +--- +title: EDB Postgres Advanced Server 64.0 release notes +navTitle: Version 64.0 +--- + +Released: 1 Jan 2024 + +``` + +If the release notes are substantially updated after release, add an `Updated: DD mmm YYYY` line, or update any existing `Updated:` line. + +## Guidelines for wording release notes + +### General guidelines - For features and enhancements, use second person (you) instead of third person (the user). - For bug fixes, avoid referring to the user. Instead, describe the software behavior. If the description is clearer by referring to the user, use third person. @@ -10,11 +32,11 @@ - Use contractions. - Use serial (aka Oxford) commas. -## Phrasing guidelines for enhancements +### Phrasing guidelines for enhancements You can use either of the forms described in the following sections for enhancements. Add as much detail as needed to convey the relevance of the enhancement. If you need to describe how the product worked before, use “previously,” not “currently.” -### Past tense description of the development work +#### Past tense description of the development work Start with a past-tense word that describes what you did. Then provide any relevant detail. @@ -24,7 +46,7 @@ Examples: - Added the ability to copy probes and alerts to all servers in a group without having to select them individually. - Enabled multi-insert support for the dynamic partition for EDB*Loader and COPY command. -### “Now” phrase +#### “Now” phrase Describe what the product does now as a result of the enhancement, generally in the form: The *product/feature* now *does the new behavior*. @@ -32,7 +54,7 @@ Examples: - EDB Postgres Advanced Server now provides INDEX and NO_INDEX hints for the partitioned table. The optimizer hints apply to the inherited index in the partitioned table. The execution plan internally expands to include the corresponding inherited child indexes and applies them in later processing. - The INTO clause now accepts multiple composite row type targets in SPL. This enhancement allows you to assign a SELECT list having a mix of scalar and composite type values that are fetched from a table to corresponding scalar or composite variables (including collection variables) in the SPL code. -### Enhancement don’ts +#### Enhancement don’ts Don’t start the enhancement with a gerund, which suggests the work is still in progress: - **Correct**: Added the XYZ function. @@ -44,7 +66,7 @@ Don’t use a title or short description: - **Correct**: You can now configure the durability options, such as Group Commit, CAMO, Eager Replication, and Lag Control, through Commit Scope. - **Incorrect**: Unified replication durability configuration - The durability options such as Group Commit, CAMO, Eager Replication, or Lag Control are now all configured through Commit Scope configuration. -## Bug fix writing guidelines +### Bug fix writing guidelines Start bug fix descriptions with: - Fixed an issue whereby… diff --git a/product_docs/docs/biganimal/release/free_trial/detail/experiment/import_data.mdx b/product_docs/docs/biganimal/release/free_trial/detail/experiment/import_data.mdx index fbc00dbd960..fea2f96b028 100644 --- a/product_docs/docs/biganimal/release/free_trial/detail/experiment/import_data.mdx +++ b/product_docs/docs/biganimal/release/free_trial/detail/experiment/import_data.mdx @@ -7,7 +7,7 @@ PostgreSQL includes a variety of ways to import data. Here, we'll show how to im For this demonstration, we're going to import batter data from the [Baseball Databank](https://github.com/chadwickbureau/baseballdatabank), which is in CSV form. While it's easy to import the data using [PostgreSQL's COPY command](https://www.postgresql.org/docs/current/sql-copy.html), we'll need to first define a table to put that data into. -We're going to [add a database](/biganimal/latest/using_cluster/01_postgres_access/#one-database-with-one-application) called "baseball," which we'll populate with some Major League Baseball statistics. +We're going to add a database called "baseball," which we'll populate with some Major League Baseball statistics. ```sql create database baseball; diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index b46c2d00abd..a866f5b2a69 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -278,139 +278,6 @@ To restore a deleted cluster, use the `--from-deleted` flag in the command. You can restore a cluster in a single cluster to a primary/standby high-availability cluster and vice versa. You can restore a distributed high-availability cluster only to a cluster using the same architecture. !!! -### Get cluster connection information - -To use your BigAnimal cluster, you first need to get your cluster's connection information. To get your cluster's connection information, use the `cluster show-connection` command: - -```shell -biganimal cluster show-connection \ - --name "my-biganimal-cluster" \ - --provider "azure" \ - --region "eastus" -__OUTPUT__ -┌─────────────┬──────────────────────────────────────────────────────────────────────────────────────────┐ -│ Access Type │ Connection String │ -├─────────────┼──────────────────────────────────────────────────────────────────────────────────────────┤ -│ read-write │ postgresql://edb_admin@p-gxhkfww1fe.30glixgayvwhtmn3.enterprisedb.network:5432/edb_admin │ -│ read-only │ Disabled │ -└─────────────┴──────────────────────────────────────────────────────────────────────────────────────────┘ -``` - -!!!tip -You can query the complete connection information with other output formats, like JSON or YAML. For example: - -```shell -biganimal cluster show-connection \ - --name "my-biganimal-cluster" \ - --provider "azure" \ - --region "eastus" \ - --output "json" -``` -!!! - -### Update cluster - -After the cluster is created, you can update attributes of the cluster, including both the cluster’s profile and its deployment architecture. You can update the following attributes: - -- Cluster name -- Password of administrator account -- Cluster architecture -- Number of standby replicas -- Instance type of cluster -- Instance volume properties -- Networking -- Allowed IP list -- Postgres database configuration -- Volume properties, size, IOPS -- Retention period -- Read-only workloads -- IAM authentication - -For example, to set the public allowed IP range list, use the `--cidr-blocks` flag: - -```shell -./biganimal cluster update --name "my-biganimal-cluster" --provider "azure" \ - --region "eastus" \ - --cidr-blocks "9.9.9.9/28=Traffic from App A" -``` - -To check whether the setting took effect, use the `cluster show` command, and view the detailed cluster information output in JSON format. For example: - -```shell -biganimal cluster show --name "my-biganimal-cluster" --provider "azure" \ - --region "eastus" \ - --output "json" \ -| jq '.[0].allowIpRangeMap' -__OUTPUT__ -[ - [ - "9.9.9.9/28", - "Traffic from App A" - ] -] -``` - -### Update the Postgres configuration of a cluster - -To update the Postgres configuration of a BigAnimal cluster directly from the CLI: - -```shell -biganimal cluster update --id "p-gxhkfww1fe" \ - --pg-config "application_name=ba_test_app,array_nulls=false" -__OUTPUT__ -Update Cluster operation is started -Cluster ID is "p-gxhkfww1fe" -``` -To specify multiple configurations, you can use multiple `--pg-config` flags or include multiple configuration settings as a key-value array string separated by commas in one `--pg-config` flag. If a Postgres setting contains a comma, you need to specify it with a separate `--pg-config` flag. - -!!! Note -You can update the cluster architecture with the `--cluster-architecture` flag. The only supported scenario is to update a single-node cluster to a primary/standby high-availability cluster. -!!! - -### Delete a cluster - -To delete a cluster you no longer need, use the `cluster delete` command. For example: - -```shell -biganimal cluster delete \ - --name "my-biganimal-cluster" \ - --provider "azure" \ - --region "eastus" -``` - -You can list all deleted clusters using the `show-deleted-clusters` command and restore them from their history backups as needed. - - -### Restore a cluster -BigAnimal continuously backs up your PostgreSQL clusters. Using the CLI, you can restore a cluster from its backup to any point in time as long as the backups are retained in the backup storage. The restored cluster can be in another region and with different configurations. You can specify new configurations in the `cluster restore` command. For example: - -```shell -biganimal cluster restore\ - --name "my-biganimal-cluster" \ - --provider "azure" \ - --region "eastus" \ - --password "mypassword@123" \ - --new-name "my-biganimal-cluster-restored" \ - --new-region="eastus2" \ - --cluster-architecture "single" \ - --instance-type "azure:Standard_E2s_v3" \ - --volume-type "azurepremiumstorage" \ - --volume-property "P1" \ - --networking "public" \ - --cidr-blocks="10.10.10.10/27=Traffic from App B" \ - --restore-point "2022-01-26T15:04:05+0800" \ - --backup-retention-period "2w" \ - --read-only-workloads: "true" -``` - -The password for the restored cluster is mandatory. The other parameters, if not specified, inherit the source database's settings. - -To restore a deleted cluster, use the `--from-deleted` flag in the command. - -!!! Note -You can restore a cluster in a single cluster to a primary/standby high-availability cluster and vice versa. You can restore a distributed high-availability cluster only to a cluster using the same architecture. -!!! - ## Managing distributed high-availability clusters diff --git a/product_docs/docs/edb_plus/41/02_release_notes/index.mdx b/product_docs/docs/edb_plus/41/02_release_notes/index.mdx index dac25ecd895..5269d7c8505 100644 --- a/product_docs/docs/edb_plus/41/02_release_notes/index.mdx +++ b/product_docs/docs/edb_plus/41/02_release_notes/index.mdx @@ -13,6 +13,6 @@ The EDB\*Plus documentation describes the latest version of EDB\*Plus Version 41 | Version | Release Date | | ------------------------------------- | ------------ | -| [41.2.0](edbplus_41.2_rel_notes.mdx) | 2023 Aug 23 | -| [41.1.0](edbplus_41.1_rel_notes.mdx) | 2023 Apr 20 | -| [41.0.0](edbplus_41.0_rel_notes.mdx) | 2023 Feb 14 | +| [41.2.0](edbplus_41.2_rel_notes.mdx) | 23 Aug 2023 | +| [41.1.0](edbplus_41.1_rel_notes.mdx) | 20 Apr 2023 | +| [41.0.0](edbplus_41.0_rel_notes.mdx) | 14 Feb 2023 | diff --git a/product_docs/docs/efm/4/efm_rel_notes/index.mdx b/product_docs/docs/efm/4/efm_rel_notes/index.mdx index f63a2e6ede6..6eb796f3255 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/index.mdx +++ b/product_docs/docs/efm/4/efm_rel_notes/index.mdx @@ -9,14 +9,14 @@ about the release that introduced the feature. | Version | Release Date | | ------- | ------------ | -| [4.7](03_efm_47_rel_notes) | 2023 Jun 20 | -| [4.6](04_efm_46_rel_notes) | 2023 Feb 14 | -| [4.5](05_efm_45_rel_notes) | 2022 Aug 30 | -| [4.4](06_efm_44_rel_notes) | 2022 Jan 5 | -| [4.3](07_efm_43_rel_notes) | 2021 Dec 18| -| [4.2](08_efm_42_rel_notes) | 2021 Apr 19| -| [4.1](09_efm_41_rel_notes) | 2021 Dec 11 | -| [4.0](10_efm_40_rel_notes) | 2021 Sep 2 | +| [4.7](03_efm_47_rel_notes) | 20 Jun 2023| +| [4.6](04_efm_46_rel_notes) | 14 Feb 2023| +| [4.5](05_efm_45_rel_notes) | 30 Aug 2022| +| [4.4](06_efm_44_rel_notes) | 05 Jan 2022| +| [4.3](07_efm_43_rel_notes) | 18 Dec 2021| +| [4.2](08_efm_42_rel_notes) | 19 Apr 2021 | +| [4.1](09_efm_41_rel_notes) | 11 Dec 2021| +| [4.0](10_efm_40_rel_notes) | 02 Sep 2021 | diff --git a/product_docs/docs/epas/11/epas_rel_notes/index.mdx b/product_docs/docs/epas/11/epas_rel_notes/index.mdx index 1cab0645dad..b321278359f 100644 --- a/product_docs/docs/epas/11/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/11/epas_rel_notes/index.mdx @@ -24,26 +24,26 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merge | | ------- | ------------ | -------------- | -| [11.21.32](epas11_21_32_rel_notes.mdx) | 2023 Aug 21 | [11.21](https://www.postgresql.org/docs/11/release-11-21.html) | -| [11.20.31](epas11_20_31_rel_notes.mdx) | 2023 May 11 | [11.20](https://www.postgresql.org/docs/11/release-11-20.html) | -| [11.19.30](epas11_19_30_rel_notes.mdx) | 2023 Feb 10 | [11.19](https://www.postgresql.org/docs/11/release-11-19.html) | -| [11.18.29](epas11_18_29_rel_notes.mdx) | 2022 Nov 10 | [11.18](https://www.postgresql.org/docs/11/release-11-18.html) | -| [11.17.28](epas11_17_28_rel_notes.mdx) | 2022 Aug 11 | [11.17](https://www.postgresql.org/docs/11/release-11-17.html) | -| [11.16.26](epas11_16_26_rel_notes.mdx) | 2022 May 12 | [11.16](https://www.postgresql.org/docs/11/release-11-16.html) | -| [11.15.25](09_epas11.15.25_rel_notes.mdx) | 2022 Feb 10 | [11.15](https://www.postgresql.org/docs/11/release-11-15.html) | -| [11.14.24](10_epas11.14.24_rel_notes.mdx) | 2021 Nov 11 | [11.14](https://www.postgresql.org/docs/11/release-11-14.html) | -| [11.13.23](11_epas11.13.23_rel_notes.mdx) | 2021 Sep 08 | [11.13](https://www.postgresql.org/docs/11/release-11-13.html) | -| [11.12.22](13_epas11.12.22_rel_notes.mdx) | 2021 May 05 | [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | -| [11.12.21](15_epas11.12.21_rel_notes.mdx) | 2021 Apr 15 | [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | -| [11.11.20](17_epas11.11.20_rel_notes.mdx) | 2021 Feb 12 | [11.11](https://www.postgresql.org/docs/11/release-11-11.html) | -| [11.10.19](19_epas11.10.19_rel_notes.mdx) | 2020 Nov 20 | [11.10](https://www.postgresql.org/docs/11/release-11-10.html) | -| [11.9.17](21_epas11.9.17_rel_notes.mdx) | 2020 Aug 18 | [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | -| [11.9.16](23_epas11.9.16_rel_notes.mdx) | 2020 Aug 17 | [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | -| [11.8.15](25_epas11.8.15_rel_notes.mdx) | 2020 May 18 | [11.8](https://www.postgresql.org/docs/11/release-11-8.html) | -| [11.7.14](27_epas11.7.14_rel_notes.mdx) | 2020 Feb 14 | [11.7](https://www.postgresql.org/docs/11/release-11-7.html) | -| [11.6.13](29_epas11.6.13_rel_notes.mdx) | 2019 Nov 19 | [11.6](https://www.postgresql.org/docs/11/release-11-6.html) | -| [11.5.12](31_epas11.5.12_rel_notes.mdx) | 2019 Aug 26 | [11.5](https://www.postgresql.org/docs/11/release-11-5.html) | -| [11.4.11](33_epas11.4.11_rel_notes.mdx) | 2019 Jun 25 | [11.4](https://www.postgresql.org/docs/11/release-11-4.html) | -| [11.3.10](35_epas11.3.10_rel_notes.mdx) | 2019 May 13 | [11.3](https://www.postgresql.org/docs/11/release-11-3.html) | -| [11.2.9](37_epas11.2.9_rel_notes.mdx) | 2019 Feb 22 | [11.2](https://www.postgresql.org/docs/11/release-11-2.html) | -| [11.1.7](39_epas11.1.7_rel_notes.mdx) | 2018 Nov 28 | [11.1](https://www.postgresql.org/docs/11/release-11-1.html) | \ No newline at end of file +| [11.21.32](epas11_21_32_rel_notes.mdx) | 21 Aug 2023 | [11.21](https://www.postgresql.org/docs/11/release-11-21.html) | +| [11.20.31](epas11_20_31_rel_notes.mdx) | 11 May 2023 | [11.20](https://www.postgresql.org/docs/11/release-11-20.html) | +| [11.19.30](epas11_19_30_rel_notes.mdx) | 10 Feb 2023 | [11.19](https://www.postgresql.org/docs/11/release-11-19.html) | +| [11.18.29](epas11_18_29_rel_notes.mdx) | 10 Nov 2022 | [11.18](https://www.postgresql.org/docs/11/release-11-18.html) | +| [11.17.28](epas11_17_28_rel_notes.mdx) | 11 Aug 2022 | [11.17](https://www.postgresql.org/docs/11/release-11-17.html) | +| [11.16.26](epas11_16_26_rel_notes.mdx) | 12 May 2022 | [11.16](https://www.postgresql.org/docs/11/release-11-16.html) | +| [11.15.25](09_epas11.15.25_rel_notes.mdx) | 10 Feb 2022 | [11.15](https://www.postgresql.org/docs/11/release-11-15.html) | +| [11.14.24](10_epas11.14.24_rel_notes.mdx) | 11 Nov 2021| [11.14](https://www.postgresql.org/docs/11/release-11-14.html) | +| [11.13.23](11_epas11.13.23_rel_notes.mdx) | 08 Sep 2021| [11.13](https://www.postgresql.org/docs/11/release-11-13.html) | +| [11.12.22](13_epas11.12.22_rel_notes.mdx) | 05 May 2021| [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | +| [11.12.21](15_epas11.12.21_rel_notes.mdx) | 15 Apr 2021| [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | +| [11.11.20](17_epas11.11.20_rel_notes.mdx) | 12 Feb 2021| [11.11](https://www.postgresql.org/docs/11/release-11-11.html) | +| [11.10.19](19_epas11.10.19_rel_notes.mdx) | 20 Nov 2020| [11.10](https://www.postgresql.org/docs/11/release-11-10.html) | +| [11.9.17](21_epas11.9.17_rel_notes.mdx) | 18 Aug 2020| [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | +| [11.9.16](23_epas11.9.16_rel_notes.mdx) | 17 Aug 2020| [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | +| [11.8.15](25_epas11.8.15_rel_notes.mdx) | 18 May 2020| [11.8](https://www.postgresql.org/docs/11/release-11-8.html) | +| [11.7.14](27_epas11.7.14_rel_notes.mdx) | 14 Feb 2020| [11.7](https://www.postgresql.org/docs/11/release-11-7.html) | +| [11.6.13](29_epas11.6.13_rel_notes.mdx) | 19 Nov 2019| [11.6](https://www.postgresql.org/docs/11/release-11-6.html) | +| [11.5.12](31_epas11.5.12_rel_notes.mdx) | 26 Aug 2019| [11.5](https://www.postgresql.org/docs/11/release-11-5.html) | +| [11.4.11](33_epas11.4.11_rel_notes.mdx) | 25 Jun 2019| [11.4](https://www.postgresql.org/docs/11/release-11-4.html) | +| [11.3.10](35_epas11.3.10_rel_notes.mdx) | 13 May 2019| [11.3](https://www.postgresql.org/docs/11/release-11-3.html) | +| [11.2.9](37_epas11.2.9_rel_notes.mdx) | 22 Feb 2019| [11.2](https://www.postgresql.org/docs/11/release-11-2.html) | +| [11.1.7](39_epas11.1.7_rel_notes.mdx) | 28 Nov 2018| [11.1](https://www.postgresql.org/docs/11/release-11-1.html) | \ No newline at end of file diff --git a/product_docs/docs/epas/12/epas_rel_notes/index.mdx b/product_docs/docs/epas/12/epas_rel_notes/index.mdx index 9261a7af773..2c30ddf4612 100644 --- a/product_docs/docs/epas/12/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/12/epas_rel_notes/index.mdx @@ -27,20 +27,20 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merges | | ------- | ------------ | --------------- | -| [12.16.20](epas12_16_20_rel_notes.mdx) | 2023 Aug 21 | [12.16](https://www.postgresql.org/docs/12/release-12-16.html) -| [12.15.19](epas12_15_19_rel_notes.mdx) | 2023 May 11 | [12.15](https://www.postgresql.org/docs/12/release-12-15.html) | -| [12.14.18](epas12_14_18_rel_notes.mdx) | 2023 Feb 10 | [12.14](https://www.postgresql.org/docs/12/release-12-14.html) | -| [12.13.17](epas12_13_17_rel_notes.mdx) | 2022 Nov 10 | [12.13](https://www.postgresql.org/docs/12/release-12-13.html) | -| [12.12.16](epas12_12_16_rel_notes.mdx) | 2022 Aug 11 | [12.12](https://www.postgresql.org/docs/12/release-12-12.html) | -| [12.11.15](epas12_11_15_rel_notes.mdx) | 2022 May 12 | [12.11](https://www.postgresql.org/docs/12/release-12-11.html) | -| [12.10.14](05_epas12.10.14_rel_notes.mdx) | 2022 Feb 10 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | | [12.10.14](05_epas12.10.14_rel_notes.mdx) | 2022 Feb 10 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | -| [12.9.13](06_epas12.9.13_rel_notes.mdx) | 2021 Nov 11 | [12.9](https://www.postgresql.org/docs/12/release-12-9.html) | -| [12.8.12](07_epas12.8.12_rel_notes.mdx) | 2021 Sep 28 | [12.8](https://www.postgresql.org/docs/12/release-12-8.html) | -| [12.7.10](08_epas12.7.10_rel_notes.mdx) | 2021 May 25 | [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | -| [12.7](09_epas12.7_rel_notes.mdx) | 2021 May 14 | [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | -| [12.6.7](10_epas12.6.7_rel_notes.mdx) | 2021 Feb 12 | [12.6](https://www.postgresql.org/docs/12/release-12-6.html) | -| [12.5.6](11_epas12.5.6_rel_notes.mdx) | 2020 Nov 20 | [12.5](https://www.postgresql.org/docs/12/release-12-5.html) | -| [12.4.5](13_epas12.4.5_rel_notes.mdx) | 2020 Aug 17 | [12.4](https://www.postgresql.org/docs/12/release-12-4.html) | -| [12.3.4](15_epas12.3.4_rel_notes.mdx) | 2020 May 18 | [12.3](https://www.postgresql.org/docs/12/release-12-3.html) | -| [12.2.3](17_epas12.2.3_rel_notes.mdx) | 2020 Feb 14 | [12.2](https://www.postgresql.org/docs/12/release-12-2.html) | -| [12.1.2](19_epas12.1.2_rel_notes.mdx) | 2019 Dec 10 | [12.0](https://www.postgresql.org/docs/12/release-12.html) | \ No newline at end of file +| [12.16.20](epas12_16_20_rel_notes.mdx) | 21 Aug 2023 | [12.16](https://www.postgresql.org/docs/12/release-12-16.html) +| [12.15.19](epas12_15_19_rel_notes.mdx) | 11 May 2023 | [12.15](https://www.postgresql.org/docs/12/release-12-15.html) | +| [12.14.18](epas12_14_18_rel_notes.mdx) | 10 Feb 2023 | [12.14](https://www.postgresql.org/docs/12/release-12-14.html) | +| [12.13.17](epas12_13_17_rel_notes.mdx) | 10 Nov 2022 | [12.13](https://www.postgresql.org/docs/12/release-12-13.html) | +| [12.12.16](epas12_12_16_rel_notes.mdx) | 11 Aug 2022 | [12.12](https://www.postgresql.org/docs/12/release-12-12.html) | +| [12.11.15](epas12_11_15_rel_notes.mdx) | 12 May 2022 | [12.11](https://www.postgresql.org/docs/12/release-12-11.html) | +| [12.10.14](05_epas12.10.14_rel_notes.mdx) | 10 Feb 2022 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | | [12.10.14](05_epas12.10.14_rel_notes.mdx) | 10 Feb 2022 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | +| [12.9.13](06_epas12.9.13_rel_notes.mdx) | 11 Nov 2021| [12.9](https://www.postgresql.org/docs/12/release-12-9.html) | +| [12.8.12](07_epas12.8.12_rel_notes.mdx) | 28 Sep 2021| [12.8](https://www.postgresql.org/docs/12/release-12-8.html) | +| [12.7.10](08_epas12.7.10_rel_notes.mdx) | 25 May 2021| [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | +| [12.7](09_epas12.7_rel_notes.mdx) | 14 May 2021| [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | +| [12.6.7](10_epas12.6.7_rel_notes.mdx) | 12 Feb 2021| [12.6](https://www.postgresql.org/docs/12/release-12-6.html) | +| [12.5.6](11_epas12.5.6_rel_notes.mdx) | 20 Nov 2020| [12.5](https://www.postgresql.org/docs/12/release-12-5.html) | +| [12.4.5](13_epas12.4.5_rel_notes.mdx) | 17 Aug 2020| [12.4](https://www.postgresql.org/docs/12/release-12-4.html) | +| [12.3.4](15_epas12.3.4_rel_notes.mdx) | 18 May 2020| [12.3](https://www.postgresql.org/docs/12/release-12-3.html) | +| [12.2.3](17_epas12.2.3_rel_notes.mdx) | 14 Feb 2020| [12.2](https://www.postgresql.org/docs/12/release-12-2.html) | +| [12.1.2](19_epas12.1.2_rel_notes.mdx) | 10 Dec 2019| [12.0](https://www.postgresql.org/docs/12/release-12.html) | \ No newline at end of file diff --git a/product_docs/docs/epas/13/epas_rel_notes/index.mdx b/product_docs/docs/epas/13/epas_rel_notes/index.mdx index eb487d41638..e0a3eb281bd 100644 --- a/product_docs/docs/epas/13/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/13/epas_rel_notes/index.mdx @@ -20,16 +20,16 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merges | | ------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------- | -| [13.12.17](epas13_12_17_rel_notes) | 2023 Aug 21 | [13.12](https://www.postgresql.org/docs/release/13.12/) | -| [13.11.15](epas13_11_15_rel_notes) | 2023 May 11 | [13.11](https://www.postgresql.org/docs/release/13.11/) | -| [13.10.14](epas13_10_14_rel_notes) | 2023 Feb 10 | [13.10](https://www.postgresql.org/docs/release/13.10/) | -| [13.9.13](epas13_9_13_rel_notes) | 2022 Nov 10 | [13.9](https://www.postgresql.org/docs/release/13.9/) | -| [13.8.12](epas13_8_12_rel_notes) | 2022 Aug 11 | [13.8](https://www.postgresql.org/docs/release/13.8/) | -| [13.7.11](epas13_7_11_rel_notes) | 2022 May 23 | [13.7](https://www.postgresql.org/docs/release/13.7/) -| [13.6.10](13_epas13.6.10_rel_notes) | 2022 Feb 10 | [13.6](https://www.postgresql.org/docs/13/release-13-6.html) | -| [13.5.9](14_epas13.5.9_rel_notes) | 2021 Nov 11 | [13.5](https://www.postgresql.org/docs/13/release-13-5.html) | -| [13.4.8](15_epas13.4.8_rel_notes) | 2021 Sep 28 | [13.4](https://www.postgresql.org/docs/13/release-13-4.html) | -| [13.3.7](16_epas13.3.7_rel_notes) | 2021 May 25 | NA | -| [13.3.6](17_epas13.3.6_rel_notes) | 2021 May 14 | [13.3](https://www.postgresql.org/docs/13/release-13-3.html) | -| [13.2.5](19_epas13.2.5_rel_notes) | 2021 Feb 02 | [13.2](https://www.postgresql.org/docs/13/release-13-2.html) | -| [13.1.4](20_epas13_rel_notes) | 2020 Dec 12 | [13](https://www.postgresql.org/docs/13/release-13.html), [13.1](https://www.postgresql.org/docs/13/release-13-1.html) | \ No newline at end of file +| [13.12.17](epas13_12_17_rel_notes) | 21 Aug 2023 | [13.12](https://www.postgresql.org/docs/release/13.12/) | +| [13.11.15](epas13_11_15_rel_notes) | 11 May 2023 | [13.11](https://www.postgresql.org/docs/release/13.11/) | +| [13.10.14](epas13_10_14_rel_notes) | 10 Feb 2023 | [13.10](https://www.postgresql.org/docs/release/13.10/) | +| [13.9.13](epas13_9_13_rel_notes) | 10 Nov 2022 | [13.9](https://www.postgresql.org/docs/release/13.9/) | +| [13.8.12](epas13_8_12_rel_notes) | 11 Aug 2022 | [13.8](https://www.postgresql.org/docs/release/13.8/) | +| [13.7.11](epas13_7_11_rel_notes) | 23 May 2022 | [13.7](https://www.postgresql.org/docs/release/13.7/) +| [13.6.10](13_epas13.6.10_rel_notes) | 10 Feb 2022 | [13.6](https://www.postgresql.org/docs/13/release-13-6.html) | +| [13.5.9](14_epas13.5.9_rel_notes) | 11 Nov 2021 | [13.5](https://www.postgresql.org/docs/13/release-13-5.html) | +| [13.4.8](15_epas13.4.8_rel_notes) | 28 Sep 2021 | [13.4](https://www.postgresql.org/docs/13/release-13-4.html) | +| [13.3.7](16_epas13.3.7_rel_notes) | 25 May 2021 | NA | +| [13.3.6](17_epas13.3.6_rel_notes) | 14 May 2021 | [13.3](https://www.postgresql.org/docs/13/release-13-3.html) | +| [13.2.5](19_epas13.2.5_rel_notes) | 02 Feb 2021 | [13.2](https://www.postgresql.org/docs/13/release-13-2.html) | +| [13.1.4](20_epas13_rel_notes) | 12 Dec 2020 | [13](https://www.postgresql.org/docs/13/release-13.html), [13.1](https://www.postgresql.org/docs/13/release-13-1.html) | \ No newline at end of file diff --git a/product_docs/docs/epas/14/epas_rel_notes/index.mdx b/product_docs/docs/epas/14/epas_rel_notes/index.mdx index 3fdff1905c9..a11ad85cf6e 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/index.mdx @@ -19,15 +19,15 @@ The EDB Postgres Advanced Server (EDB Postgres Advanced Server) documentation de | Version | Release date | Upstream merges | | ------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------- | -| [14.9.0](epas14_9_0_rel_notes) | 2023 Aug 21 | [14.9](https://www.postgresql.org/docs/14/release-14-9.html) | -| [14.8.0](epas14_8_0_rel_notes) | 2023 May 11 | [14.8](https://www.postgresql.org/docs/14/release-14-8.html) | -| [14.7.0](epas14_7_0_rel_notes) | 2023 Feb 10 | [14.7](https://www.postgresql.org/docs/14/release-14-7.html) | -| [14.6.0](epas14_6_0_rel_notes) | 2022 Nov 10 | [14.6](https://www.postgresql.org/docs/14/release-14-6.html) | -| [14.5.0](epas14_5_0_rel_notes) | 2022 Aug 11 | [14.5](https://www.postgresql.org/docs/14/release-14-5.html) | -| [14.4.0](epas14_4_0_rel_notes) | 2022 Jun 16 | [14.4](https://www.postgresql.org/docs/14/release-14-4.html) | -| [14.3.0](epas14_3_0_rel_notes) | 2022 May 12 | [14.3](https://www.postgresql.org/docs/14/release-14-3.html) | -| [14.2.1](19_epas14.2.1_rel_notes) | 2022 Feb 10 | [14.2](https://www.postgresql.org/docs/14/release-14-2.html) | -| [14.1.0](20_epas14_rel_notes) | 2021 Dec 01 | [14.0](https://www.postgresql.org/docs/14/release-14.html), [14.1](https://www.postgresql.org/docs/14/release-14-1.html) | +| [14.9.0](epas14_9_0_rel_notes) | 21 Aug 2023 | [14.9](https://www.postgresql.org/docs/14/release-14-9.html) | +| [14.8.0](epas14_8_0_rel_notes) | 11 May 2023 | [14.8](https://www.postgresql.org/docs/14/release-14-8.html) | +| [14.7.0](epas14_7_0_rel_notes) | 10 Feb 2023 | [14.7](https://www.postgresql.org/docs/14/release-14-7.html) | +| [14.6.0](epas14_6_0_rel_notes) | 10 Nov 2022 | [14.6](https://www.postgresql.org/docs/14/release-14-6.html) | +| [14.5.0](epas14_5_0_rel_notes) | 11 Aug 2022 | [14.5](https://www.postgresql.org/docs/14/release-14-5.html) | +| [14.4.0](epas14_4_0_rel_notes) | 16 Jun 2022 | [14.4](https://www.postgresql.org/docs/14/release-14-4.html) | +| [14.3.0](epas14_3_0_rel_notes) | 12 May 2022 | [14.3](https://www.postgresql.org/docs/14/release-14-3.html) | +| [14.2.1](19_epas14.2.1_rel_notes) | 10 Feb 2022 | [14.2](https://www.postgresql.org/docs/14/release-14-2.html) | +| [14.1.0](20_epas14_rel_notes) | 01 Dec 2021 | [14.0](https://www.postgresql.org/docs/14/release-14.html), [14.1](https://www.postgresql.org/docs/14/release-14-1.html) | ## Support announcements diff --git a/product_docs/docs/epas/15/epas_rel_notes/index.mdx b/product_docs/docs/epas/15/epas_rel_notes/index.mdx index 039dd690f8c..6739f08a0e5 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/index.mdx @@ -13,9 +13,9 @@ The EDB Postgres Advanced Server documentation describes the latest version of E | Version | Release date | Upstream merges | | ------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [15.4.0](epas15_4_0_rel_notes) | 2023 Aug 21 | [15.4](https://www.postgresql.org/docs/release/15.4/) -| [15.3.0](epas15_3_0_rel_notes) | 2023 May 11 | [15.3](https://www.postgresql.org/docs/release/15.3/) | -| [15.2.0](epas15_2_0_rel_notes) | 2023 Feb 14 | [15.0](https://www.postgresql.org/docs/release/15.0/), [15.1](https://www.postgresql.org/docs/release/15.1/), [15.2](https://www.postgresql.org/docs/release/15.2/) | +| [15.4.0](epas15_4_0_rel_notes) | 21 Aug 2023 | [15.4](https://www.postgresql.org/docs/release/15.4/) +| [15.3.0](epas15_3_0_rel_notes) | 11 May 2023 | [15.3](https://www.postgresql.org/docs/release/15.3/) | +| [15.2.0](epas15_2_0_rel_notes) | 14 Feb 2023 | [15.0](https://www.postgresql.org/docs/release/15.0/), [15.1](https://www.postgresql.org/docs/release/15.1/), [15.2](https://www.postgresql.org/docs/release/15.2/) | ## Component certification diff --git a/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx b/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx index 3e969e562cb..a9e46eded50 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/04_control_schema_objects_created_for_publication.mdx @@ -411,7 +411,7 @@ _edb_replicator_pub.sp_dropsequence SQL_STORED_PROCEDURE _edb_replicator_sub.rrep_common_seq USER_TABLE ``` -SQL Server versions 2012 and 2014 support creation of sequence objects that can now perform the functionality previously provided by the preceding list of objects. The following are the sequence objects that are now used when the publication database is SQL Server 2012 or 2014: +SQL Server versions 2014 and 2012 support creation of sequence objects that can now perform the functionality previously provided by the preceding list of objects. The following are the sequence objects that are now used when the publication database is SQL Server 2012 or 2014: ```shell 1> USE edb; diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx index 36623d6ebb4..8ba40e8def8 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx @@ -13,15 +13,15 @@ The Replication Server documentation describes the latest version including mino | Version | Release Date | | -------------------------------- | ------------ | -| [7.5.1](eprs_rel_notes_7.5.1) | 2023 May 26 | -| [7.5.0](eprs_rel_notes_7.5.0) | 2023 Feb 14 | -| [7.4.0](eprs_rel_notes_7.4.0) | 2022 Nov 29 | -| [7.3.0](15_eprs_rel_notes_7.3.0) | 2022 Nov 15 | -| [7.2.1](16_eprs_rel_notes_7.2.1) | 2022 Jul 25 | -| [7.2.0](17_eprs_rel_notes_7.2.0) | 2022 Jun 24 | -| [7.1.0](18_eprs_rel_notes_7.1.0) | 2022 Mar 21 | -| [7.0.1](19_eprs_rel_notes_7.0.1) | 2022 Mar 03 | -| [7.0.0](20_eprs_rel_notes_7.0.0) | 2021 Dec 01 | +| [7.5.1](eprs_rel_notes_7.5.1) | 26 May 2023 | +| [7.5.0](eprs_rel_notes_7.5.0) | 14 Feb 2023 | +| [7.4.0](eprs_rel_notes_7.4.0) | 29 Nov 2022 | +| [7.3.0](15_eprs_rel_notes_7.3.0) | 15 Nov 2022 | +| [7.2.1](16_eprs_rel_notes_7.2.1) | 25 Jul 2022 | +| [7.2.0](17_eprs_rel_notes_7.2.0) | 24 Jun 2022 | +| [7.1.0](18_eprs_rel_notes_7.1.0) | 21 Mar 2022 | +| [7.0.1](19_eprs_rel_notes_7.0.1) | 03 Mar 2022 | +| [7.0.0](20_eprs_rel_notes_7.0.0) | 01 Dec 2021 | ## Supported upgrade paths diff --git a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/index.mdx b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/index.mdx index 04658f3c2c7..e435172e198 100644 --- a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/index.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/index.mdx @@ -18,11 +18,11 @@ The Hadoop Foreign Data Wrapper documentation describes the latest version inclu | Version | Release Date | | --------------------------------| ------------ | -| [2.3.1](hadoop_rel_notes_2.3.1) | 2023 Jul 20 | -| [2.3.0](hadoop_rel_notes_2.3.0) | 2023 Jan 06 | -| [2.2.0](hadoop_rel_notes_2.2.0) | 2022 May 26 | -| [2.1.0](hadoop_rel_notes_2.1.0) | 2021 Dec 02 | -| [2.0.8](hadoop_rel_notes_2.0.8) | 2021 Jun 24 | -| [2.0.7](hadoop_rel_notes_2.0.7) | 2020 Nov 23 | -| [2.0.5](hadoop_rel_notes_2.0.5) | 2019 Dec 10 | -| [2.0.4](hadoop_rel_notes_2.0.4) | 2018 Nov 28 | +| [2.3.1](hadoop_rel_notes_2.3.1) | 20 Jul 2023 | +| [2.3.0](hadoop_rel_notes_2.3.0) | 06 Jan 2023 | +| [2.2.0](hadoop_rel_notes_2.2.0) | 26 May 2022 | +| [2.1.0](hadoop_rel_notes_2.1.0) | 02 Dec 2021 | +| [2.0.8](hadoop_rel_notes_2.0.8) | 24 Jun 2021 | +| [2.0.7](hadoop_rel_notes_2.0.7) | 23 Nov 2020 | +| [2.0.5](hadoop_rel_notes_2.0.5) | 10 Dec 2019 | +| [2.0.4](hadoop_rel_notes_2.0.4) | 28 Nov 2018 | diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx index 020b7b15338..0f26c6d3125 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/index.mdx @@ -13,16 +13,16 @@ These release notes describe what's new in each release. When a minor or patch r | Version | Release Date | | ---------------------------------------- | ------------ | -| [42.5.4.1](jdbc_42.5.4.1_rel_notes) | 2023 Mar 16 | -| [42.5.1.2](jdbc_42.5.1.2_rel_notes) | 2023 Feb 14 | -| [42.5.1.1](jdbc_42.5.1.1_rel_notes) | 2022 Dec 9 | -| [42.5.0.1](jdbc_42.5.0.1_rel_notes) | 2022 Sep 1 | -| [42.3.3.1](08_jdbc_42.3.3.1_rel_notes) | 2022 Apr 20 | -| [42.3.2.1](09_jdbc_42.3.2.1_rel_notes) | 2022 Feb 15 | -| [42.2.24.1](10_jdbc_42.2.24.1_rel_notes) | 2021 Nov 5 | -| [42.2.19.1](12_jdbc_42.2.19.1_rel_notes) | 2021 Apr 15 | -| [42.2.12.3](14_jdbc_42.2.12.3_rel_notes) | 2020 Oct 22 | -| [42.2.9.1](16_jdbc_42.2.9.1_rel_notes) | 2020 May 18 | -| [42.2.8.1](18_jdbc_42.2.8.1_rel_notes) | 2019 Oct 21 | +| [42.5.4.1](jdbc_42.5.4.1_rel_notes) | 16 Mar 2023 | +| [42.5.1.2](jdbc_42.5.1.2_rel_notes) | 14 Feb 2023 | +| [42.5.1.1](jdbc_42.5.1.1_rel_notes) | 09 Dec 2022 | +| [42.5.0.1](jdbc_42.5.0.1_rel_notes) | 01 Sep 2022 | +| [42.3.3.1](08_jdbc_42.3.3.1_rel_notes) | 20 Apr 2022 | +| [42.3.2.1](09_jdbc_42.3.2.1_rel_notes) | 15 Feb 2022 | +| [42.2.24.1](10_jdbc_42.2.24.1_rel_notes) | 5 Nov 2021 | +| [42.2.19.1](12_jdbc_42.2.19.1_rel_notes) | 15 Apr 2021 | +| [42.2.12.3](14_jdbc_42.2.12.3_rel_notes) | 22 Oct 2020 | +| [42.2.9.1](16_jdbc_42.2.9.1_rel_notes) | 18 May 2020 | +| [42.2.8.1](18_jdbc_42.2.8.1_rel_notes) | 21 Oct 2019 | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx index 71b24680f38..aa7cc862c00 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx @@ -19,14 +19,14 @@ The Migration Toolkit documentation describes the latest version of Migration To | Version | Release Date | | ------- | ------------ | -| [55.6.0](mtk_556_rel_notes) | 2023 May 25 | -| [55.5.0](mtk_555_rel_notes) | 2023 Feb 14 | -| [55.4.0](mtk_554_rel_notes) | 2022 Nov 29 | -| [55.3.0](mtk_553_rel_notes) | 2022 Oct 06 | -| [55.2.3](mtk_5523_rel_notes) | 2022 Jun 16 | -| [55.2.2](05_mkt_5522_rel_notes) | 2022 Mar 10 | -| [55.2.1](06_mkt_5521_rel_notes) | 2022 Jan 13 | -| [55.2.0](07_mkt_552_rel_notes) | 2021 Dec 2 | -| [55.1.0](08_mkt_551_rel_notes) | 2021 Sep 20 | -| [55.0.0](09_mkt_55_rel_notes) | 2021 Mar 19 | +| [55.6.0](mtk_556_rel_notes) | 25 May 2023 | +| [55.5.0](mtk_555_rel_notes) | 14 Feb 2023 | +| [55.4.0](mtk_554_rel_notes) | 29 Nov 2022 | +| [55.3.0](mtk_553_rel_notes) | 06 Oct 2022 | +| [55.2.3](mtk_5523_rel_notes) | 16 Jun 2022 | +| [55.2.2](05_mkt_5522_rel_notes) | 10 Mar 2022 | +| [55.2.1](06_mkt_5521_rel_notes) | 13 Jan 2022 | +| [55.2.0](07_mkt_552_rel_notes) | 2 Dec 2021 | +| [55.1.0](08_mkt_551_rel_notes) | 20 Sep 2021 | +| [55.0.0](09_mkt_55_rel_notes) | 19 Mar 2021 | diff --git a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/index.mdx b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/index.mdx index 3e99eee7f41..92d5ea532ba 100644 --- a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/index.mdx +++ b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/index.mdx @@ -17,13 +17,13 @@ The Mongo Foreign Data Wrapper documentation describes the latest version of Mon | Version | Release date | | ----------------------------- | ------------ | -| [5.5.1](mongo5.5.1_rel_notes) | 2023 Jul 20 | -| [5.5.0](mongo5.5.0_rel_notes) | 2023 Jan 06 | -| [5.4.0](mongo5.4.0_rel_notes) | 2022 May 26 | -| [5.3.0](mongo5.3.0_rel_notes) | 2021 Dec 02 | -| [5.2.9](mongo5.2.9_rel_notes) | 2021 Jun 24 | -| [5.2.8](mongo5.2.8_rel_notes) | 2020 Nov 23 | -| [5.2.6](mongo5.2.8_rel_notes) | 2019 Sep 27 | -| [5.2.3](mongo5.2.8_rel_notes) | 2018 Nov 01 | +| [5.5.1](mongo5.5.1_rel_notes) | 20 Jul 2023 | +| [5.5.0](mongo5.5.0_rel_notes) | 06 Jan 2023 | +| [5.4.0](mongo5.4.0_rel_notes) | 26 May 2022 | +| [5.3.0](mongo5.3.0_rel_notes) | 02 Dec 2021 | +| [5.2.9](mongo5.2.9_rel_notes) | 24 Jun 2021 | +| [5.2.8](mongo5.2.8_rel_notes) | 23 Nov 2020 | +| [5.2.6](mongo5.2.8_rel_notes) | 27 Sep 2019 | +| [5.2.3](mongo5.2.8_rel_notes) | 01 Nov 2018 | diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx index ed38e10191e..99debbb99dd 100644 --- a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx @@ -17,11 +17,11 @@ The MySQL Foreign Data Wrapper documentation describes the latest version of MyS | Version | Release Date | | ----------------------------- | ------------ | -| [2.9.1](mysql2.9.1_rel_notes) | 2023 Jul 20 | -| [2.9.0](mysql2.9.0_rel_notes) | 2023 Jan 06 | -| [2.8.0](mysql2.8.0_rel_notes) | 2022 May 26 | -| [2.7.0](mysql2.7.0_rel_notes) | 2021 Dec 02 | -| [2.6.0](mysql2.6.0_rel_notes) | 2021 May 18 | -| [2.5.5](mysql2.5.5_rel_notes) | 2020 Nov 23 | -| [2.5.3](mysql2.5.3_rel_notes) | 2019 Dec 10 | -| [2.5.1](mysql2.5.1_rel_notes) | 2018 Nov 28 | \ No newline at end of file +| [2.9.1](mysql2.9.1_rel_notes) | 20 Jul 2023 | +| [2.9.0](mysql2.9.0_rel_notes) | 06 Jan 2023 | +| [2.8.0](mysql2.8.0_rel_notes) | 26 May 2022 | +| [2.7.0](mysql2.7.0_rel_notes) | 02 Dec 2021 | +| [2.6.0](mysql2.6.0_rel_notes) | 18 May 2021 | +| [2.5.5](mysql2.5.5_rel_notes) | 23 Nov 2020 | +| [2.5.3](mysql2.5.3_rel_notes) | 10 Dec 2019 | +| [2.5.1](mysql2.5.1_rel_notes) | 28 Nov 2018 | \ No newline at end of file diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx new file mode 100644 index 00000000000..a401f116870 --- /dev/null +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx @@ -0,0 +1,13 @@ +--- +title: "Version 15.2.0.4" +--- +The EDB OCL Connector provides an API similar to the Oracle Call Interface. + +New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 15.2.0.4 include: + +| Type | Description | +| ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Bug fix | Fixed a regression whereby a spurious rollback/begin occurs after deallocating a statement. [Support ticket: #94735]| + +!!!Important + This version requires EDB Postgres Advanced Server 15.4 or later. diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx index 6312a14c160..861724d4958 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx @@ -2,6 +2,7 @@ title: "EDB OCL Connector release notes" navTitle: Release Notes navigation: + - 15.2.0.4_ocl_release_notes - 15.2.0.3_ocl_release_notes - 15.2.0.2_ocl_release_notes - 01_ocl_release_notes @@ -13,7 +14,8 @@ Release notes describe what's new in a release. When a minor or patch release in | Version | Release date | | -------------------------------------- | ------------ | -| [15.2.0.3](15.2.0.3_ocl_release_notes) | 2023 Jun 20 | -| [15.2.0.2](15.2.0.2_ocl_release_notes) | 2023 May 19 | -| [15.2.0.1](01_ocl_release_notes) | 2023 Feb 14 | +| [15.2.0.4](15.2.0.4_ocl_release_notes) | 24 Aug 2023 | +| [15.2.0.3](15.2.0.3_ocl_release_notes) | 20 Jun 2023 | +| [15.2.0.2](15.2.0.2_ocl_release_notes) | 19 May 2023 | +| [15.2.0.1](01_ocl_release_notes) | 14 Feb 2023 | diff --git a/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx b/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx index 9e63dbfb4c3..63ce06b4210 100644 --- a/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx +++ b/product_docs/docs/odbc_connector/12/01_odbc_rel_notes/index.mdx @@ -8,6 +8,6 @@ Release notes describe what is new in a release. When a minor or patch release i | Version | Release Date | | ------------------------------------------- | ------------ | -| [12.02.0000.02](01_odbc_12.2.0.2_rel_notes) | 2021 Nov 16 | -| [12.00.0000.02](03_odbc_12.0.0.2_rel_notes) | 2020 Aug 9 | +| [12.02.0000.02](01_odbc_12.2.0.2_rel_notes) | 16 Nov 2021 | +| [12.00.0000.02](03_odbc_12.0.0.2_rel_notes) | 09 Aug 2020 | diff --git a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx index f4f7db8dacc..1263f196cd5 100644 --- a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx +++ b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx @@ -10,8 +10,8 @@ Release notes describe what's new in a release. When a minor or patch release in | Version | Release date | | ----------------------------------------- | ------------ | -| [13.02.0000.02](odbc_13.2.0.02_rel_notes) | 2023 Feb 14 | -| [13.02.0000.01](02_odbc_13.2.0.01_rel_notes) | 2022 May 17 | -| [13.01.0000.02](03_odbc_13.1.0.02_rel_notes) | 2021 Dec 12 | -| [13.01.0000.01](04_odbc_13.1.0.01_rel_notes) | 2021 Sep 14 | -| [13.00.0000.01](05_odbc_13.0.0.01_rel_notes) | 2020 Nov 19 | +| [13.02.0000.02](odbc_13.2.0.02_rel_notes) | 14 Feb 2023| +| [13.02.0000.01](02_odbc_13.2.0.01_rel_notes) | 17 May 2022| +| [13.01.0000.02](03_odbc_13.1.0.02_rel_notes) | 12 Dec 2021 | +| [13.01.0000.01](04_odbc_13.1.0.01_rel_notes) | 14 Sep 2021 | +| [13.00.0000.01](05_odbc_13.0.0.01_rel_notes) | 19 Nov 2020 | diff --git a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx index c8c1c6e8829..c2a53ccf12d 100644 --- a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx +++ b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx @@ -8,9 +8,9 @@ The EDB PgBouncer documentation describes the latest version of EDB PgBouncer 1, | Version | Release date | Upstream merges | | ------------------------------ | ------------ | --------------------------------------------------------------------------------- | -| [1.19.0.0](06_11900_rel_notes) | 2023 Jun 07 | Upstream [1.19.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-119x) -| [1.18.0.0](07_11800_rel_notes) | 2023 Feb 14 | Upstream [1.18.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-118x) -| [1.17.0.0](08_11700_rel_notes) | 2022 Aug 04 | Upstream [1.17.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-117x) -| [1.16.1.0](09_11610_rel_notes) | 2021 Dec 11 | Upstream [1.16.1.0](https://www.pgbouncer.org/changelog.html#pgbouncer-116x) | -| [1.16.0.1](10_11601_rel_notes) | 2021 Jun 10 | Upstream [1.16.0.1](https://www.pgbouncer.org/changelog.html#pgbouncer-116x) | +| [1.19.0.0](06_11900_rel_notes) | 07 Jun 2023 | Upstream [1.19.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-119x) +| [1.18.0.0](07_11800_rel_notes) | 14 Feb 2023 | Upstream [1.18.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-118x) +| [1.17.0.0](08_11700_rel_notes) | 04 Aug 2022 | Upstream [1.17.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-117x) +| [1.16.1.0](09_11610_rel_notes) | 11 Dec 2021 | Upstream [1.16.1.0](https://www.pgbouncer.org/changelog.html#pgbouncer-116x) | +| [1.16.0.1](10_11601_rel_notes) | 10 Jun 2021 | Upstream [1.16.0.1](https://www.pgbouncer.org/changelog.html#pgbouncer-116x) | diff --git a/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx b/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx index 722e81914b4..190f1efe85f 100644 --- a/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx +++ b/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx @@ -25,15 +25,15 @@ The release notes in this section provide information on what was new in each re | Version | Release Date | | ----------------------- | ------------ | -| [2.3.1](harp2.3.1_rel_notes) | 2023 Jul 27 | -| [2.3.0](harp2.3.0_rel_notes) | 2023 Jul 12 | -| [2.2.3](harp2.2.3_rel_notes) | 2023 May 16 | -| [2.2.2](harp2.2.2_rel_notes) | 2023 Mar 30 | -| [2.2.1](harp2.2.1_rel_notes) | 2022 Nov 16 | -| [2.2.0](harp2.2.0_rel_notes) | 2022 Aug 22 | -| [2.1.1](harp2.1.1_rel_notes) | 2022 Jun 21 | -| [2.1.0](harp2.1.0_rel_notes) | 2022 May 17 | -| [2.0.3](harp2.0.3_rel_notes) | 2022 Mar 31 | -| [2.0.2](harp2.0.2_rel_notes) | 2022 Feb 24 | -| [2.0.1](harp2.0.1_rel_notes) | 2021 Jan 31 | -| [2.0.0](harp2_rel_notes) | 2021 Dec 01 | +| [2.3.1](harp2.3.1_rel_notes) | 27 Jul 2023 | +| [2.3.0](harp2.3.0_rel_notes) | 12 Jul 2023 | +| [2.2.3](harp2.2.3_rel_notes) | 16 May 2023 | +| [2.2.2](harp2.2.2_rel_notes) | 30 Mar 2023 | +| [2.2.1](harp2.2.1_rel_notes) | 16 Nov 2022 | +| [2.2.0](harp2.2.0_rel_notes) | 22 Aug 2022 | +| [2.1.1](harp2.1.1_rel_notes) | 21 Jun 2022 | +| [2.1.0](harp2.1.0_rel_notes) | 17 May 2022 | +| [2.0.3](harp2.0.3_rel_notes) | 31 Mar 2022 | +| [2.0.2](harp2.0.2_rel_notes) | 24 Feb 2022 | +| [2.0.1](harp2.0.1_rel_notes) | 31 Jan 2021 | +| [2.0.0](harp2_rel_notes) | 01 Dec 2021 | diff --git a/product_docs/docs/pgd/4/rel_notes/index.mdx b/product_docs/docs/pgd/4/rel_notes/index.mdx index 75e5ab566bc..9ea08a1e8fd 100644 --- a/product_docs/docs/pgd/4/rel_notes/index.mdx +++ b/product_docs/docs/pgd/4/rel_notes/index.mdx @@ -27,17 +27,17 @@ The EDB Postgres Distributed documentation describes the latest version of EDB P | ------------ | ---------------------------- | ----- | ----- | ----- | -------------------------------------------------------------------------------- | | 2023 July 27 | [4.3.1-2 ](pgd_4.3.1-2_rel_notes)| 4.3.1 | 2.3.1 | 1.1.1 | [23.19](/tpa/latest/rel_notes/tpa_23.19_rel_notes) | | 2023 July 12 | [4.3.1-1 ](pgd_4.3.1-1_rel_notes)| 4.3.1 | 2.3.0 | 1.1.1 | [23.19](/tpa/latest/rel_notes/tpa_23.19_rel_notes) | -| 2023 May 17 | [4.3.1](pgd_4.3.1_rel_notes) | 4.3.1 | 2.2.3 | 1.1.1 | [23.17](/tpa/latest/rel_notes/tpa_23.17_rel_notes) | -| 2023 Mar 30 | [4.3.0-1](pgd_4.3.0-1_rel_notes) | 4.3.0 | 2.2.2 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | -| 2023 Feb 14 | [4.3.0](pgd_4.3.0_rel_notes) | 4.3.0 | 2.2.1 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | -| 2022 Dec 14 | [4.2.2](pgd_4.2.2_rel_notes) | 4.2.2 | 2.2.1 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | -| 2022 Nov 16 | [4.2.1](pgd_4.2.1_rel_notes) | 4.2.1 | 2.2.1 | 1.1.0 | [23.7](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-237) | -| 2022 Aug 22 | [4.2.0](pgd_4.2.0_rel_notes) | 4.2.0 | 2.2.0 | 1.1.0 | [23.5](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-235) | +| 17 May 2023 | [4.3.1](pgd_4.3.1_rel_notes) | 4.3.1 | 2.2.3 | 1.1.1 | [23.17](/tpa/latest/rel_notes/tpa_23.17_rel_notes) | +| 30 Mar 2023 | [4.3.0-1](pgd_4.3.0-1_rel_notes) | 4.3.0 | 2.2.2 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | +| 14 Feb 2023 | [4.3.0](pgd_4.3.0_rel_notes) | 4.3.0 | 2.2.1 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | +| 14 Dec 2022 | [4.2.2](pgd_4.2.2_rel_notes) | 4.2.2 | 2.2.1 | 1.1.0 | [23.9](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-239) | +| 16 Nov 2022 | [4.2.1](pgd_4.2.1_rel_notes) | 4.2.1 | 2.2.1 | 1.1.0 | [23.7](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-237) | +| 22 Aug 2022 | [4.2.0](pgd_4.2.0_rel_notes) | 4.2.0 | 2.2.0 | 1.1.0 | [23.5](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-235) | | 2022 June 21 | [4.1.1](pgd_4.1.1_rel_notes) | 4.1.1 | 2.1.1 | 1.0.0 | [23.2](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-232) | -| 2022 May 17 | [4.1.0](pgd_4.1.0_rel_notes) | 4.1.0 | 2.1.0 | 1.0.0 | [23.1](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-231) | -| 2022 Mar 31 | [4.0.3](pgd_4.0.3_rel_notes) | - | 2.0.3 | - | 22.10 | -| 2022 Feb 24 | [4.0.2](pgd_4.0.2_rel_notes) | 4.0.2 | 2.0.2 | - | 22.9 | -| 2022 Jan 31 | [4.0.1](pgd_4.0.1_rel_notes) | 4.0.1 | 2.0.1 | - | 22.6 | -| 2021 Dec 01 | [4.0.0](pgd_4.0.0_rel_notes) | 4.0.0 | 2.0.0 | - | 21.9 | +| 17 May 2022 | [4.1.0](pgd_4.1.0_rel_notes) | 4.1.0 | 2.1.0 | 1.0.0 | [23.1](/tpa/latest/rel_notes/tpa_23.1-11_rel_notes/#tpa-231) | +| 31 Mar 2022 | [4.0.3](pgd_4.0.3_rel_notes) | - | 2.0.3 | - | 22.10 | +| 24 Feb 2022 | [4.0.2](pgd_4.0.2_rel_notes) | 4.0.2 | 2.0.2 | - | 22.9 | +| 31 Jan 2022 | [4.0.1](pgd_4.0.1_rel_notes) | 4.0.1 | 2.0.1 | - | 22.6 | +| 01 Dec 2021 | [4.0.0](pgd_4.0.0_rel_notes) | 4.0.0 | 2.0.0 | - | 21.9 | diff --git a/product_docs/docs/pgd/5/monitoring/otel.mdx b/product_docs/docs/pgd/5/monitoring/otel.mdx index ca7df3a644d..c33fb9ec965 100644 --- a/product_docs/docs/pgd/5/monitoring/otel.mdx +++ b/product_docs/docs/pgd/5/monitoring/otel.mdx @@ -3,7 +3,7 @@ title: OpenTelemetry integration --- You can configure EDB Postgres Distributed to report monitoring information -as well as traces to the OpenTelemetry collector. +as well as traces to the [OpenTelemetry](https://opentelemetry.io/) collector. EDB Postgres Distributed OTEL collector fills several resource attributes. These are attached to all metrics and traces: diff --git a/product_docs/docs/pgd/5/monitoring/sql.mdx b/product_docs/docs/pgd/5/monitoring/sql.mdx index 0a7f7d64719..36ac35396c8 100644 --- a/product_docs/docs/pgd/5/monitoring/sql.mdx +++ b/product_docs/docs/pgd/5/monitoring/sql.mdx @@ -113,7 +113,7 @@ You can use another view for monitoring of outgoing replication activity: - [`bdr.node_replication_rates`](/pgd/latest/reference/catalogs-visible/#bdrnode_replication_rates) for monitoring outgoing replication -The []`bdr.node_replication_rates`](/pgd/latest/reference/catalogs-visible/#bdrnode_replication_rates) view gives an overall picture of the outgoing +The [`bdr.node_replication_rates`](/pgd/latest/reference/catalogs-visible/#bdrnode_replication_rates) view gives an overall picture of the outgoing replication activity along with the catchup estimates for peer nodes, specifically. @@ -152,7 +152,7 @@ view. !!! Note This catalog is present only when the bdr-enterprise extension is installed. -Administrators can query `[`bdr.node_slots`](/pgd/latest/reference/catalogs-visible/#bdrnode_slots) for outgoing replication from the +Administrators can query [`bdr.node_slots`](/pgd/latest/reference/catalogs-visible/#bdrnode_slots) for outgoing replication from the local node. It shows information about replication status of all other nodes in the group that are known to the current node as well as any additional replication slots created by PGD on the current node. diff --git a/product_docs/docs/pgd/5/rel_notes/index.mdx b/product_docs/docs/pgd/5/rel_notes/index.mdx index 8ca36d6563f..c5eb7e32160 100644 --- a/product_docs/docs/pgd/5/rel_notes/index.mdx +++ b/product_docs/docs/pgd/5/rel_notes/index.mdx @@ -20,7 +20,7 @@ that introduced the feature. | Release Date | EDB Postgres Distributed | BDR extension | PGD CLI | PGD Proxy | | ------------- | ---------------------------- | ------------- | ------- | --------- | -| 2023 Aug 4 | [5.2.0](pgd_5.2.0_rel_notes) | 5.2.0 | 5.2.0 | 5.2.0 | -| 2023 May 16 | [5.1.0](pgd_5.1.0_rel_notes) | 5.1.0 | 5.1.0 | 5.1.0 | -| 2023 Mar 21 | [5.0.1](pgd_5.0.1_rel_notes) | 5.0.0 | 5.0.1 | 5.0.1 | -| 2023 Feb 21 | [5.0.0](pgd_5.0.0_rel_notes) | 5.0.0 | 5.0.0 | 5.0.0 | +| 4 Aug 2023 | [5.2.0](pgd_5.2.0_rel_notes) | 5.2.0 | 5.2.0 | 5.2.0 | +| 16 May 2023 | [5.1.0](pgd_5.1.0_rel_notes) | 5.1.0 | 5.1.0 | 5.1.0 | +| 21 Mar 2023 | [5.0.1](pgd_5.0.1_rel_notes) | 5.0.0 | 5.0.1 | 5.0.1 | +| 21 Feb 2023 | [5.0.0](pgd_5.0.0_rel_notes) | 5.0.0 | 5.0.0 | 5.0.0 | diff --git a/product_docs/docs/pge/15/release_notes/index.mdx b/product_docs/docs/pge/15/release_notes/index.mdx index bd99b69f9b0..0d513be5602 100644 --- a/product_docs/docs/pge/15/release_notes/index.mdx +++ b/product_docs/docs/pge/15/release_notes/index.mdx @@ -10,8 +10,8 @@ cover what was new in each release. | Version | Release date | | ------------------------ | ------------ | -| [15.3](rel_notes15.3) | 2023 May 11 | -| [15.2](rel_notes15.2) | 2023 Feb 14 | +| [15.3](rel_notes15.3) | 11 May 2023 | +| [15.2](rel_notes15.2) | 14 Feb 2023 | diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx index 24731fc47b7..1b0236f8d2f 100644 --- a/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx +++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx @@ -18,8 +18,8 @@ The EDB Pgpool-II documentation describes the latest version of EDB Pgpool-II, i | Version | Release Date | Upstream merges | | | ------------------------------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | -| [4.4.2](442_rel_notes) | 2023 Feb 14 | Upstream [4.4.2](https://www.pgpool.net/docs/44/en/html/release-4-4-2.html) | | -| [4.3.2](07_432_rel_notes), [4.2.9](429_rel_notes), [4.1.12](4112_rel_notes), [4.0.19](4019_rel_notes), [3.7.24](3724_rel_notes) | 2022 Jul 05 | Upstream [4.3.2](https://www.pgpool.net/docs/43/en/html/release-4-3-2.html#bug-fixes), [4.2.9](https://www.pgpool.net/docs/43/en/html/release-4-2-9.html#bug-fixes), [4.1.12](https://www.pgpool.net/docs/43/en/html/release-4-1-12.html#bug-fixes), [4.0.19](https://www.pgpool.net/docs/43/en/html/release-4-0-19.html#bug-fixes), [3.7.24](https://www.pgpool.net/docs/43/en/html/release-3-7-24.html#bug-fixes) | | -| [4.3.0](08_430_rel_notes) | 2022 Feb 01 | Upstream [4.3.0](https://www.pgpool.net/docs/43/en/html/release-4-3-0.html#bug-fixes) | | -| [4.2.6](09_426_rel_notes) | 2021 Dec 01 | Upstream [4.2.6](https://www.pgpool.net/docs/42/en/html/release-4-2-6.html#bug-fixes) | | -| [4.2.5](10_425_rel_notes) | 2021 Jun 10 | Upstream [4.2.5](https://www.pgpool.net/docs/42/en/html/release-4-2-5.html) and [4.2.4](https://www.pgpool.net/docs/42/en/html/release-4-2-4.html) | | \ No newline at end of file +| [4.4.2](442_rel_notes) | 14 Feb 2023 | Upstream [4.4.2](https://www.pgpool.net/docs/44/en/html/release-4-4-2.html) | | +| [4.3.2](07_432_rel_notes), [4.2.9](429_rel_notes), [4.1.12](4112_rel_notes), [4.0.19](4019_rel_notes), [3.7.24](3724_rel_notes) | 05 Jul 2022 | Upstream [4.3.2](https://www.pgpool.net/docs/43/en/html/release-4-3-2.html#bug-fixes), [4.2.9](https://www.pgpool.net/docs/43/en/html/release-4-2-9.html#bug-fixes), [4.1.12](https://www.pgpool.net/docs/43/en/html/release-4-1-12.html#bug-fixes), [4.0.19](https://www.pgpool.net/docs/43/en/html/release-4-0-19.html#bug-fixes), [3.7.24](https://www.pgpool.net/docs/43/en/html/release-3-7-24.html#bug-fixes) | | +| [4.3.0](08_430_rel_notes) | 01 Feb 2022 | Upstream [4.3.0](https://www.pgpool.net/docs/43/en/html/release-4-3-0.html#bug-fixes) | | +| [4.2.6](09_426_rel_notes) | 01 Dec 2021 | Upstream [4.2.6](https://www.pgpool.net/docs/42/en/html/release-4-2-6.html#bug-fixes) | | +| [4.2.5](10_425_rel_notes) | 10 Jun 2021 | Upstream [4.2.5](https://www.pgpool.net/docs/42/en/html/release-4-2-5.html) and [4.2.4](https://www.pgpool.net/docs/42/en/html/release-4-2-4.html) | | \ No newline at end of file diff --git a/product_docs/docs/postgis/3.2/01_release_notes/index.mdx b/product_docs/docs/postgis/3.2/01_release_notes/index.mdx index ba879151a01..769dc9c3e12 100644 --- a/product_docs/docs/postgis/3.2/01_release_notes/index.mdx +++ b/product_docs/docs/postgis/3.2/01_release_notes/index.mdx @@ -13,11 +13,11 @@ cover what was new in each release. | Version | Release date | | ------------------------ | ------------ | -| [3.2.1](rel_notes321) | 2022 Aug 04 | -| [3.2.0](rel_notes32) | 2022 Dec 01 | -| [3.1.5](rel_notes315) | 2022 Aug 03 | -| [3.1.4](rel_notes314) | 2021 Dec 01 | -| [3.1.2](rel_notes312) | 2021 Jun 24| +| [3.2.1](rel_notes321) | 04 Aug 2022 | +| [3.2.0](rel_notes32) | 01 Dec 2022 | +| [3.1.5](rel_notes315) | 03 Aug 2022| +| [3.1.4](rel_notes314) | 01 Dec 2021| +| [3.1.2](rel_notes312) | 24 Jun 2021 | diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/rel_notes/index.mdx index a847b4e6165..cf3533088ad 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/rel_notes/index.mdx @@ -11,7 +11,7 @@ The EDB Postgres Distributed for Kubernetes documentation describes the major ve | Version | Release date | | -------------------------- | ------------ | -| [0.6.0](0_6_rel_notes) | 2023 May 15 | +| [0.6.0](0_6_rel_notes) | 15 May 2023 | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx index 335c160cdfa..d490711144a 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx @@ -63,58 +63,58 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | Version | Release date | Upstream merges | | -------------------------- | ------------ | ------------------------------------------------------------------------------------------- | -| [1.20.2](1_20_2_rel_notes) | 2023 Jul 27 | Upstream [1.20.2](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | -| [1.20.1](1_20_1_rel_notes) | 2023 Jun 13 | Upstream [1.20.1](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | -| [1.20.0](1_20_0_rel_notes) | 2023 Apr 27 | Upstream [1.20.0](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | -| [1.19.4](1_19_4_rel_notes) | 2023 Jul 27 | Upstream [1.19.4](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | -| [1.19.3](1_19_3_rel_notes) | 2023 Jun 13 | Upstream [1.19.3](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | -| [1.19.2](1_19_2_rel_notes) | 2023 Apr 27 | Upstream [1.19.2](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | -| [1.19.1](1_19_1_rel_notes) | 2023 Mar 20 | Upstream [1.19.1](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | -| [1.19.0](1_19_0_rel_notes) | 2023 Feb 14 | Upstream [1.19.0](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | -| [1.18.6](1_18_6_rel_notes) | 2023 Jul 27 | None | -| [1.18.5](1_18_5_rel_notes) | 2023 Jun 13 | Upstream [1.18.5](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.18.4](1_18_4_rel_notes) | 2023 Apr 27 | Upstream [1.18.4](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.18.3](1_18_3_rel_notes) | 2023 Mar 20 | Upstream [1.18.3](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.18.2](1_18_2_rel_notes) | 2023 Feb 14 | Upstream [1.18.2](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.18.1](1_18_1_rel_notes) | 2022 Dec 21 | Upstream [1.18.1](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.18.0](1_18_0_rel_notes) | 2022 Nov 14 | Upstream [1.18.0](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | -| [1.17.5](1_17_5_rel_notes) | 2023 Mar 20 | Upstream [1.17.5](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.4](1_17_4_rel_notes) | 2023 Feb 14 | Upstream [1.17.4](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.3](1_17_3_rel_notes) | 2022 Dec 21 | Upstream [1.17.3](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.2](1_17_2_rel_notes) | 2022 Nov 14 | Upstream [1.17.2](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.1](1_17_1_rel_notes) | 2022 Oct 7 | Upstream [1.17.1](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.17.0](1_17_rel_notes) | 2022 Sep 6 | Upstream [1.17.0](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | -| [1.16.4](1_16_4_rel_notes) | 2022 Nov 14 | Upstream [1.16.4](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | -| [1.16.3](1_16_3_rel_notes) | 2022 Oct 7 | Upstream [1.16.3](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | -| [1.16.2](1_16_2_rel_notes) | 2022 Sep 6 | Upstream [1.16.2](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | -| [1.16.1](1_16_1_rel_notes) | 2022 Aug 12 | Upstream [1.16.1](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | -| [1.16.0](1_16_rel_notes) | 2022 Jul 07 | Upstream [1.16.0](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16) | -| [1.15.5](1_15_5_rel_notes) | 2022 Oct 7 | Upstream [1.15.5](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.15.4](1_15_4_rel_notes) | 2022 Sep 6 | Upstream [1.15.4](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.15.3](1_15_3_rel_notes) | 2022 Aug 12 | Upstream [1.15.3](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.15.2](1_15_2_rel_notes) | 2022 Jul 07 | Upstream [1.15.2](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.15.1](1_15_1_rel_notes) | 2022 May 27 | Upstream [1.15.1](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.15.0](1_15_rel_notes) | 2022 Apr 21 | Upstream [1.15.0](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | -| [1.14.0](1_14_rel_notes) | 2022 Mar 25 | NA | -| [1.13.0](1_13_rel_notes) | 2022 Feb 17 | NA | -| [1.12.0](1_12_rel_notes) | 2022 Jan 11 | NA | -| [1.11.0](1_11_rel_notes) | 2021 Dec 15 | NA | -| [1.10.0](1_10_rel_notes) | 2021 Nov 11 | NA | -| [1.9.2](1_9_2_rel_notes) | 2021 Oct 15 | NA | -| [1.9.1](1_9_1_rel_notes) | 2021 Sep 30 | NA | -| [1.9.0](1_9_rel_notes) | 2021 Sep 28 | NA | -| [1.8.0](1_8_rel_notes) | 2021 Sep 13 | NA | -| [1.7.1](1_7_1_rel_notes) | 2021 Aug 11 | NA | -| [1.7.0](1_7_rel_notes) | 2021 Jul 28 | NA | -| [1.6.0](1_6_rel_notes) | 2021 Jul 12 | NA | -| [1.5.1](1_5_1_rel_notes) | 2021 Jun 11 | NA | -| [1.5.0](1_5_rel_notes) | 2021 Jun 17 | NA | -| [1.4.0](1_4_rel_notes) | 2021 May 18 | NA | -| [1.3.0](1_3_rel_notes) | 2021 Apr 23 | NA | -| [1.2.1](1_2_1_rel_notes) | 2021 Apr 06 | NA | -| [1.2.0](1_2_rel_notes) | 2021 Mar 31 | NA | -| [1.1.0](1_1_rel_notes) | 2021 Mar 03 | NA | -| [1.0.0](1_0_rel_notes) | 2021 Feb 04 | NA | +| [1.20.2](1_20_2_rel_notes) | 27 Jul 2023 | Upstream [1.20.2](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | +| [1.20.1](1_20_1_rel_notes) | 13 Jun 2023 | Upstream [1.20.1](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | +| [1.20.0](1_20_0_rel_notes) | 27 Apr 2023 | Upstream [1.20.0](https://cloudnative-pg.io/documentation/1.20/release_notes/v1.20/) | +| [1.19.4](1_19_4_rel_notes) | 27 Jul 2023 | Upstream [1.19.4](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | +| [1.19.3](1_19_3_rel_notes) | 13 Jun 2023 | Upstream [1.19.3](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | +| [1.19.2](1_19_2_rel_notes) | 27 Apr 2023 | Upstream [1.19.2](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | +| [1.19.1](1_19_1_rel_notes) | 20 Mar 2023 | Upstream [1.19.1](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | +| [1.19.0](1_19_0_rel_notes) | 14 Feb 2023 | Upstream [1.19.0](https://cloudnative-pg.io/documentation/1.19/release_notes/v1.19/) | +| [1.18.6](1_18_6_rel_notes) | 27 Jul 2023 | None | +| [1.18.5](1_18_5_rel_notes) | 13 Jun 2023 | Upstream [1.18.5](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.18.4](1_18_4_rel_notes) | 27 Apr 2023 | Upstream [1.18.4](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.18.3](1_18_3_rel_notes) | 20 Mar 2023 | Upstream [1.18.3](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.18.2](1_18_2_rel_notes) | 14 Feb 2023 | Upstream [1.18.2](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.18.1](1_18_1_rel_notes) | 21 Dec 2022 | Upstream [1.18.1](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.18.0](1_18_0_rel_notes) | 14 Nov 2022 | Upstream [1.18.0](https://cloudnative-pg.io/documentation/1.18/release_notes/v1.18/) | +| [1.17.5](1_17_5_rel_notes) | 20 Mar 2023 | Upstream [1.17.5](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.4](1_17_4_rel_notes) | 14 Feb 2023 | Upstream [1.17.4](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.3](1_17_3_rel_notes) | 21 Dec 2022 | Upstream [1.17.3](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.2](1_17_2_rel_notes) | 14 Nov 2022 | Upstream [1.17.2](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.1](1_17_1_rel_notes) | 07 Oct 2022 | Upstream [1.17.1](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.17.0](1_17_rel_notes) | 06 Sep 2022 | Upstream [1.17.0](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.16.4](1_16_4_rel_notes) | 14 Nov 2022 | Upstream [1.16.4](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | +| [1.16.3](1_16_3_rel_notes) | 07 Oct 2022 | Upstream [1.16.3](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | +| [1.16.2](1_16_2_rel_notes) | 06 Sep 2022 | Upstream [1.16.2](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | +| [1.16.1](1_16_1_rel_notes) | 12 Aug 2022 | Upstream [1.16.1](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | +| [1.16.0](1_16_rel_notes) | 07 Jul 2022 | Upstream [1.16.0](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16) | +| [1.15.5](1_15_5_rel_notes) | 07 Oct 2022 | Upstream [1.15.5](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.4](1_15_4_rel_notes) | 06 Sep 2022 | Upstream [1.15.4](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.3](1_15_3_rel_notes) | 12 Aug 2022 | Upstream [1.15.3](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.2](1_15_2_rel_notes) | 07 Jul 2022 | Upstream [1.15.2](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.1](1_15_1_rel_notes) | 27 May 2022 | Upstream [1.15.1](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.15.0](1_15_rel_notes) | 21 Apr 2022 | Upstream [1.15.0](https://cloudnative-pg.io/documentation/1.15/release_notes/v1.15) | +| [1.14.0](1_14_rel_notes) | 25 Mar 2022 | NA | +| [1.13.0](1_13_rel_notes) | 17 Feb 2022 | NA | +| [1.12.0](1_12_rel_notes) | 11 Jan 2022 | NA | +| [1.11.0](1_11_rel_notes) | 15 Dec 2021 | NA | +| [1.10.0](1_10_rel_notes) | 11 Nov 2021 | NA | +| [1.9.2](1_9_2_rel_notes) | 15 Oct 2021 | NA | +| [1.9.1](1_9_1_rel_notes) | 30 Sep 2021 | NA | +| [1.9.0](1_9_rel_notes) | 28 Sep 2021 | NA | +| [1.8.0](1_8_rel_notes) | 13 Sep 2021 | NA | +| [1.7.1](1_7_1_rel_notes) | 11 Aug 2021 | NA | +| [1.7.0](1_7_rel_notes) | 28 Jul 2021 | NA | +| [1.6.0](1_6_rel_notes) | 12 Jul 2021 | NA | +| [1.5.1](1_5_1_rel_notes) | 11 Jun 2021 | NA | +| [1.5.0](1_5_rel_notes) | 17 Jun 2021 | NA | +| [1.4.0](1_4_rel_notes) | 18 May 2021 | NA | +| [1.3.0](1_3_rel_notes) | 23 Apr 2021 | NA | +| [1.2.1](1_2_1_rel_notes) | 06 Apr 2021 | NA | +| [1.2.0](1_2_rel_notes) | 31 Mar 2021 | NA | +| [1.1.0](1_1_rel_notes) | 03 Mar 2021 | NA | +| [1.0.0](1_0_rel_notes) | 04 Feb 2021 | NA |