From 038f3a05092365eca070bdc588554520dfd5ffb9 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Tue, 26 Jun 2012 07:35:57 +0300 Subject: Fix pg_upgrade, broken by the xlogid/segno -> 64-bit int refactoring. The xlogid + segno representation of a particular WAL segment doesn't make much sense in pg_resetxlog anymore, now that we don't use that anywhere else. Use the WAL filename instead, since that's a convenient way to name a particular WAL segment. I did this partially for pg_resetxlog in the original xlogid/segno -> uint64 patch, but I neglected pg_upgrade and the docs. This should now be more complete. --- doc/src/sgml/ref/pg_resetxlog.sgml | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/pg_resetxlog.sgml b/doc/src/sgml/ref/pg_resetxlog.sgml index e98ae404459..27b9ab41d0f 100644 --- a/doc/src/sgml/ref/pg_resetxlog.sgml +++ b/doc/src/sgml/ref/pg_resetxlog.sgml @@ -131,13 +131,8 @@ PostgreSQL documentation the directory pg_xlog under the data directory. These names are also in hexadecimal and have three parts. The first part is the timeline ID and should usually be kept the same. - Do not choose a value larger than 255 (0xFF) for the third - part; instead increment the second part and reset the third part to 0. For example, if 00000001000000320000004A is the - largest entry in pg_xlog, -l 0x1,0x32,0x4B will - work; but if the largest entry is - 000000010000003A000000FF, choose -l 0x1,0x3B,0x0 - or more. + largest entry in pg_xlog, use -l 00000001000000320000004B or higher. -- cgit v1.2.3