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: | The Hermit Hacker <scrappy(at)hub(dot)org>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_group_name_index corrupt? |
Date: | 2000-05-05 05:16:06 |
Message-ID: | 200005050516.BAA12456@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> >> 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...
Please give me something to add to the TODO.
--
Bruce Momjian | http://www.op.net/~candle
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-05-05 05:32:17 | Re: pg_group_name_index corrupt? |
Previous Message | Bruce Momjian | 2000-05-05 05:15:17 | Re: pg_group_name_index corrupt? |