From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Couple of issues with pg_xlogdump |
Date: | 2013-04-23 14:51:06 |
Message-ID: | 20130423145106.GK2169@eldon.alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund escribió:
> On 2013-04-23 15:16:05 +0530, Pavan Deolasee wrote:
> > > It works without either if you use explicit options like -s STARTADDR
> > > and -p PATH which is frequently useful to just print a few records at
> > > the correct point. I am not sure how could put that in there without
> > > making it too complicated. Any suggestions?
> > >
> > Ah ok. Can we mention these details at in the documentation ?
> > http://www.postgresql.org/docs/devel/static/pgxlogdump.html
>
> So something like:
> At least one of STARTSEG, --start and --path or --rmgr=list has to be
> specified.
I think we need more than one synopsis line. Maybe
Usage:
pg_xlogdump [OPTION] --path=PATH --start=STARTPOS
pg_xlogdump [OPTION] [STARTSEG [ENDSEG]]
And then, under "options", do not list --path and --start (because
that'd imply they can be used when STARTSEG is specified, which I
understand they cannot).
Do we have any other possible operation mode? IIRC those are the only
two possible modes.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-04-23 14:59:43 | Re: putting a bgworker to rest |
Previous Message | Shaun Thomas | 2013-04-23 14:50:12 | Re: high io BUT huge amount of free memory |