| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: pg_waldump: Improve option parsing error messages |
| Date: | 2022-05-20 07:45:10 |
| Message-ID: | E1nrxJu-000F8d-Gd@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
pg_waldump: Improve option parsing error messages
I rephrased the error messages to be more in the style of
option_parse_int(), and also made use of the new "detail" message
facility. I didn't actually use option_parse_int() (which could be
used for -n) because libpgfeutils wasn't used here yet and I wanted to
keep this just to string changes. But it could be done in the future.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/25f915b31e41e5c86e1905d199c7d41cc66161ed
Modified Files
--------------
src/bin/pg_waldump/pg_waldump.c | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2022-05-20 08:06:34 | pgsql: doc: Explain 'invalid' index state for CREATE INDEX CONCURRENTLY |
| Previous Message | Tom Lane | 2022-05-19 22:36:21 | pgsql: Doc: clarify location of libpq's default service file on Windows |