From: leiyanliang@highgo.com <leiyanliang@highgo.com>
To: leiyanliang@highgo.com <leiyanliang@highgo.com>
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17077: about three parameters in postgresql 13.3
Date: Sat, 17 Jul 2021 12:40:25 +0800
Message-ID: <202107171236202362593@highgo.com> (raw)
References: <17077-ade8e166a01e1374@postgresql.org>
I want to know: this bug report is a problem or not ?
From: PG Bug reporting form
Date: 2021-06-30 14:09
To: pgsql-bugs@lists.postgresql.org
CC: leiyanliang@highgo.com
Subject: BUG #17077: about three parameters in postgresql 13.3
The following bug has been logged on the website:
Bug reference: 17077
Logged by: yanliang lei
Email address: leiyanliang@highgo.com
PostgreSQL version: 13.3
Operating system: CentOS7.6
Description:
Three parameters are
'transaction_deferrable','transaction_isolation','transaction_read_only'。
in the following sql statement,there are three
parameters（'transaction_deferrable','transaction_isolation','transaction_read_only'）
[pg133@VM-0-8-centos ~]$ psql -d postgres
psql (13.3)
Type "help" for help.
postgres=# select * from pg_settings where name in
('transaction_deferrable','transaction_isolation','transaction_read_only');
name | setting | unit |
category |
short_desc |
extra_desc | c
ontext | vartype | source | min_val | max_val |
enumvals | boot_val | reset_val
| sourcefile | sourceline | pending_restart
------------------------+----------------+------+-------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+------------+--
-------+---------+----------+---------+---------+----------------------------------------------------------------------+----------------+----------------+------------+------------+-----------------
transaction_deferrable | off | | Client Connection Defaults
/ Statement Behavior | Whether to defer a read-only serializable transaction
until it can be executed with no possible serialization failures. |
| u
ser | bool | override | | |
| off | off
| | | f
transaction_isolation | read committed | | Client Connection Defaults
/ Statement Behavior | Sets the current transaction's isolation level.
|
| u
ser | enum | override | | | {serializable,"repeatable
read","read committed","read uncommitted"} | read committed | read committed
| | | f
transaction_read_only | off | | Client Connection Defaults
/ Statement Behavior | Sets the current transaction's read-only status.
|
| u
ser | bool | override | | |
| off | off
| | | f
(3 rows)
postgres=#
in the
https://www.postgresql.org/docs/current/runtime-config-client.html#RUNTIME-CONFIG-CLIENT-STATEMENT
there is no description about these three parameters。
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: leiyanliang@highgo.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17077: about three parameters in postgresql 13.3
In-Reply-To: <202107171236202362593@highgo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox