On 3/12/21 2:50 AM, Tom Lane wrote:
> 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 n
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 i
The following changes would make docs clear:
work_mem (numeric with memory unit)
statement_timeout (numeric with time unit)
,where "numeric with memory unit" and "numeric with time unit" are links
that point to "https://www.postgresql.org/docs/current/config-setting.html";
Tom Lane wrote:
[ redire
[ redirecting to pgsql-docs ]
Alex 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_
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/progress-reporting.html
Description:
The "vacuuming indexes" documentation has:
"If a table has any indexes, this will happen at least once per vacuum,
after the heap has been completely
