We had documentation of default_transaction_isolation et al,
but for some reason not of transaction_isolation et al.
AFAICS this is just an ancient oversight, so repair.
Per bug #17077 from Yanliang Lei.
Discussion: https://postgr.es/m/17077-
ade8e166a01e1374@postgresql.org
- This parameter enables compression of WAL using the specified
+ This parameter enables compression of WAL using the specified
compression method.
When enabled, the
PostgreSQL
server compresses full page images written to WAL when
+
+ transaction_isolation (enum)
+
+
transaction isolation level
+
+
+
transaction_isolation configuration parameter
+
+
+
+ This parameter reflects the current transaction's isolation level.
+ At the beginning of each transaction, it is set to the current value
+ of .
+ Any subsequent attempt to change it is equivalent to a
+ linkend="sql-set-transaction"/> command.
+
+
+
+
+
+ transaction_read_only (boolean)
+
+ setting default
+
+
+
transaction_read_only configuration parameter
+
+
+
+ This parameter reflects the current transaction's read-only status.
+ At the beginning of each transaction, it is set to the current value
+ of .
+ Any subsequent attempt to change it is equivalent to a
+ linkend="sql-set-transaction"/> command.
+
+
+
+
+
+ transaction_deferrable (boolean)
+
+ setting default
+
+
+
transaction_deferrable configuration parameter
+
+
+
+ This parameter reflects the current transaction's deferrability status.
+ At the beginning of each transaction, it is set to the current value
+ of .
+ Any subsequent attempt to change it is equivalent to a
+ linkend="sql-set-transaction"/> command.
+
+
+
+
session_replication_role (enum)
PostgreSQL will automatically remove
temporary files after a backend crash. If disabled, the files will be
retained and may be used for debugging, for example. Repeated crashes
- may however result in accumulation of useless files. This parameter
+ may however result in accumulation of useless files. This parameter
can only be set in the postgresql.conf file or on
the server command line.
- The session default transaction modes can also be set by setting the
+ The session default transaction modes can also be set or examined via the
configuration parameters ,
, and
.
ALTER DATABASE, etc. Consult
for more information.
+
+ The current transaction's modes can similarly be set or examined via the
+ configuration parameters ,
+ , and
+ . Setting one of these
+ parameters acts the same as the corresponding SET
+ TRANSACTION option, with the same restrictions on when it can
+ be done. However, these parameters cannot be set in the configuration
+ file, or from any source other than live SQL.
+