Re: pg_resetxlog -m documentation not up to date - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_resetxlog -m documentation not up to date
Date
Msg-id 1371692603.13762.38.camel@vanquo.pezone.net
Whole thread Raw
In response to pg_resetxlog -m documentation not up to date  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pg_resetxlog -m documentation not up to date  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
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,OLDEST    set next multitransaction ID and oldest value
> 
> but the man page does not reflect that change.
> 
> 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 something like
> 
>   -m XID,XID       set next and oldest multitransaction ID
> 
> 
> 
> 






pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: warn_unused_result in pgbench
Next
From: Alvaro Herrera
Date:
Subject: Re: pg_resetxlog -m documentation not up to date