From: | Michael Akinde <michael(dot)akinde(at)met(dot)no> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Large object loading stalls |
Date: | 2009-02-18 16:01:31 |
Message-ID: | 499C30DB.8060805@met.no |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hej,
I killed the test about an hour ago to eliminate the free space stuff as
an issue. I've started the process up again, so if (when) the test hangs
again, I'll try to get the stack trace.
Regards,
Michael Akinde
Tom Lane wrote:
> Michael Akinde <michael(dot)akinde(at)met(dot)no> writes:
>
>> We have been running into a strange problem on our production servers of
>> a system we are about to roll out with the loading of large objects.
>>
>
> Hmm, can you attach to the stuck backend and the vacuum worker process
> with gdb and get stack traces from them? The pg_locks view does not
> indicate any locking problem, but I'm wondering if there could be a
> deadlock at the LWLock level.
>
> regards, tom lane
>
Attachment | Content-Type | Size |
---|---|---|
michael.akinde.vcf | text/x-vcard | 287 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Aurimas Černius | 2009-02-18 16:08:07 | Re: connecting using libpq breaks printf |
Previous Message | Andrei Kovalevski | 2009-02-18 15:55:36 | Re: Mammoth replicator |