Re: Create table/view/index hanging following server crash - Mailing list pgsql-admin

From Kim
Subject Re: Create table/view/index hanging following server crash
Date
Msg-id 45708296.4030502@myemma.com
Whole thread Raw
In response to Re: Create table/view/index hanging following server crash  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
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
p: 800 595 4401
w: www.myemma.com

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Create table/view/index hanging following server crash
Next
From: Tom Lane
Date:
Subject: Re: Problem restoring with pg_dump