| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 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 01:25:32 |
| Message-ID: | 1556.957489932@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | 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...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-05-05 01:30:29 | Re: pg_group_name_index corrupt? |
| Previous Message | Tom Lane | 2000-05-05 01:11:17 | Re: pg_group_name_index corrupt? |