pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: leiyanliang@highgo.com
Subject: BUG #17077: about three parameters in postgresql 13.3
Date: Wed, 30 Jun 2021 06:09:48 +0000
Message-ID: <17077-ade8e166a01e1374@postgresql.org> (raw)

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。



view thread (7+ messages)  latest in thread

Message-ID: <17077-ade8e166a01e1374@postgresql.org>
Permalink:  ../17077-ade8e166a01e1374@postgresql.org/
Also on:    postgresql.org/message-id/17077-ade8e166a01e1374@postgresql.org

 · 

reply

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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, leiyanliang@highgo.com
  Subject: Re: BUG #17077: about three parameters in postgresql 13.3
  In-Reply-To: <17077-ade8e166a01e1374@postgresql.org>

* 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