Merge pull request #1851 from EnterpriseDB/release/2021-09-15

Release/2021 09 15

product_docs/docs/edbcloud/beta/getting_started/03_create_cluster.mdx

@@ -26,9 +26,9 @@ To create a cluster:
 8. Select the region where you want your cluster to be deployed in the **Region** field. For the best performance, EDB typically recommends that this region should be the same as other resources you have that communicate with your cluster.
 9. Enable or disable high availablity using the **High Availability** slide button. High availability is enabled by default. When high availability is enabled, clusters are configured with one primary and two replicas with synchronous streaming replication. Clusters are configured across availability zones in regions with availability zones. When high availability is disabled, only one instance is provisioned. See [Supported Architectures](../overview/02_high_availibility) for more information.
 10. In the the **Instance Type** section, select the number of vCPUs and amount of memory you desire.
-11. In the **Storage** field, select the type and amount of storage needed for your cluster.
+11. In the **Storage** field, select the type and amount of storage needed for your cluster. 
    !!! Note
-       Azure premium storage is the only option for the Preview.
+       EDB Cloud currently supports Azure Premium SSD storage types. See [the Azure documentation](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssd) for more information.
 12. (Optional) Expand the **Advanced Customization** section, to specify:
     1.  The desired amount of connections your cluster allows for other applications. You can either enter the amount or use the arrows. The default is 100.
 

product_docs/docs/epas/11/epas_compat_sql/36_create_table.mdx

@@ -15,7 +15,7 @@ legacyRedirectsGenerated:
 **Synopsis**
 
 ```text
-CREATE [ GLOBAL TEMPORARY ] TABLE <table_name> (
+CREATE [ GLOBAL TEMPORARY | UNLOGGED ] TABLE <table_name> (
   { <column_name> <data_type> [ DEFAULT <default_expr> ]
   [ <column_constraint> [ ... ] ] | <table_constraint> } [, ...]
   )
@@ -75,6 +75,10 @@ There are two ways to define constraints: table constraints and column constrain
 
  If specified, the table is created as a temporary table. Temporary tables are automatically dropped at the end of a session, or optionally at the end of the current transaction (see `ON COMMIT` below). Existing permanent tables with the same name are not visible to the current session while the temporary table exists, unless they are referenced with schema-qualified names. In addition, temporary tables are not visible outside the session in which it was created. (This aspect of global temporary tables is not compatible with Oracle databases.) Any indexes created on a temporary table are automatically temporary as well.
 
+`UNLOGGED`
+
+ If specified, the table is created as an unlogged table. The data written to unlogged tables is not written to the write-ahead log (WAL), making them faster than an ordinary table. Indexes created on an unlogged table are automatically unlogged. The contents of an unlogged table are not replicated to a standby server. The unlogged table is automatically truncated after a crash or shutdown.
+
 `table_name`
 
  The name (optionally schema-qualified) of the table to be created.

product_docs/docs/epas/12/epas_compat_sql/36_create_table.mdx

@@ -15,7 +15,7 @@ legacyRedirectsGenerated:
 **Synopsis**
 
 ```text
-CREATE [ GLOBAL TEMPORARY ] TABLE <table_name> (
+CREATE [ GLOBAL TEMPORARY | UNLOGGED ] TABLE <table_name> (
   { <column_name> <data_type> [ DEFAULT <default_expr> ]
   [ <column_constraint> [ ... ] ] | <table_constraint> } [, ...]
   )
@@ -75,6 +75,10 @@ There are two ways to define constraints: table constraints and column constrain
 
  If specified, the table is created as a temporary table. Temporary tables are automatically dropped at the end of a session, or optionally at the end of the current transaction (see `ON COMMIT` below). Existing permanent tables with the same name are not visible to the current session while the temporary table exists, unless they are referenced with schema-qualified names. In addition, temporary tables are not visible outside the session in which it was created. (This aspect of global temporary tables is not compatible with Oracle databases.) Any indexes created on a temporary table are automatically temporary as well.
 
+`UNLOGGED`
+
+ If specified, the table is created as an unlogged table. The data written to unlogged tables is not written to the write-ahead log (WAL), making them faster than an ordinary table. Indexes created on an unlogged table are automatically unlogged. The contents of an unlogged table are not replicated to a standby server. The unlogged table is automatically truncated after a crash or shutdown.
+
 `table_name`
 
  The name (optionally schema-qualified) of the table to be created.

product_docs/docs/epas/13/epas_compat_sql/36_create_table.mdx

@@ -15,7 +15,7 @@ legacyRedirectsGenerated:
 **Synopsis**
 
 ```text
-CREATE [ GLOBAL TEMPORARY ] TABLE <table_name> (
+CREATE [ GLOBAL TEMPORARY | UNLOGGED ] TABLE <table_name> (
   { <column_name> <data_type> [ DEFAULT <default_expr> ]
   [ <column_constraint> [ ... ] ] | <table_constraint> } [, ...]
   )
@@ -80,6 +80,10 @@ There are two ways to define constraints: table constraints and column constrain
 
  If specified, the table is created as a temporary table. Temporary tables are automatically dropped at the end of a session, or optionally at the end of the current transaction (see `ON COMMIT` below). Existing permanent tables with the same name are not visible to the current session while the temporary table exists, unless they are referenced with schema-qualified names. In addition, temporary tables are not visible outside the session in which it was created. (This aspect of global temporary tables is not compatible with Oracle databases.) Any indexes created on a temporary table are automatically temporary as well.
 
+`UNLOGGED`
+
+ If specified, the table is created as an unlogged table. The data written to unlogged tables is not written to the write-ahead log (WAL), making them faster than an ordinary table. Indexes created on an unlogged table are automatically unlogged. The contents of an unlogged table are not replicated to a standby server. The unlogged table is automatically truncated after a crash or shutdown.
+
 `table_name`
 
  The name (optionally schema-qualified) of the table to be created.