From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Hint and detail punctuation |
Date: | 2018-12-06 04:46:26 |
Message-ID: | 20181206044626.GG2407@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 05, 2018 at 05:22:25PM +0100, Daniel Gustafsson wrote:
> While looking at error messages downstream, I noticed a few hints and details
> in postgres which aren’t punctuated as per the style guide. The attached patch
> fixes the ones where it seemed reasonable to end with a period.
Good point. I am spotting a couple more places:
src/backend/utils/misc/guc.c:
GUC_check_errdetail("effective_io_concurrency must be set to 0 on
platforms that lack posix_fadvise()");
src/backend/utils/misc/guc.c:
GUC_check_errdetail("recovery_target_timeline is not a valid number");
src/backend/utils/misc/guc.c:
GUC_check_errdetail("recovery_target_name is too long (maximum %d
characters)",
Thanks,
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2018-12-06 04:46:34 | Re: error message when subscription target is a partitioned table |
Previous Message | Pavel Stehule | 2018-12-06 04:33:14 | Re: zheap: a new storage format for PostgreSQL |