Re: Strange problem when upgrading to 7.2 with pg_upgrade.

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Brian Hirt <bhirt(at)mobygames(dot)com>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Strange problem when upgrading to 7.2 with pg_upgrade.
Date: 2002-02-22 12:40:49
Message-ID: 200202221240.g1MCenw18554@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> We increased the xid because the old files have xid's that are greater
> than the newly initdb'ed database. We did a vacuum, so no one is going
> to check clog, but we need to increase the transaction counter because
> old rows could be seen as matching the current transaction.
>
> Can you suggest how to create the needed clog files? I don't see any
> value in changing your current clog code in the backend.

Tom, is there a way to increment the XID every 100 million and start the
postmaster to create the needed pg_clog files to get to the XID I need?

--
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-02-22 13:08:11 Re: [PATCHES] Re: nocreatetable for 7.1.2 [patch]
Previous Message Alex Adriaanse 2002-02-22 11:55:14 Re: point in time recovery and moving datafiles online