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.rau@chaos1.de PGP-Key:29E99DD6 +49 151 2300 9283 computing @
chaos claudius