From: Vik Fearing <vik@postgresfriends.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Alex <cdalxndr@yahoo.com>
Cc: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Invalid idle_in_transaction_session_timeout data type
Date: Fri, 12 Mar 2021 07:26:19 +0100
Message-ID: <8ea2c5ee-d2ad-e32c-3c49-5fa77b9090f2@postgresfriends.org> (raw)
In-Reply-To: <2406383.1615513844@sss.pgh.pa.us>
References: <11783b8644ae5.7f3aa1e3b18b4.ref@yahoo.com>
<11783b8644ae5.7f3aa1e3b18b4@yahoo.com>
<20210311.211047.1106690547580793701.t-ishii@gmail.com>
<c0e06b0927222.cf42cafcd23b9@yahoo.com>
<2294219.1615479605@sss.pgh.pa.us>
<eb11dc69fdccb.1f6615ec2e0de@yahoo.com>
<2406383.1615513844@sss.pgh.pa.us>
On 3/12/21 2:50 AM, Tom Lane wrote:
> Alex <cdalxndr@yahoo.com> 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)
This gets a little more complicated with:
shared_buffers (integer, units of BLOCKSZ)
--
Vik Fearing
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-docs@postgresql.org
Cc: vik@postgresfriends.org, tgl@sss.pgh.pa.us, cdalxndr@yahoo.com, ishii@sraoss.co.jp, pgsql-docs@lists.postgresql.org
Subject: Re: Invalid idle_in_transaction_session_timeout data type
In-Reply-To: <8ea2c5ee-d2ad-e32c-3c49-5fa77b9090f2@postgresfriends.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