Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lKK9X-000550-BP for pgsql-bugs@arkaria.postgresql.org; Thu, 11 Mar 2021 12:10:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lKK9W-0003po-6E for pgsql-bugs@arkaria.postgresql.org; Thu, 11 Mar 2021 12:10:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lKK9W-0003pg-00 for pgsql-bugs@lists.postgresql.org; Thu, 11 Mar 2021 12:10:54 +0000 Received: from mx0b-0050f201.pphosted.com ([148.163.141.54]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lKK9R-0005AB-Ar for pgsql-bugs@lists.postgresql.org; Thu, 11 Mar 2021 12:10:52 +0000 Received: from pps.filterd (m0203370.ppops.net [127.0.0.1]) by mx0b-0050f201.pphosted.com (8.16.1.2/8.16.1.2) with SMTP id 12B9YX9f013265 for ; Thu, 11 Mar 2021 21:10:48 +0900 Received: from sraihe.sra.co.jp (sraihe.sra.co.jp [221.255.117.38]) by mx0b-0050f201.pphosted.com with ESMTP id 3760282qfy-1 for ; Thu, 11 Mar 2021 21:10:48 +0900 Received: from srascb.sra.co.jp (srascb [133.137.8.65]) by sraihe.sra.co.jp (Postfix) with ESMTP id A2DC12A684B for ; Thu, 11 Mar 2021 21:10:47 +0900 (JST) Received: from sranhm.sra.co.jp (osspc25 [133.137.174.97]) by srascb.sra.co.jp (Postfix) with ESMTP id 85FE95800E4 for ; Thu, 11 Mar 2021 21:10:47 +0900 (JST) Received: from localhost (sraihb-hub.sra.co.jp [133.137.8.6]) by sranhm.sra.co.jp (Postfix) with ESMTP id 5980FA158C; Thu, 11 Mar 2021 21:10:47 +0900 (JST) Date: Thu, 11 Mar 2021 21:10:47 +0900 (JST) Message-Id: <20210311.211047.1106690547580793701.t-ishii@gmail.com> To: cdalxndr@yahoo.com Cc: pgsql-bugs@lists.postgresql.org Subject: Re: Invalid idle_in_transaction_session_timeout data type From: Tatsuo Ishii In-Reply-To: <11783b8644ae5.7f3aa1e3b18b4@yahoo.com> References: <11783b8644ae5.7f3aa1e3b18b4.ref@yahoo.com> <11783b8644ae5.7f3aa1e3b18b4@yahoo.com> X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=9919 signatures=668683 X-Proofpoint-Spam-Details: rule=spam_low_notspam policy=spam_low score=0 mlxlogscore=937 spamscore=0 bulkscore=0 phishscore=0 adultscore=0 lowpriorityscore=0 suspectscore=0 clxscore=1034 malwarescore=0 mlxscore=0 impostorscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2103110066 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > https://www.postgresql.org/docs/13/runtime-config-client.html > shows > that `idle_in_transaction_session_timeout` is integer, bug you can set > text values '30s' and `show idle_in_transaction_session_timeout` > returns `30s` not an integer. > Documentation should be updated to include this data field format. The documentation says: "If this value is specified without units, it is taken as milliseconds." If the value is specified with units, it follows the rule described here: https://www.postgresql.org/docs/13/config-setting.html "Numeric with Unit: Some numeric parameters have an implicit unit, because they describe quantities of memory or time. The unit might be bytes, kilobytes, blocks (typically eight kilobytes), milliseconds, seconds, or minutes." : : "Valid time units are us (microseconds), ms (milliseconds), s (seconds), min (minutes), h (hours), and d (days)." So I see no problem with the document. Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp