Re: pg_group_name_index corrupt?

okay, something that I think needs to be clarified ... RC5 requires an
initdb, so you have to do a pg_dumpall first, then initdb, then reload ...

your recent fixes ... should we be running pg_dumpall from RC5 on our RC4
databases, or does it not matter? I'm using the RC5 one right now, and
all appears correct, but I figured I'd ask ...

On Thu, 4 May 2000, Tom Lane wrote:

> >> Would a pg_upgrade fix this, or do I have to do a whole dump/reload?
>
> > pg_upgrade *should* work, but if I were you I'd make a backup dump
> > first, just in case. I don't trust pg_upgrade very much...
>
> Oh, btw: pg_upgrade will *not* work to save and reload your group
> definitions, because neither it nor pg_dumpall do anything at all with
> pg_group! For that matter, a full dumpall/reload won't preserve
> groups either!
>
> I griped about that a week or so ago, but no one seems to have picked up
> on it. Do you want to consider that a "must fix" problem as well?
> I think it's a pretty minor fix, but considering how late we are in the
> cycle...
>
> regards, tom lane
>

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org