SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-10-2008, 06:52 AM
| ||||
| ||||
 Re: Create table/view/index hanging following server crash Kim <kim@myemma.com> writes: > In looking around the catalogs to try and see any more clues, I took a > look at pg_namespace. There were temp table namespaces listed there, > however there should be no temp tables on the system right now at all. This is normal. > Is there a clean way to clear those temp namespaces out? Don't worry about them, they'll be cleaned out on re-use. What you need to find is the system catalog corruption that is causing memory bloat during a CREATE TABLE. Does a SELECT * FROM pg_class show any problem? How about pg_attribute and pg_type? If plain SELECT is OK then the issue is likely index corruption, which you could fix with REINDEX. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly      |
|
04-10-2008, 06:52 AM
| ||||
| ||||
| Re: Create table/view/index hanging following server crash Tom, I can't thank you enough. It was pg_attribute, and a reindex cleared up the problem. regards, kim Tom Lane wrote: >Kim <kim@myemma.com> writes: > > >>In looking around the catalogs to try and see any more clues, I took a >>look at pg_namespace. There were temp table namespaces listed there, >>however there should be no temp tables on the system right now at all. >> >> > >This is normal. > > > >>Is there a clean way to clear those temp namespaces out? >> >> > >Don't worry about them, they'll be cleaned out on re-use. What you need >to find is the system catalog corruption that is causing memory bloat >during a CREATE TABLE. Does a SELECT * FROM pg_class show any problem? >How about pg_attribute and pg_type? If plain SELECT is OK then the >issue is likely index corruption, which you could fix with REINDEX. > > regards, tom lane > > > -- *kim hatcher* senior developer, emmaŽ e: kim@myemma.com <mailto:kim@myemma.com> p: 800 595 4401 w: www.myemma.com <http://www.myemma.com> |
 |
« Backup of a big DB with a lot of large objects
|
Create table/view/index hanging following server crash »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 10:03 AM.
