Re: Error logging messages - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Error logging messages
Date
Msg-id b8097bc0-982a-a694-212d-3ac81d97e731@enterprisedb.com
Whole thread Raw
In response to Error logging messages  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Error logging messages  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
On 13.04.22 13:51, Daniel Gustafsson wrote:
> 0002: Capitalizes pg_log_error_detail and conversely starts pg_log_error with a
> lowercase letter without punctuation.

I'm having some doubts about some of these changes, especially for 
interactive features in psql, where the messages are often use a bit of 
a different style.  I don't think this kind of thing is an improvement, 
for example:

-       pg_log_error("You are currently not connected to a database.");
+       pg_log_error("you are currently not connected to a database");

If we want to be strict about it, we could change the message to

"not currently connected to a database"

But I do not think just chopping of the punctuation and lower-casing the 
first letter of what is after all still a sentence would be an improvement.



pgsql-hackers by date:

Previous
From: "Euler Taveira"
Date:
Subject: Re: Support logical replication of DDLs
Next
From: Tom Lane
Date:
Subject: Re: TRAP: FailedAssertion("HaveRegisteredOrActiveSnapshot()", File: "toast_internals.c", Line: 670, PID: 19403)