Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 394BA9F9F0E for ; Fri, 1 Dec 2006 14:53:44 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 74501-10 for ; Fri, 1 Dec 2006 14:53:34 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B04B99FA282 for ; Fri, 1 Dec 2006 14:53:35 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kB1IrXhe001244; Fri, 1 Dec 2006 13:53:33 -0500 (EST) To: Kim cc: pgsql-admin@postgresql.org Subject: Re: Create table/view/index hanging following server crash In-reply-to: <457070EC.8020307@myemma.com> References: <457070EC.8020307@myemma.com> Comments: In-reply-to Kim message dated "Fri, 01 Dec 2006 12:14:04 -0600" Date: Fri, 01 Dec 2006 13:53:33 -0500 Message-ID: <1243.1164999213@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/9 X-Sequence-Number: 23801 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