Re: [PERFORM] URGENT: pg_statistic_relid_att_index has gone
Harald Lau <[EMAIL PROTECTED]> writes: > on a 7.2 System (Suse-Linux) I got an error "duplicate key in unique > index pg_statistic_relid_att_index" (think it was while vacuuming) > I REINDEXd the database. > Now the table pg_statistic_relid_att_index is completely gone. > Has anybody an advise? Dump, initdb, reload. You've probably got more problems than just that. This might be a good time to update to something newer than PG 7.2, too. regards, tom lane ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [PERFORM] URGENT: pg_statistic_relid_att_index has gone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > on a 7.2 System (Suse-Linux) I got an error "duplicate key in unique > index pg_statistic_relid_att_index" (think it was while vacuuming) > > I REINDEXd the database. > Now the table pg_statistic_relid_att_index is completely gone. go searching the internet first, man ... Surprisingly I'm not the first one having such a breakdown Found a solution provided by Tom Lane: http://www.xy1.org/pgsql-general@postgresql.org/msg04568.html Seems to work, many thanks Sorry for the overhasty question Harald -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: GnuPT 2.7.2 iQEVAwUBQ0E5nXfX3+fgcdKcAQJWsgf+JvgWRjgl/RLBzGd8wNt7x6/VngGOzdpT 4E3OgbrGuAPEC3INkMLTLRU2hVvjRqgkNaWS2YlXpFmlAff6czGeSbwXv4vDiiH7 AYHpONACLgr8jcHohS0kmylqu/3QYSsmRBDOTOCNms1iMEmJZvpru9YJpSEjwWUL /n5pu5lurcpU+VGLTCikin5UnsNWmQzsegz+f2co3UuTDHIUER+W2538Fb9iiZBD P9TCI972U+oC2YTg+Puh22jPfS1gG7EHUxKt/XbE9klca1AnCdJX6LdsIh7vdMhw 6u8JzaaAz9nHtqYFpClkEpnkp9KEohw/uQyDUCB7FK//MRtSWx+MPw== =52pe -END PGP SIGNATURE- ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[PERFORM] URGENT: pg_statistic_relid_att_index has gone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, on a 7.2 System (Suse-Linux) I got an error "duplicate key in unique index pg_statistic_relid_att_index" (think it was while vacuuming) I REINDEXd the database. Now the table pg_statistic_relid_att_index is completely gone. Has anybody an advise? tia, Harald -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: GnuPT 2.7.2 iQEVAwUBQ0Ejx3fX3+fgcdKcAQIVoQf+MFnt+U65FPNxQjHwZ15eT13NwBoCsOE9 d3nFaKTG58SmI9QziMt1Tpo+pD89LMQZacnCRDv/M3Tz6ruSQaPIsxS6m1evKjq7 7ixSRCwD+41C2x27qSRZDOEUt6AvG5xfSv43NxJQNS/zB+/TnQ3wGXzwdRrRQiQE Mv6DXv5s+3Wrbg9qG78Xn3mHOGGySFSG1x9ItUoST+jC6a7rOl5YL3wDCacdgve/ pzq3fe6+JYjEQyKFxEzZYJidsWvr9C7EKfc321PYBscuPNyGMU1Vohe8kDYFbyeG L23jXPV8c7WO2w4aQMdQr6V9YXtnBeMgGdAFjo4My29xbdepkwOUvw== =I8Ax -END PGP SIGNATURE- ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq