postgresql
I have now seen this problem twice. The current one in version 8 and the last time in version 7.3 of postgresql.
A table goes bad in a way I haven't discovered with the nasty side effect of taking a long time to access.
I have a table called announcements for the home page of crazedimaginations.net. Some announcements are from the cast director and are handled differently. So I make two calls to that table when I paint the home page.
Right now, there are six announcements in that table. Just six. But any query on that table takes slightly more than 7 seconds. Thus, the home page takes 15 seconds to load.
The only way I have found to fix the problem is to create a temp table as a query from the old table, delete the old table, then create the table again from the temp. It solves the problem.
But it also means I have to drop all the dependent objects and recreate them. It is a pain in the butt.
I have not found a way to repair the bad table. None of the tools I know about work.
Sigh.
Anyway, the home page does not take forever to load anymore.
A table goes bad in a way I haven't discovered with the nasty side effect of taking a long time to access.
I have a table called announcements for the home page of crazedimaginations.net. Some announcements are from the cast director and are handled differently. So I make two calls to that table when I paint the home page.
Right now, there are six announcements in that table. Just six. But any query on that table takes slightly more than 7 seconds. Thus, the home page takes 15 seconds to load.
The only way I have found to fix the problem is to create a temp table as a query from the old table, delete the old table, then create the table again from the temp. It solves the problem.
But it also means I have to drop all the dependent objects and recreate them. It is a pain in the butt.
I have not found a way to repair the bad table. None of the tools I know about work.
Sigh.
Anyway, the home page does not take forever to load anymore.