From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alex <cdalxndr(at)yahoo(dot)com> |
Cc: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Invalid idle_in_transaction_session_timeout data type |
Date: | 2021-03-12 06:26:19 |
Message-ID: | 8ea2c5ee-d2ad-e32c-3c49-5fa77b9090f2@postgresfriends.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-docs |
On 3/12/21 2:50 AM, Tom Lane wrote:
> Alex <cdalxndr(at)yahoo(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | tomohiro hiramitsu | 2021-03-12 08:23:29 | Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table. |
Previous Message | Tom Lane | 2021-03-12 01:50:44 | Re: Invalid idle_in_transaction_session_timeout data type |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-03-12 15:03:17 | Re: Invalid idle_in_transaction_session_timeout data type |
Previous Message | Tom Lane | 2021-03-12 01:50:44 | Re: Invalid idle_in_transaction_session_timeout data type |