Re: Strange problem when upgrading to 7.2 with pg_upgrade.

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-04-09 04:44:15
Message-ID: 200204090444.g394iF821457@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Since I have done a vacuum, I assume I just keep creating 256k chunks
> > until I reach the max xid from the previous release, and delete the
> > files prior to the 1gb size limit.
>
> Keep your hands *off* the existing segments. The CLOG code will clean
> them up when it's good and ready ...

OK. Fill out the current clog and add additional ones to reach the
current max xid, rounded to the nearest 8k, assuming 256k file equals
1mb of xids.

Why do you take these things so personally?

--
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 Tatsuo Ishii 2002-04-09 05:08:56 Re: unknownin/out patch (was [HACKERS] PQescapeBytea is
Previous Message Tom Lane 2002-04-09 04:37:58 Re: Strange problem when upgrading to 7.2 with pg_upgrade.