Re: progress report for ANALYZE

From: Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp>
To: vignesh C <vignesh21(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: progress report for ANALYZE
Date: 2019-11-01 06:22:17
Message-ID: 7775f683-9512-326c-12e7-03975594e830@nttcom.co.jp_1
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi vignesh!

On 2019/09/17 20:51, vignesh C wrote:
> On Thu, Sep 5, 2019 at 2:31 AM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>>
>> There were some minor problems in v5 -- bogus Docbook as well as
>> outdated rules.out, small "git diff --check" complaint about whitespace.
>> This v6 (on today's master) fixes those, no other changes.
>>
> + <entry>
> + The command is preparing to begin scanning the heap. This phase is
> + expected to be very brief.
> + </entry>
> In the above after "." there is an extra space, is this intentional. I
> had noticed that in lot of places there is couple of spaces and
> sometimes single space across this file.
>
> Like in below, there is single space after ".":
> <entry>Time when this process' current transaction was started, or null
> if no transaction is active. If the current
> query is the first of its transaction, this column is equal to the
> <structfield>query_start</structfield> column.
> </entry>

Sorry for the late reply.

Probably, it is intentional because there are many extra space
in other documents. See below:

# Results of grep
=============
$ grep '\. ' doc/src/sgml/monitoring.sgml | wc -l
114
$ grep '\. ' doc/src/sgml/information_schema.sgml | wc -l
184
$ grep '\. ' doc/src/sgml/func.sgml | wc -l
577
=============

Therefore, I'm going to leave it as is. :)

Thanks,
Tatsuro Yamada

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhenghua Lyu 2019-11-01 06:42:25 On disable_cost
Previous Message lingce.ldm 2019-11-01 05:27:54 Re: Problem with synchronous replication