From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | 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 01:50:44 |
Message-ID: | 2406383.1615513844@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-docs |
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)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Vik Fearing | 2021-03-12 06:26:19 | Re: Invalid idle_in_transaction_session_timeout data type |
Previous Message | Alex | 2021-03-11 21:34:31 | Re: Invalid idle_in_transaction_session_timeout data type |
From | Date | Subject | |
---|---|---|---|
Next Message | Vik Fearing | 2021-03-12 06:26:19 | Re: Invalid idle_in_transaction_session_timeout data type |
Previous Message | Alex | 2021-03-11 21:34:31 | Re: Invalid idle_in_transaction_session_timeout data type |