Improve style guideline compliance of assorted error-report messages.
Tom Lane <tgl@sss.pgh.pa.us>
Improve style guideline compliance of assorted error-report messages. Per the project style guide, details and hints should have leading capitalization and end with a period. On the other hand, errcontext should not be capitalized and should not end with a period. To support well formatted error contexts in dblink, extend dblink_res_error() to take a format+arguments rather than a hardcoded string. Daniel Gustafsson Discussion: https://postgr.es/m/B3C002C8-21A0-4F53-A06E-8CAB29FCF295@yesql.se
Files
| Path | Change | +/− |
|---|---|---|
| contrib/dblink/dblink.c | modified | +48 −20 |
| contrib/dblink/expected/dblink.out | modified | +12 −12 |
| contrib/file_fdw/file_fdw.c | modified | +2 −2 |
| contrib/pgcrypto/px.c | modified | +2 −2 |
| contrib/postgres_fdw/connection.c | modified | +1 −1 |
| contrib/postgres_fdw/expected/postgres_fdw.out | modified | +7 −7 |
| contrib/postgres_fdw/option.c | modified | +1 −1 |
| src/backend/access/transam/xlog.c | modified | +1 −1 |
| src/backend/replication/logical/logical.c | modified | +1 −1 |
Discussion
- Error detail/hint style fixup 7 messages · 2018-03-19 → 2018-03-23