Re: pg_resetxlog -m documentation not up to date

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Subject: Re: pg_resetxlog -m documentation not up to date
Date: 2013-06-20 01:43:23
Message-ID: 1371692603.13762.38.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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
>
>
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-06-20 01:57:28 Re: pg_resetxlog -m documentation not up to date
Previous Message Peter Eisentraut 2013-06-20 01:38:44 warn_unused_result in pgbench