| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Dang Minh Huong <kakalot49(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Usage of pg_waldump |
| Date: | 2018-05-01 16:26:30 |
| Message-ID: | 20180501162630.ht426rxwfmqxg74j@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hi,
On 2018-05-01 16:41:04 +0900, Dang Minh Huong wrote:
> The syntax is known as,
>
> pg_waldump [OPTION]... [STARTSEG [ENDSEG]]
>
> Mean that, it could work with no arguments.
> But the "no arguments specified" ERROR will be returned in that case.
>
> $ pg_waldump
> pg_waldump: no arguments specified
> Try "pg_waldump --help" for more information.
>
> I wonder it should be,
>
> pg_waldump { OPTION... [STARTSEG [ENDSEG]] } | { [OPTION]... STARTSEG [ENDSEG] }
>
> Have any comments?
To me that doesn't seem like an improvement, looks a good chunk more
complicated. You'll get the error and the docs also tell you that some
arguments are needed.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-05-01 16:39:22 | Re: Usage of pg_waldump |
| Previous Message | Stephen Frost | 2018-05-01 14:51:03 | Re: BUG #15180: Alter table add column if not exists with unique constraint will add extra duplicate |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stas Kelvich | 2018-05-01 16:27:22 | Global snapshots |
| Previous Message | Catalin Iacob | 2018-05-01 16:24:16 | Re: Postgres, fsync, and OSs (specifically linux) |