From: Tom Lane <tgl@sss.pgh.pa.us>
To: Axel Rau <Axel.Rau@chaos1.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: remote pg_dump hangs always at same table
Date: Sat, 13 Mar 2010 11:33:25 -0500
Message-ID: <2689.1268498005@sss.pgh.pa.us> (raw)
In-Reply-To: <63A3189E-E6F9-491B-91CF-E907EF9C8C6C@chaos1.de>
References: <63A3189E-E6F9-491B-91CF-E907EF9C8C6C@chaos1.de>
Axel Rau <Axel.Rau@chaos1.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, Axel.Rau@chaos1.de
Subject: Re: remote pg_dump hangs always at same table
In-Reply-To: <2689.1268498005@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox