From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Adriaan Joubert <a(dot)joubert(at)albourne(dot)com> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Index corruption |
Date: | 1999-12-29 19:07:32 |
Message-ID: | 199912291907.OAA07128@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > Were you the person I told to use pg_upgrade and re-initdb
> your > database? If not, I would recommend that as the fix.
> You may need to > re-enable pg_upgrade by editing the script.
>
> Nope, but I've tried this now and it fails miserably for me. I
> had to edit the file created by pg_dump quote heavily as I have
> user-defined types and they required some initialisation before
> they could be used in the definition of indexes. Anyway, I
> managed to work around that, and pg_upgrade claimed that everything
> had finished successfully. But, although the datafiles were in
> the right place and the right size all the tables were empty.
> So some system tables were evidently not initialised correctly.
> I tried this both with 6.5.2 and 6.5.3, but no luck either way.
All I can say is someone did this recently for a system index problem
and it worked.
--
Bruce Momjian | http://www.op.net/~candle
maillist(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 | Bruce Momjian | 1999-12-29 19:09:00 | Re: [HACKERS] Index corruption |
Previous Message | svn | 1999-12-29 18:14:55 | revoke/grant rights issue |