Skip to content

Commit

Permalink
Merge pull request #4113 from EnterpriseDB/release/2023-05-19
Browse files Browse the repository at this point in the history
Release: 2023-05-19
  • Loading branch information
drothery-edb authored May 19, 2023
2 parents 5de0527 + a0a4ed9 commit bd11606
Show file tree
Hide file tree
Showing 136 changed files with 80 additions and 25 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -32,13 +32,17 @@ To connect your cloud:
The command checks for cloud account readiness and displays the results.

1. If the following readiness checks aren't met, see [Configure your Azure subscription](/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure#configure-your-azure-subscription) to manually configure your cloud:
- Are the necessary Azure resource providers registered for your subscription?

- Is there a restriction on SKUs for the standard Esv3 family and standard D2_v4 VM size?
- Is the limit on the number of vCPU and public IP addresses in your region enough for your clusters?
- Are the necessary Azure resource providers registered for your subscription?

- Is there a restriction on SKUs for the standard Esv3 family and standard D2_v4 VM size?
- Is the limit on the number of vCPU and public IP addresses in your region enough for your clusters?

If the cloud readiness checks pass, your cloud account is successfully set up.

!!! Note
At this point, you can't change the Azure subscription as you have already provided the Azure subscription ID.

1. Connect your cloud account to BigAnimal:

