Compatibility
-
+
SQL92
diff --git a/doc/src/sgml/ref/create_user.sgml b/doc/src/sgml/ref/create_user.sgml
index ba389aebe76..2fb981b4d55 100644
--- a/doc/src/sgml/ref/create_user.sgml
+++ b/doc/src/sgml/ref/create_user.sgml
@@ -1,5 +1,5 @@
@@ -75,7 +75,8 @@ CREATE USER username
Sets the user's password. If you do not plan to use password
authentication you can omit this option, otherwise the user
won't be able to connect to a password-authenticated server.
- See pg_hba.conf(5) or the administrator's guide for details on
+ See the chapter on client authentication in the
+ Administrator's Guide for details on
how to set up authentication mechanisms.
diff --git a/doc/src/sgml/ref/set.sgml b/doc/src/sgml/ref/set.sgml
index 044cf8fd65b..7f36aae9d78 100644
--- a/doc/src/sgml/ref/set.sgml
+++ b/doc/src/sgml/ref/set.sgml
@@ -1,5 +1,5 @@
@@ -392,13 +392,19 @@ SELECT CURRENT_TIMESTAMP AS today;
Compatibility
-
- The second syntax shown above (SET TIME ZONE)
- attempts to mimic SQL92. However, SQL allows
- only numeric time zone offsets. All other parameter settings as
- well as the first syntax shown above are a
- Postgres extension.
-
+
+
+ SQL92
+
+
+
+ The second syntax shown above (SET TIME ZONE)
+ attempts to mimic SQL92. However, SQL allows
+ only numeric time zone offsets. All other parameter settings as
+ well as the first syntax shown above are a
+ Postgres extension.
+
+
diff --git a/doc/src/sgml/ref/set_constraints.sgml b/doc/src/sgml/ref/set_constraints.sgml
index 3cdb5d67a21..af8bfcb60ec 100644
--- a/doc/src/sgml/ref/set_constraints.sgml
+++ b/doc/src/sgml/ref/set_constraints.sgml
@@ -1,4 +1,4 @@
-
+
SET CONSTRAINTS
@@ -44,10 +44,33 @@ SET CONSTRAINTS { ALL | constraint
-
+ Compatibility
-
- SQL92, SQL99
-
+
+
+ SQL92, SQL99
+
+
+ SET CONSTRAINT is defined in
+ SQL92 and SQL99.
+
+
+
+
diff --git a/doc/src/sgml/ref/set_session.sgml b/doc/src/sgml/ref/set_session.sgml
new file mode 100644
index 00000000000..b542d6646e8
--- /dev/null
+++ b/doc/src/sgml/ref/set_session.sgml
@@ -0,0 +1,91 @@
+
+
+
+
+ SET
+ SQL - Language Statements
+
+
+ SET SESSION CHARACTERISTICS
+ Set per-session run-time parameters
+
+
+
+SET SESSION CHARACTERISTICS TRANSACTION ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE }
+SET SESSION CHARACTERISTICS TIME ZONE { 'timezone' | LOCAL | DEFAULT }
+
+
+
+
+ Description
+
+ SET SESSION CHARACTERISTICS changes the run-time
+ environment for the entire SQL
+ session. Currently, transaction isolation level and time zone can
+ be specified by this command.
+
+
+
+ Use to show the
+ current setting of a parameters.
+
+
+
+ Refer to
+ and to for more
+ information on allowed parameters.
+
+
+
+
+ Examples
+
+
+ Set the timezone for Berkeley, California, using double quotes to
+ preserve the uppercase attributes of the time zone specifier (note
+ that the date/time format is ISO here):
+
+
+SET SESSION CHARACTERISTICS TIME ZONE "PST8PDT";
+SELECT CURRENT_TIMESTAMP AS today;
+
+ today
+------------------------
+ 1998-07-14 07:41:21-07
+
+
+
+
+
+ Compatibility
+
+
+ SQL99
+
+
+ SET SESSION is defined in
+ SQL99.
+
+
+
+
+
+
diff --git a/doc/src/sgml/ref/set_transaction.sgml b/doc/src/sgml/ref/set_transaction.sgml
index e5de2e7f5b4..a5ca5fac1ff 100644
--- a/doc/src/sgml/ref/set_transaction.sgml
+++ b/doc/src/sgml/ref/set_transaction.sgml
@@ -1,7 +1,7 @@
-
+
- SET TRANSACTION
+ SET TRANSACTIONSQL - Language Statements
@@ -66,28 +66,44 @@ SET TRANSACTION ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE }
-
+ Compatibility
-
- SQL92, SQL99
-
+
+ SQL92, SQL99
-
- SERIALIZABLE is the default level in SQL.
- Postgres does not provide the isolation levels and . Because
- of multi-version concurrency control, the serializable level is not
- truly serializable. See the User's Guide for
- details.
-
+
+ SERIALIZABLE is the default level in SQL.
+ Postgres does not provide the isolation levels and . Because
+ of multi-version concurrency control, the serializable level is not
+ truly serializable. See the User's Guide for
+ details.
+
-
- In SQL there are two other transaction
- characteristics that can be set with this command: whether the
- transaction is read-only and the size of the diagnostics area.
- Neither of these concepts are supported in Postgres.
-
+
+ In SQL there are two other transaction
+ characteristics that can be set with this command: whether the
+ transaction is read-only and the size of the diagnostics area.
+ Neither of these concepts are supported in Postgres.
+
+
+