Re: remote pg_dump hangs always at same table

From: Axel Rau <Axel(dot)Rau(at)chaos1(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: remote pg_dump hangs always at same table
Date: 2010-03-13 18:45:11
Message-ID: 658A0A8A-847B-48BC-8729-66EFB111A585@chaos1.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


Am 13.03.2010 um 17:33 schrieb Tom Lane:

> Is it CPU-busy, or idle?
Idle.
> If the latter, is it blocked on a lock
> according to pg_locks?
It has acquired a lot of shared and one exclusive lock which all have
been granted.
>
> The most informative thing you could do is attach to both pg_dump and
> its connected backend with gdb and get stack traces. But looking at
> pg_locks might solve the mystery without that.
I will try to do that.

Thanks for responding,
Axel
---
axel(dot)rau(at)chaos1(dot)de PGP-Key:29E99DD6 +49 151 2300 9283 computing @
chaos claudius

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Axel Rau 2010-03-13 21:17:55 Re: remote pg_dump hangs always at same table
Previous Message Tom Lane 2010-03-13 16:33:25 Re: remote pg_dump hangs always at same table