Re: [CRITICAL PATCH] Release Candidate 5 ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [CRITICAL PATCH] Release Candidate 5 ...
Date: 2000-05-05 04:24:41
Message-ID: 4907.957500681@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> This RC *requires* a complete dump/initdb/reload of your database
> ... without it, consider your database a ticking timebomb ...

Or at least your pg_group table is a timebomb, if it's not empty.
Panic is not called for unless you use groups.

It should be noted that we found and fixed some problems in pg_upgrade
as well. This may mean that pg_upgrade is now safe. Or not, but it's
hard to say without testing. I would like to ask people who are
upgrading to RC5 to try to use pg_upgrade for the move, and report
whether you see problems or not. *Please* read the man page for
pg_upgrade, and make a complete dump beforehand so you have a fallback
if it fails ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-05-05 04:32:18 Re: pg_group_name_index corrupt?
Previous Message Don Baccus 2000-05-05 04:23:39 Re: ``..Advice For New Immigrants...