From: | Kim <kim(at)myemma(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Create table/view/index hanging following server crash |
Date: | 2006-12-01 19:29:26 |
Message-ID: | 45708296.4030502@myemma.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(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
>
>
>
--
*kim hatcher*
senior developer, emma®
e: kim(at)myemma(dot)com <mailto:kim(at)myemma(dot)com>
p: 800 595 4401
w: www.myemma.com <http://www.myemma.com>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-12-01 19:32:45 | Re: Problem restoring with pg_dump |
Previous Message | Tom Lane | 2006-12-01 18:53:33 | Re: Create table/view/index hanging following server crash |