Re: Create table/view/index hanging following server crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kim <kim(at)myemma(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Create table/view/index hanging following server crash
Date: 2006-12-01 18:53:33
Message-ID: 1243.1164999213@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Kim <kim(at)myemma(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Kim 2006-12-01 19:29:26 Re: Create table/view/index hanging following server crash
Previous Message Joshua D. Drake 2006-12-01 18:18:19 Re: Backup of a big DB with a lot of large objects