Re: [HACKERS] pg_resetxlog -m documentation not up to date

2013-07-01 Thread Alvaro Herrera
Peter Eisentraut wrote: > On 6/19/13 9:57 PM, Alvaro Herrera wrote: > > Peter Eisentraut wrote: > >> Ping. This ought to be fixed before 9.3 goes out. > > > > Will fix. > > > >> On Sat, 2013-04-27 at 21:22 -0400, Peter Eisentraut wrote: > >>> The pg_resetxlog -m option was changed from > > The

Re: [HACKERS] pg_resetxlog -m documentation not up to date

2013-07-01 Thread Peter Eisentraut
On 6/19/13 9:57 PM, Alvaro Herrera wrote: > Peter Eisentraut wrote: >> Ping. This ought to be fixed before 9.3 goes out. > > Will fix. > >> On Sat, 2013-04-27 at 21:22 -0400, Peter Eisentraut wrote: >>> The pg_resetxlog -m option was changed from The man page lists the -m option as -m mxid,mxid

Re: [HACKERS] pg_resetxlog -m documentation not up to date

2013-06-27 Thread Alvaro Herrera
Peter Eisentraut wrote: > It was introduced in 0ac5ad5134f2769ccbaefec73844f8504c4d6182 "Improve > concurrency of foreign key locking", but there is also no explanation > there. It is apparently needed in pg_upgrade. > > This should be documented, and I think the help line should be changed > to

Re: [HACKERS] pg_resetxlog -m documentation not up to date

2013-06-19 Thread Alvaro Herrera
Peter Eisentraut wrote: > Ping. This ought to be fixed before 9.3 goes out. Will fix. > On Sat, 2013-04-27 at 21:22 -0400, Peter Eisentraut wrote: > > The pg_resetxlog -m option was changed from -- Álvaro Herrerahttp://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support,

Re: [HACKERS] pg_resetxlog -m documentation not up to date

2013-06-19 Thread Peter Eisentraut
Ping. This ought to be fixed before 9.3 goes out. On Sat, 2013-04-27 at 21:22 -0400, Peter Eisentraut wrote: > The pg_resetxlog -m option was changed from > > -m XID set next multitransaction ID > > to > > -m XID,OLDESTset next multitransaction ID and oldest value > > but t