Re: Strange problem when upgrading to 7.2 with pg_upgrade.

From: "Mattew T(dot) O'Connor" <matthew(at)zeut(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Brian Hirt <bhirt(at)mobygames(dot)com>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Strange problem when upgrading to 7.2 with pg_upgrade.
Date: 2002-04-09 19:22:32
Message-ID: 200204091922.g39JMW318135@rh71.zeut.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wouldn't be so quick to assume that almost everyone has upgraded by now. I
know we have not, at least not in production.

On Tuesday 09 April 2002 02:14 pm, Bruce Momjian wrote:
> This is a good bug report. I can fix pg_upgrade by adding clog files
> containing zeros to pad out to the proper length. However, my guess is
> that most people have already upgrade to 7.2.X, so there isn't much
> value in fixing it now. I have updated pg_upgrade CVS for 7.3, and
> hopefully we will have it working and well tested by the time 7.3 is
> released.
>
> Compressed clog was new in 7.2, so I guess it is no surprise I missed
> that change in pg_upgrade. In 7.3, pg_clog will be moved over from the
> old install, so this shouldn't be a problem with 7.3.
>
> Thanks for the report. Sorry I don't have a fix.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-04-09 19:42:55 Re: notification: pg_notify ?
Previous Message Bruce Momjian 2002-04-09 18:23:47 Re: unknownin/out patch (was [HACKERS] PQescapeBytea is