Re: Usage of pg_waldump

2018-11-13 Thread Peter Eisentraut
On 01/05/2018 18:39, David G. Johnston wrote: > ​note: there is either an extra space between the two closing brackets > or a missing space before startseg I have committed a fix for this. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote D

Re: Usage of pg_waldump

2018-05-01 Thread David G. Johnston
On Tue, May 1, 2018 at 9:26 AM, Andres Freund wrote: > 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

Re: Usage of pg_waldump

2018-05-01 Thread Andres Freund
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 argum

Usage of pg_waldump

2018-05-01 Thread Dang Minh Huong
Hi, I am confused with the Usage of pg_waldump (or pg_xlogdump). 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