Merge pull request #2339 from EnterpriseDB/release/2022-02-15-a

Release/2022 02 15 a

.github/workflows/sync-and-process-files.yml

@@ -45,6 +45,7 @@ jobs:
         working-directory: source
 
       - name: Create pull request
+        if: ${{ !env.ACT }}
         uses: peter-evans/[email protected]
         with:
           body: ${{ env.BODY }}

product_docs/docs/bdr/3.7/appusage.mdx

@@ -390,7 +390,7 @@ form](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRIN
 
 Here's an example invocation in a CAMO environment:
 
-```shell
+```sh
     pgbench -m camo -p $node1_port -h $node1_host bdrdemo \
         "host=$node2_host user=postgres port=$node2_port dbname=bdrdemo"
 ```

product_docs/docs/bdr/3.7/camo_clients.mdx

@@ -1,8 +1,8 @@
 ---
-navTitle: 'Appendix E: CAMO Reference Clients'
-title: 'Appendix E: CAMO Reference Client Implementations'
+navTitle: 'Appendix D: CAMO Reference Clients'
+title: 'Appendix D: CAMO Reference Client Implementations'
 originalFilePath: camo_clients.md
 
 ---
 
-<AuthenticatedContentPlaceholder target="https://documentation.2ndquadrant.com/bdr3-enterprise/release/latest/camo_clients/" topic="Appendix E: CAMO Reference Client Implementations" />
+<AuthenticatedContentPlaceholder target="https://documentation.2ndquadrant.com/bdr3-enterprise/release/latest/camo_clients/" topic="Appendix D: CAMO Reference Client Implementations" />

product_docs/docs/bdr/3.7/functions.mdx

@@ -56,7 +56,9 @@ Upon session initialization, this is set to the node id the client is
 connected to.  This allows an application to figure out what node it
 is connected to even behind a transparent proxy.
 
-It is also used in combination with CAMO, see the [Connection pools and proxies](camo#connection-pools-and-proxies) section.
+It is also used in combination with CAMO, see the
+[Connection pools and proxies](CAMO#connection-pools-and-proxies)
+section.
 
 ### bdr.last_committed_lsn
 
@@ -224,7 +226,7 @@ to all of the nodes in the cluster.
 
 Be careful when using this function since you risk breaking replication
 and causing inconsistencies between nodes. Use either transparent DDL
-replication or `bdr.bdr_replicate_ddl_command()` to replicate DDL.
+replication or `bdr.replicate_ddl_command()` to replicate DDL.
 DDL may be blocked in a future release.
 
 #### Example
@@ -279,6 +281,84 @@ $$);
 ]
 ```
 
+### bdr.run_on_nodes
+
+Function to run a query on a specified list of nodes.
+
+!!! Warning
+    This function will run an arbitrary query on remote nodes with the
+    privileges of the user used for the internode connections as specified in the
+    node's DSN. Caution needs to be taken when granting privileges to this function.
+
+#### Synopsis
+
+```postgresql
+bdr.run_on_nodes(node_names text[], query text)
+```
+
+#### Parameters
+
+-   `node_names` - text ARRAY of node names where query will be executed.
+-   `query` - arbitrary query to be executed.
+
+#### Notes
+
+This function will connect to other nodes and execute the query, returning
+a result from each of them in json format. Multiple rows may be returned from
+each node, encoded as a json array. Any errors, such as being unable to
+connect because a node is down, will be shown in the response field.
+No explicit statement_timeout or other runtime parameters are set, so
+defaults will be used.
+
+This function does not go through normal replication, it uses direct client
+connection to all known nodes. By default, the connection is created
+with bdr.ddl_replication = off, since the command are already being sent
+to all of the nodes in the cluster.
+
+Be careful when using this function since you risk breaking replication
+and causing inconsistencies between nodes. Use either transparent DDL
+replication or `bdr.replicate_ddl_command()` to replicate DDL.
+DDL may be blocked in a future release.
+
+### bdr.run_on_group
+
+Function to run a query on a group of nodes.
+
+!!! Warning
+    This function will run an arbitrary query on remote nodes with the
+    privileges of the user used for the internode connections as specified in the
+    node's DSN. Caution needs to be taken when granting privileges to this function.
+
+#### Synopsis
+
+```postgresql
+bdr.run_on_group(node_group_name text, query text)
+```
+
+#### Parameters
+
+-   `node_group_name` - name of node group where query will be executed.
+-   `query` - arbitrary query to be executed.
+
+#### Notes
+
+This function will connect to other nodes and execute the query, returning
+a result from each of them in json format. Multiple rows may be returned from
+each node, encoded as a json array. Any errors, such as being unable to
+connect because a node is down, will be shown in the response field.
+No explicit statement_timeout or other runtime parameters are set, so
+defaults will be used.
+
+This function does not go through normal replication, it uses direct client
+connection to all known nodes. By default, the connection is created
+with bdr.ddl_replication = off, since the command are already being sent
+to all of the nodes in the cluster.
+
+Be careful when using this function since you risk breaking replication
+and causing inconsistencies between nodes. Use either transparent DDL
+replication or `bdr.replicate_ddl_command()` to replicate DDL.
+DDL may be blocked in a future release.
+
 ### bdr.global_lock_table
 
 This function will acquire a global DML locks on a given table.

product_docs/docs/bdr/3.7/index.mdx

@@ -2,6 +2,7 @@
 navTitle: BDR
 navigation:
   - index
+  - release-notes
   - overview
   - appusage
   - configuration
@@ -25,11 +26,9 @@ navigation:
   - catalogs
   - monitoring
   - functions
-  - credits
-  - release-notes
   - isolation_details
   - known-issues
-  - libraries
+  - licenses
   - camo_clients
 title: BDR (Bi-Directional Replication)
 directoryDefaults:

product_docs/docs/bdr/3.7/isolation_details.mdx

@@ -1,4 +1,5 @@
 ---
+navTitle: 'Appendix A: Conflict Details'
 title: 'Appendix B: Conflict Details'
 originalFilePath: isolation/details.md
 

product_docs/docs/bdr/3.7/known-issues.mdx

@@ -1,5 +1,5 @@
 ---
-title: 'Appendix C: Known Issues'
+title: 'Appendix B: Known Issues'
 originalFilePath: known-issues.md
 
 ---

product_docs/docs/bdr/3.7/licenses.mdx

@@ -0,0 +1,186 @@
+---
+title: 'Appendix C: Licenses'
+originalFilePath: licenses.md
+
+---
+
+In this section we list the libraries used by BDR3, with the
+corresponding licenses.
+
+| Library | License                            |
+| :------ | :--------------------------------- |
+| LLVM    | BSD (3-clause)                     |
+| OpenSSL | SSLeay License AND OpenSSL License |
+| Libpq   | PostgreSQL License                 |
+
+## LLVM
+
+Copyright © 1994 The Regents of the University of California.  All
+rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+1.  Redistributions of source code must retain the above copyright
+    notice, this list of conditions and the following disclaimer.
+2.  Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in
+    the documentation and/or other materials provided with the
+    distribution.
+3.  Neither the name of the University nor the names of its
+    contributors may be used to endorse or promote products derived
+    from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS \`\`AS IS''
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
+BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
+BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
+WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
+IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+## OpenSSL
+
+====================================================================
+
+Copyright © 1998-2004 The OpenSSL Project.  All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+1.  Redistributions of source code must retain the above copyright
+    notice, this list of conditions and the following disclaimer.
+
+2.  Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in
+    the documentation and/or other materials provided with the
+    distribution.
+
+3.  All advertising materials mentioning features or use of this
+    software must display the following acknowledgment:
+    "This product includes software developed by the OpenSSL Project
+    for use in the OpenSSL Toolkit. (<http://www.openssl.org/)">
+
+4.  The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
+    endorse or promote products derived from this software without
+    prior written permission. For written permission, please contact
+    openssl-coreopenssl.org.
+
+5.  Products derived from this software may not be called "OpenSSL"
+    nor may "OpenSSL" appear in their names without prior written
+    permission of the OpenSSL Project.
+
+6.  Redistributions of any form whatsoever must retain the following
+    acknowledgment:
+    "This product includes software developed by the OpenSSL Project
+    for use in the OpenSSL Toolkit (<http://www.openssl.org/)">
+
+THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT \`\`AS IS'' AND ANY
+EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR
+ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+OF THE POSSIBILITY OF SUCH DAMAGE.
+
+====================================================================
+
+This product includes cryptographic software written by Eric Young
+(eaycryptsoft.com).  This product includes software written by Tim
+Hudson (tjhcryptsoft.com).
+
+## Original SSLeay Licence
+
+Copyright © 1995-1998 Eric Young (eaycryptsoft.com)
+All rights reserved.
+
+This package is an SSL implementation written
+by Eric Young (eaycryptsoft.com).
+The implementation was written so as to conform with Netscapes SSL.
+
+This library is free for commercial and non-commercial use as long as
+the following conditions are aheared to.  The following conditions
+apply to all code found in this distribution, be it the RC4, RSA,
+lhash, DES, etc., code; not just the SSL code.  The SSL documentation
+included with this distribution is covered by the same copyright terms
+except that the holder is Tim Hudson (tjhcryptsoft.com).
+
+Copyright remains Eric Young's, and as such any Copyright notices in
+the code are not to be removed.
+If this package is used in a product, Eric Young should be given attribution
+as the author of the parts of the library used.
+This can be in the form of a textual message at program startup or
+in documentation (online or textual) provided with the package.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+1.  Redistributions of source code must retain the copyright
+    notice, this list of conditions and the following disclaimer.
+2.  Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in the
+    documentation and/or other materials provided with the distribution.
+3.  All advertising materials mentioning features or use of this software
+    must display the following acknowledgement:
+    "This product includes cryptographic software written by
+     Eric Young (eaycryptsoft.com)"
+    The word 'cryptographic' can be left out if the rouines from the library
+    being used are not cryptographic related :-).
+4.  If you include any Windows specific code (or a derivative thereof) from
+    the apps directory (application code) you must include an acknowledgement:
+    "This product includes software written by Tim Hudson (tjhcryptsoft.com)"
+
+THIS SOFTWARE IS PROVIDED BY ERIC YOUNG \`\`AS IS'' AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+The licence and distribution terms for any publically available version or
+derivative of this code cannot be changed.  i.e. this code cannot simply be
+copied and put under another distribution licence
+[including the GNU Public Licence.]
+
+## PostgreSQL License
+
+PostgreSQL Database Management System
+(formerly known as Postgres, then as Postgres95)
+
+Portions Copyright © 1996-2020, The PostgreSQL Global Development Group
+
+Portions Copyright © 1994, The Regents of the University of California
+
+Permission to use, copy, modify, and distribute this software and its
+documentation for any purpose, without fee, and without a written agreement
+is hereby granted, provided that the above copyright notice and this paragraph
+and the following two paragraphs appear in all copies.
+
+IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR
+DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING
+LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION,
+EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING,
+BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS,
+AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE,
+SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.