Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1nY9P1-0004QF-Ht
	for pgsql-hackers@arkaria.postgresql.org; Sat, 26 Mar 2022 16:36:35 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1nY9Oz-0004iB-V4
	for pgsql-hackers@arkaria.postgresql.org; Sat, 26 Mar 2022 16:36:33 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nY9Oz-0004i1-Lz
	for pgsql-hackers@lists.postgresql.org; Sat, 26 Mar 2022 16:36:33 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nY9Ox-0005sO-Em
	for pgsql-hackers@postgresql.org; Sat, 26 Mar 2022 16:36:32 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 22QGa78N051567;
	Sat, 26 Mar 2022 12:36:07 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
cc: nagata@sraoss.co.jp, coelho@cri.ensmp.fr, thomas.munro@gmail.com,
        m.polyakova@postgrespro.ru, alvherre@2ndquadrant.com,
        pgsql-hackers@postgresql.org, teodor@sigaev.ru
Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
In-reply-to: <20220325.102520.1046619137276131190.t-ishii@sranhm.sra.co.jp>
References: <3163793.1648166710@sss.pgh.pa.us>
 <20220325.091400.602625132738741785.t-ishii@sranhm.sra.co.jp>
 <20220325101218.f70a36ae31064117c02f8b9e@sraoss.co.jp>
 <20220325.102520.1046619137276131190.t-ishii@sranhm.sra.co.jp>
Comments: In-reply-to Tatsuo Ishii <ishii@sraoss.co.jp>
	message dated "Fri, 25 Mar 2022 10:25:20 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <51565.1648312567.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 26 Mar 2022 12:36:07 -0400
Message-ID: <51566.1648312567@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/51566.1648312567%40sss.pgh.pa.us>
Precedence: bulk

Tatsuo Ishii <ishii@sraoss.co.jp> writes:
> Thanks. Patch pushed.

This patch has caused the PDF documentation to fail to build cleanly:

[WARN] FOUserAgent - The contents of fo:block line 1 exceed the available =
area in the inline-progression direction by more than 50 points. (See posi=
tion 125066:375)

It's complaining about this:

<synopsis>
<replaceable>interval_start</replaceable> <replaceable>num_transactions</r=
eplaceable> <replaceable>sum_latency</replaceable> <replaceable>sum_latenc=
y_2</replaceable> <replaceable>min_latency</replaceable> <replaceable>max_=
latency</replaceable> { <replaceable>failures</replaceable> | <replaceable=
>serialization_failures</replaceable> <replaceable>deadlock_failures</repl=
aceable> } <optional> <replaceable>sum_lag</replaceable> <replaceable>sum_=
lag_2</replaceable> <replaceable>min_lag</replaceable> <replaceable>max_la=
g</replaceable> <optional> <replaceable>skipped</replaceable> </optional> =
</optional> <optional> <replaceable>retried</replaceable> <replaceable>ret=
ries</replaceable> </optional>
</synopsis>

which runs much too wide in HTML format too, even though that toolchain
doesn't tell you so.

We could silence the warning by inserting an arbitrary line break or two,
or refactoring the syntax description into multiple parts.  Either way
seems to create a risk of confusion.

TBH, I think the *real* problem is that the complexity of this log format
has blown past "out of hand".  Can't we simplify it?  Who is really going
to use all these numbers?  I pity the poor sucker who tries to write a
log analysis tool that will handle all the variants.

			regards, tom lane