| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_xlogdump bad error msg? |
| Date: | 2016-07-14 13:39:38 |
| Message-ID: | CABUevEwf+FaWQfTNg5M_Kqf9W10S2-Ru=saqgqaBQEd-XSB0_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 11, 2016 at 5:20 PM, Andres Freund <andres(at)anarazel(dot)de> 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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haribabu Kommi | 2016-07-14 13:39:51 | Re: Unable to test parallel aggregate/joins in Postgres beta 2 |
| Previous Message | Devrim Gündüz | 2016-07-14 13:29:03 | Re: Unable to test parallel aggregate/joins in Postgres beta 2 |