Merge pull request #1847 from EnterpriseDB/bugfix/epas/df-263-unlogge…

…d-parameter

DF-263 UNLOGGED Parameter added

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.