Re: pg_resetxlog -m documentation not up to date
От | Peter Eisentraut |
---|---|
Тема | Re: pg_resetxlog -m documentation not up to date |
Дата | |
Msg-id | 1371692603.13762.38.camel@vanquo.pezone.net обсуждение исходный текст |
Ответ на | pg_resetxlog -m documentation not up to date (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: pg_resetxlog -m documentation not up to date
|
Список | 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 по дате отправления: