RE: Inconsistent GUC descriptions - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: Inconsistent GUC descriptions
Date
Msg-id OSCPR01MB14966F6721C16343DEF95E0EEF5C42@OSCPR01MB14966.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Inconsistent GUC descriptions  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers
Dear Horiguchi-san,

I really appreciate your post-commit reviewing.

> However, the existing message for the same situation is written
> without "The value of" at the beginning.

Right. To clarify, max_slot_wal_keep_size has similar check hook which rejects
the upgrade mode, and it starts with "\"%s\" must be set to".

> In addition, all existing
> messages following the "%s must be set to" pattern omit this phrase.

Yes, effective_io_concurrency and maintenance_io_concurrency start with it.

> Therefore, I believe the initial part of the new message should be
> removed for consistency. The attached patch makes this adjustment.

Agreed. I read your patch just in case and looks good to me...

Best regards,
Hayato Kuroda
FUJITSU LIMITED




pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Remove wal_[sync|write][_time] from pg_stat_wal and track_wal_io_timing
Next
From: Amit Kapila
Date:
Subject: Re: Introduce XID age and inactive timeout based replication slot invalidation