Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 998E29FA12B for ; Fri, 1 Dec 2006 15:29:35 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 67969-01 for ; Fri, 1 Dec 2006 15:29:27 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from myemma.com (db1.e2ma.net [66.179.147.163]) by postgresql.org (Postfix) with ESMTP id 9F4FD9F9EED for ; Fri, 1 Dec 2006 15:29:27 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by myemma.com (Postfix) with ESMTP id D59BF23CF5; Fri, 1 Dec 2006 13:29:26 -0600 (CST) Received: from myemma.com ([127.0.0.1]) by localhost (velma [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15052-08; Fri, 1 Dec 2006 13:29:25 -0600 (CST) Received: from [192.168.1.113] (c-68-53-86-247.hsd1.tn.comcast.net [68.53.86.247]) by myemma.com (Postfix) with ESMTP id 50CCC23CEC; Fri, 1 Dec 2006 13:29:25 -0600 (CST) Message-ID: <45708296.4030502@myemma.com> Date: Fri, 01 Dec 2006 13:29:26 -0600 From: Kim User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: Create table/view/index hanging following server crash References: <457070EC.8020307@myemma.com> <1243.1164999213@sss.pgh.pa.us> In-Reply-To: <1243.1164999213@sss.pgh.pa.us> Content-Type: multipart/alternative; boundary="------------040509030503080401050905" X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at myemma.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.013 tagged_above=0 required=5 tests=AWL, BAYES_20, FORGED_RCVD_HELO, HTML_40_50, HTML_MESSAGE, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200612/10 X-Sequence-Number: 23802 This is a multi-part message in MIME format. --------------040509030503080401050905 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Tom, I can't thank you enough. It was pg_attribute, and a reindex cleared up the problem. regards, kim Tom Lane wrote: >Kim 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 --------------040509030503080401050905 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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
--------------040509030503080401050905--