Re: PG13: message style changes - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: PG13: message style changes
Date
Msg-id 20201107055842.GA1486@paquier.xyz
Whole thread Raw
In response to PG13: message style changes  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: PG13: message style changes  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On Sat, Nov 07, 2020 at 12:49:43AM -0300, Alvaro Herrera wrote:
> In 0001, I propose changing messages that were introduced as different
> for parallel vacuum workers.  Frankly I don't understand why we are
> bragging about the vacuum being done in a parallel worker; does the user
> care?  It seems to me that users are just satisfied to know that the
> indexes were scanned; the fact that this was done in a parallel worker
> is not of much interest, so why call attention to that?  Therefore, we
> can reduce the message to what's emitted in the normal case.

Indeed.  Worth noting also that one can get the same level of
information with %P in log_line_prefix.

> In 0002, I propose to remove the word "concurrently" in an error
> message when an invalid index cannot be reindexed.  In fact, the problem
> is generic: we just cannot reindex the index at all, regardless of
> concurrently or not.  So we can reduce this message to be identical to
> the one we throw in the non-concurrent case.

No issues from me here.

> Patch 0004 just adds a comment to clarify a message that I found
> confusing when doing the translation.

+1.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: extension patch of CREATE OR REPLACE TRIGGER
Next
From: Tom Lane
Date:
Subject: Re: pgbench stopped supporting large number of client connections on Windows