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:19:16
Message-ID: 200204090419.g394JGd18621@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:
> >> I suspect that pg_upgrade has neglected to make sure the clog is long
> >> enough.
>
> > Here is the code that sets the transaction id. Tom, does pg_resetxlog
> > handle pg_clog file creation properly?
>
> pg_resetxlog doesn't know a single solitary thing about the clog.
>
> The problem here is that if you're going to move the current xact ID
> forward, you need to be prepared to create pages of the clog
> accordingly. Or maybe the clog routines need to be less rigid in their
> assumptions, but I'm uncomfortable with relaxing their expectations
> unless it can be shown that they may fail to cope with cases that
> arise in normal system operation. This isn't such a case.

Tom, any suggestion on how I can increase clog as part of pg_upgrade?

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-04-09 04:21:54 Re: Strange problem when upgrading to 7.2 with pg_upgrade.
Previous Message Bruce Momjian 2002-04-09 04:14:36 Re: Solaris ISM Testing