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-11 16:20:05 |
Message-ID: | 2294219.1615479605@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-docs |
[ redirecting to pgsql-docs ]
Alex <cdalxndr(at)yahoo(dot)com> writes:
> In my opinion, it would be more clear if "Numeric with Unit" would be
> specified on that property documentation, so that I can search more about
> what that means (eventually a link pointing to details).
> I saw "(integer)" so I assumed `show idle_in_transaction_session_timeout `
> will return an integer.
This complaint isn't totally without merit. I wonder whether there is
any value in listing a unit-ized GUC's default unit as part of the
type info, so that we'd have entries like
work_mem (integer, kilobytes)
statement_timeout (integer, milliseconds)
That'd both provide some concrete info about which unit applies,
and cue unwary users that there might be more to it than just a
number.
I'm not sure whether this could replace the existing boilerplate
phrases about "If this value is specified without units, it is taken
as kilobytes", but it's sure more compact.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-03-11 16:37:11 | Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |
Previous Message | Regina Obe | 2021-03-11 16:15:36 | RE: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |
From | Date | Subject | |
---|---|---|---|
Next Message | Alex | 2021-03-11 21:34:31 | Re: Invalid idle_in_transaction_session_timeout data type |
Previous Message | Alex | 2021-03-11 12:23:29 | Re: Invalid idle_in_transaction_session_timeout data type |