Re: [HACKERS] pg_upgrade

> Probably the cleanest way to deal with that is to tweak pg_resetxlog
> further to have an optional switch with a minimum xlog position.
> It already knows how to set up its cleared xlog with a position >=
> end of the removed log, so you could have an additional option switch
> that forces the new position to be >= switch value. To issue the
> switch, pg_upgrade would have to look at the old xlog files to determine
> the endpoint of the old xlog. Seems messy but not impossible.

Also, how do I find the current xlog segment position. Is it one of
these fields shown by pg_controldata?

pg_controldata
pg_control version number: 71
Catalog version number: 200110251
Database state: SHUTDOWNED
pg_control last modified: 01/10/02 13:00:04
Current log file id: 0
Next log file segment: 7
Latest checkpoint location: 0/6000010
Prior checkpoint location: 0/0
Latest checkpoint's REDO location: 0/6000010
Latest checkpoint's UNDO location: 0/6000010
Latest checkpoint's StartUpID: 8
Latest checkpoint's NextXID: 105
Latest checkpoint's NextOID: 16557
Time of latest checkpoint: 01/10/02 13:00:04
Database block size: 8192
Blocks per segment of large relation: 131072
LC_COLLATE: C
LC_CTYPE: C

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026