Re: pg_xlogdump bad error msg?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_xlogdump bad error msg?
Date: 2016-07-11 15:20:59
Message-ID: 20160711152059.o4lwv2ydicqlzcmm@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Srinivas Karthik V 2016-07-11 15:24:23 Changing the result set to contain the cost of the optimizer's chosen plan
Previous Message Masahiko Sawada 2016-07-11 14:51:05 Re: Reviewing freeze map code