Re: remote pg_dump hangs always at same table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Axel Rau <Axel(dot)Rau(at)chaos1(dot)de>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: remote pg_dump hangs always at same table
Date: 2010-03-13 16:33:25
Message-ID: 2689.1268498005@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Axel Rau <Axel(dot)Rau(at)chaos1(dot)de> writes:
> I have a daily remote backup session like
> pg_dump -h db -i -Fp database | gzip > file
> which hangs after producing about 200 MB of compressed output:

Is it CPU-busy, or idle? If the latter, is it blocked on a lock
according to pg_locks?

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.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Axel Rau 2010-03-13 18:45:11 Re: remote pg_dump hangs always at same table
Previous Message Axel Rau 2010-03-13 12:24:50 remote pg_dump hangs always at same table