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.aki...@met.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
begin:vcard
fn:Michael Akinde
n:Akinde;Michael
org:Meteorologisk Institutt, Norge;IT
adr;quoted-printable:;;Gaustadall=C3=A9en 30D;Oslo;;0313;Norge
email;internet:michael.aki...@met.no
tel;work:22963379
tel;cell:45885379
x-mozilla-html:FALSE
url:http://www.met.no
version:2.1
end:vcard
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
