On 2019-03-14 14:10, Tom Lane wrote:
>> The portability is not something I'm concerned about, but Ditaa requires
>> Java, so that might annoy some people.
> Portability is something you *should* be concerned about. We want
> all patch submitters to be able to build the docs, else we'll forever
> b
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/progress-reporting.html
Description:
Replace "Whenever VACUUM is running" with "Whenever AUTOVACUUM is running"
The pg_stat_progress_vacuum view does not show VACUUM run manually.
Thanks
Peter Eisentraut writes:
> On 2019-03-11 15:50, Tom Lane wrote:
>> Ideally, we'd treat them much as we do for bison output files:
>> we'll supply them in tarballs but you'd better have the relevant
>> tools if you want to build docs from a git pull. However, that
>> may be assuming too much about
On 2019-03-11 15:50, Tom Lane wrote:
> Ideally, we'd treat them much as we do for bison output files:
> we'll supply them in tarballs but you'd better have the relevant
> tools if you want to build docs from a git pull. However, that
> may be assuming too much about the portability of the tools ..
