This is a discussion on BUG #1838: IndexSupportInitialze within the pgsql Bugs forums, part of the PostgreSQL category; --> The following bug has been logged online: Bug reference: 1838 Logged by: Judith Altamirano Email address: jaltamirano@correolux.com.mx PostgreSQL version: ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| The following bug has been logged online: Bug reference: 1838 Logged by: Judith Altamirano Email address: jaltamirano@correolux.com.mx PostgreSQL version: Postgres95 Operating system: Red Hat 6.2 Description: IndexSupportInitialze Details: Hi, when I try to make a query it appears the next error: IndexSupportInitialize: corrupted catalos after of a table named suc_usr, I can't drop de table index neither the table... I would apreciatte if somebody know how can I fix the bug ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |
| |||
| On Fri, Aug 19, 2005 at 07:32:41PM +0100, Judith Altamirano wrote: > > PostgreSQL version: Postgres95 Is that *really* the version you're running? What's the output of the following query? SELECT version(); -- Michael Fuhr ---------------------------(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 |
| |||
| "Judith Altamirano" <jaltamirano@correolux.com.mx> writes: > PostgreSQL version: Postgres95 > Operating system: Red Hat 6.2 > Description: IndexSupportInitialze > Details: > Hi, when I try to make a query it appears the next error: > IndexSupportInitialize: corrupted catalos > after of a table named suc_usr, I can't drop de table index > neither the table... Postgres95!? Red Hat 6.2? My goodness, you are using ancient software. The list of known bugs fixed since those days would terrify anybody (and that goes for the whole OS not just Postgres). I urgently recommend that you make a dump of your data, install something more modern, and reload the database. If your version of Postgres had REINDEX, you might be able to get out from under the immediate problem with that, but REINDEX wasn't there before Postgres 7.0. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster |
| ||||
| Judith Altamirano <jaltamirano@correolux.com.mx> writes: > Sorry, I just looked into the copyright, but the version that I'm currently > used is POstgres 7.0.2, that is anyway ancient, > the same: > IndexSupportInitialize: corrupted catalos > do you think that there is a way to fixed it? If it's 7.0 you might be able to fix it with a REINDEX DATABASE. You'll need to stop the postmaster and do this in a standalone backend. My recollection is that the first couple of releases that had REINDEX had very poor documentation of how to use it ... you might look at the online documentation for more recent versions, eg http://www.postgresql.org/docs/7.3/s...l-reindex.html (versions newer than 7.3 will tell you about stuff that does not work in 7.0, so this is probably the best one to look at) regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend |