Re: [HACKERS] pg_xlogdump bad error msg?
On Mon, Jul 11, 2016 at 5:20 PM, Andres Freund wrote: > On 2016-07-11 13:36:37 +0200, Magnus Hagander wrote: > > When you don't specify a start segment to pg_xlogdump, you get: > > > > pg_xlogdump: no start log position given in range mode. > > > > > > What is "range mode", and is there any other mode for pg_xlogdump? Should > > it not just be "no start log position or segment given" or something like > > that? > > Works for me as well. > I assume that means you agree with changing it, so I will. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
Re: [HACKERS] pg_xlogdump bad error msg?
On 2016-07-11 13:36:37 +0200, Magnus Hagander wrote: > When you don't specify a start segment to pg_xlogdump, you get: > > pg_xlogdump: no start log position given in range mode. > > > What is "range mode", and is there any other mode for pg_xlogdump? Should > it not just be "no start log position or segment given" or something like > that? Works for me as well. Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
