pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kim <kim@myemma.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Create table/view/index hanging following server crash
Date: Fri, 01 Dec 2006 13:53:33 -0500
Message-ID: <1243.1164999213@sss.pgh.pa.us> (raw)
In-Reply-To: <457070EC.8020307@myemma.com>
References: <457070EC.8020307@myemma.com>

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



view thread (3+ messages)  latest in thread

Message-ID: <1243.1164999213@sss.pgh.pa.us>
Permalink:  ../1243.1164999213@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1243.1164999213@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, kim@myemma.com
  Subject: Re: Create table/view/index hanging following server crash
  In-Reply-To: <1243.1164999213@sss.pgh.pa.us>
  References: <457070EC.8020307@myemma.com> <1243.1164999213@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox