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 1lKWwz-0006xX-Ia for pgsql-docs@arkaria.postgresql.org; Fri, 12 Mar 2021 01:50:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lKWwy-0001ZL-GA for pgsql-docs@arkaria.postgresql.org; Fri, 12 Mar 2021 01:50:48 +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 1lKWwy-0001ZE-Ak for pgsql-docs@lists.postgresql.org; Fri, 12 Mar 2021 01:50:48 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lKWww-000389-Av for pgsql-docs@lists.postgresql.org; Fri, 12 Mar 2021 01:50:47 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 12C1oiCn2406384; Thu, 11 Mar 2021 20:50:44 -0500 From: Tom Lane To: Alex cc: Tatsuo Ishii , pgsql-docs@lists.postgresql.org Subject: Re: Invalid idle_in_transaction_session_timeout data type In-reply-to: References: <11783b8644ae5.7f3aa1e3b18b4.ref@yahoo.com> <11783b8644ae5.7f3aa1e3b18b4@yahoo.com> <20210311.211047.1106690547580793701.t-ishii@gmail.com> <2294219.1615479605@sss.pgh.pa.us> Comments: In-reply-to Alex message dated "Thu, 11 Mar 2021 21:34:31 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2406382.1615513844.1@sss.pgh.pa.us> Date: Thu, 11 Mar 2021 20:50:44 -0500 Message-ID: <2406383.1615513844@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alex writes: > The following changes would make docs clear: > work_mem (numeric with memory unit) > statement_timeout (numeric with time unit) I'm not sure about "clear", but I am sure that'd be inaccurate. We have integer GUCs and float8 GUCs, but no numeric GUCs. I do not see a useful purpose in obscuring that distinction. I could see using a couple more words than I suggested before: work_mem (integer, units of kilobytes) regards, tom lane