| From: | Adriaan Joubert <a(dot)joubert(at)albourne(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Index corruption |
| Date: | 1999-12-29 15:46:55 |
| Message-ID: | 386A2CEF.ACC31BA2@albourne.com |
| 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.
Any other suggestions would be very welcome.
Regards,
Adriaan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-12-29 15:47:06 | Re: [SQL] Index scan on CIDR field ? |
| Previous Message | Tom Lane | 1999-12-29 15:20:43 | Re: [HACKERS] Index Puzzle for you |