```shell
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -134,19 +134,29 @@ The return type is the same as the argument types. All arguments must have the s

### Examples

This example computes a bonus for noncommissioned employees. If an employee is a commissioned employee,
this expression returns the employee's commission. If the employee isn't a commissioned employee, that is, their commission is `NULL`, this expression returns a bonus that is 10% of their salary.
This example computes a bonus for noncommissioned employees. If an employee is a commissioned employee this expression returns the employee's commission. If the employee isn't a commissioned employee, that is, their commission is `NULL`, this expression returns a bonus that is 10% of their salary.

```text
bonus = NVL(emp.commission, emp.salary * .10)
```
```text
bonus = NVL(emp.commission, emp.salary * .10)
```

In this example, the type of `1` is numeric and the type of `''` is considered as unknown. Therefore PostgreSQL decides that the common type is numeric. It tries to interpret the empty string as a numeric value, which produces the indicated error:

```sql
edb=# select nvl('',1);
ERROR: invalid input syntax for type numeric: ""
```

In this example, the type of 1 is numeric and the type of '' is considered as unknown. Therefore PostgreSQL decides that the common type is numeric. It tries to interpret the empty string as a numeric value, which produces the indicated error:
In this example, if `33` is type casted to double precision, it converts to double precision and returns the value as double precision. If `33` is type casted to numeric, it converts to numeric and returns the value as numeric.

```sql
edb=# select nvl('',1);
ERROR: invalid input syntax for type numeric: ""
```
```sql
edb=# select NVL(33::double precision,0), pg_typeof(NVL(33::double precision,0)), pg_typeof(NVL(33::numeric,0));
__OUTPUT__
nvl | pg_typeof | pg_typeof
-----+------------------+-----------
33 | double precision | numeric
(1 row)
```

## NVL2

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ EDB Postgres Advanced Server 15.2.0 includes the following enhancements and bug
| Enhancement | Added support for WHERE clause to the UPDATE and INSERT of MERGE command for Oracle compatibility.| Oracle compatibility |
| Enhancement | Added the HTP and HTF packages to built-in packages for Oracle compatibility. | Oracle compatibility |
| Enhancement | 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 | The NVL function now accepts double precision data type arguments. | |
| Enhancement | EDB Postgres Advanced Server now skips IN/OUT/IN OUT modifiers in the USING expression. A USING clause in EXECUTE IMMEDIATE supports passing parameters to embedded SPL blocks. However, these parameters are treated as IN OUT only, and there was previously no way to specify whether the parameter is IN, OUT, or IN OUT. To ease migration from Oracle, these modifiers are now skipped at the beginning of the expression whenever possible. | Oracle compatibility |
| Enhancement | Added the FORMAT_ERROR_STACK() and FORMAT_ERROR_BACKTRACE() functions to the DBMS_UTILITY package. These functions are used in a stored procedure, function, or package to return the current exception name. These functions are useful for debugging and logging purposes. | |
| Enhancement | Added Oracle-compatible UPDATE..SET ROW syntax support. UPDATE changes the values of the specified columns in all rows that satisfy the condition. Only the columns being modify are mentioned in the SET clause. Columns not being modified explicitly retain their previous values. The SET ROW clause enables you to update a target record using a record-type variable or row-type objects. The record or row used must have compatible data types with table's columns in order. | Oracle compatibility |
Expand Down
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
title: "EDB OCL Connector"
directoryDefaults:
description: "EDB OCL Connector Version 14.1.0.1 Documentation and release notes."
description: "EDB OCL Connector Version 15.1.0.1 Documentation and release notes."
navigation:
- 01_ocl_release_notes
- ocl_rel_notes
- 02_supported_platforms
- 03_libpq_compatibility
- installing
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: "Release notes"
title: "Version 15.2.0.1"
---
The EDB OCL Connector provides an API similar to the Oracle Call Interface.

Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
title: "Version 15.2.0.2"
---
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.2 include:

| Type | Description |
| ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Bug fix | Fixed a performance issue when reading approximately 250,000 rows using the Perforce DBLink abstraction library. [Support ticket: #85251] |
| Bug fix | Fixed an issue where the β€œValue accessor mismatch" error occurred when retrieving the value of an INTEGER or NUMBER datatype using the Perforce DBLink abstraction library. Support ticket: 85247] |
| Bug fix | Fixed an OCI Date Issue where the date returned was always epoch (1970-1-1). [Support ticket: 88425] |
| Bug fix | Fixed an issue where data insert was failing if parameter names contained the same prefix. [Support ticket: 91805] |
17 changes: 17 additions & 0 deletions product_docs/docs/ocl_connector/15/ocl_rel_notes/index.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: "EDB ODBC Connector release notes"
navTitle: Release Notes
navigation:
- 15.2.0.2_ocl_release_notes
- 01_ocl_release_notes
---

The EDB ODBC connector documentation describes the latest version of the EDB ODBC connector.

Release notes describe what's new in a release. When a minor or patch release introduces new functionality, indicators in the content identify the version that introduced the new feature.

| Version | Release date |
| ----------------------------------------- | ------------ |
| [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 |

2 changes: 1 addition & 1 deletion product_docs/docs/pgd/5/nodes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -510,7 +510,7 @@ node subscribing to each node. In this case, no LCR files are written.
Even though the decoding worker is enabled for a PGD group, following
GUCs control the production and use of LCR per node. By default
these are `false`. For production and use of LCRs, enable the
decoding worker for the PGD group and set these GUCs to to `true` on each of the nodes in the PGD group.
decoding worker for the PGD group and set these GUCs to `true` on each of the nodes in the PGD group.

- `bdr.enable_wal_decoder` — When turned `false`, all WAL
senders using LCRs restart to use WAL directly. When `true`
Expand Down
8 changes: 5 additions & 3 deletions product_docs/docs/pgd/5/tpa.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -49,12 +49,12 @@ The available configuration options include:
| ------------------ | ----------- |
| `--architecture` | Required. Set to `PGD-Always-ON` for EDB Postgres Distributed deployments. |
| `–-postgresql <version>` <br/> or <br/> `--edb-postgres-advanced <version>` <br/> or <br/> `--edb-postgres-extended <version>` | Required. Specifies the distribution and version of Postgres to use. For more details, see [Cluster configuration: Postgres flavour and version](/tpa/latest/tpaexec-configure/#postgres-flavour-and-version). |
| `--redwood` or `--noredwood` | Required when `--edb-postgres-advanced` flag is present. Specifies whether Oracle database compatibility features are desired. |
| `--redwood` or `--no-redwood` | Required when `--edb-postgres-advanced` flag is present. Specifies whether Oracle database compatibility features are desired. |
| `--location-names l1 l2 l3` | Required. Specifies the number and name of the locations PGD will be deployed to. |
| `--data-nodes-per-location N` | Specifies number of data nodes per location. Default 3. |
| `--add-witness-node-per-location` | For even number of data nodes per location, this will add witness node to allow for local consensus. This is enabled by default for 2 data node locations. |
| `--add-proxy-nodes-per-location` | Whether to separate PGD-Proxies from data nodes, and how many to configure. By default one proxy is configured and cohosted for each data node. |
| `--pgd-proxy-routing global|local` | Should PGD-proxy routing be handled on a global or local (per location) basis. |
| `--pgd-proxy-routing global\|local` | Should PGD-proxy routing be handled on a global or local (per location) basis. |
| `--add-witness-only-location loc` | This designates one of the cluster location as witness only (no data nodes will be present in that location). |
| `--enable-camo` | Sets up CAMO pair in each location. This only works with 2 data node per location. |

Expand All @@ -66,14 +66,16 @@ For example:
[tpa]$ tpaexec configure ~/clusters/speedy \
--architecture PGD-Always-ON \
--platform aws \
--edb-postgres-advanced 15 \
--redwood \
--location-names eu-west-1 eu-north-1 eu-central-1 \
--data-nodes-per-location 3 \
--pgd-proxy-routing global
```

The first argument must be the cluster directory, for example, `speedy` or `~/clusters/speedy` (the cluster is named `speedy` in both cases). We recommend that you keep all your clusters in a common directory, for example, `~/clusters`. The next argument must be `--architecture` to select an architecture, followed by options.

The command creates a directory named ~/clusters/speedy and generates a configuration file named `config.yml` that follows the layout of the PGD-Always-ON architecture. You can use the `tpaexec configure --architecture PGD-Always-ON --help` command to see what values are supported for the configuration options in this architecture.
The command creates a directory named ~/clusters/speedy and generates a configuration file named `config.yml` that follows the layout of the PGD-Always-ON architecture. You can use the `tpaexec configure --architecture PGD-Always-ON --help` command to see what values are supported for the configuration options in this architecture. In the example , the options select an AWS deployment (`--platform aws`) with EDB Postgres Advanced, version 15 and Oracle compatibility (`--edb-postgres-advanced 15` and `--redwood`) with three locations (`--location-names eu-west-1 eu-north-1 eu-central-1`) and three data nodes at each location (`--data-nodes-per-location 3`). The last option sets the proxy routing policy to global (`--pgd-proxy-routing global`).

### Common configuration options

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -31,10 +31,14 @@ helm upgrade --dependency-update \
--namespace pgd-operator-system \
--create-namespace \
edb/edb-postgres-distributed-for-kubernetes \
--set image.imageCredentials.username=${USERNAME} \
--set image.imageCredentials.password=${PASSWORD}
--set image.imageCredentials.username=${REPO} \
--set image.imageCredentials.password=${TOKEN}
```

Set `REPO` to either `k8s_enterprise_pgd` or `k8s_standard_pgd` depending on the EDB software subscription purchased and Postgres distribution to be installed. Use `k8s_enterprise_pgd` if you are a trialist or preview user.

Set `TOKEN` to the repository token for your EDB account. You can obtain this by going to the [Repos page](https://www.enterprisedb.com/repos-downloads) on the EDB website, signing in (if necessary) and then and displaying the EDB Repos 2.0 token using the Reveal Token button or copying it using the Copy button.

For further details on the Helm chart, please refer to the
[Helm chart repo](https://github.com/EnterpriseDB/edb-postgres-for-kubernetes-charts).

Expand Down Expand Up @@ -148,4 +152,4 @@ region-c 0 1 PGDGroup - Healthy
### Upgrades

TODO
-->
-->
2 changes: 1 addition & 1 deletion product_docs/docs/tpa/23/architecture-BDR-Always-ON.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ You can list all available options using the help command.
tpaexec configure --architecture BDR-Always-ON --help
```

The table below describes the mandatory options for BDR-Always-ON
The tables below describe the mandatory options for BDR-Always-ON
and additional important options.
More detail on the options is provided in the following section.

Expand Down
2 changes: 1 addition & 1 deletion product_docs/docs/tpa/23/reference/distributions.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ legacy platform is likely to work as long as you have access to the
necessary packages, but this is not considered a supported use of TPA
and is not suitable for production use.

!!! Note
!!!Note
This page is about distribution support on target instances that you
are deploying *to*, not about the system you are running TPA *from*.
See the [installation instructions](../INSTALL/#distribution-support) for
Expand Down
4 changes: 4 additions & 0 deletions static/_redirects
Original file line number Diff line number Diff line change
Expand Up @@ -170,6 +170,10 @@
/docs/odbc_connector/12.0.0.1/* /docs/odbc_connector/latest/ 301
/docs/odbc_connector/12.2.0.1/* /docs/odbc_connector/latest/ 301
# Collapsed versions
/docs/ocl_connector/12.1.2.1/* /docs/ocl_connector/12/:splat/ 301
/docs/ocl_connector/13.1.4.2/* /docs/ocl_connector/13/:splat/ 301
/docs/ocl_connector/14.1.0.1/* /docs/ocl_connector/14/:splat 301
/docs/ocl_connector/15.2.0.1/* /docs/ocl_connector/15/:splat 301
/docs/mysql_data_adapter/2.7.0/* /docs/mongo_data_adapter/2/:splat 301
/docs/mysql_data_adapter/2.6.0/* /docs/mongo_data_adapter/2/:splat 301
/docs/mysql_data_adapter/2.5.5/* /docs/mongo_data_adapter/2/:splat 301
Expand Down

2 comments on commit bd11606

@github-actions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-actions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸŽ‰ Published on https://edb-docs.netlify.app as production
πŸš€ Deployed on https://6467c4629488a754fa70325f--edb-docs.netlify.app

Please sign in to comment.