Am 13.03.2010 um 22:59 schrieb Tom Lane:
BTW, if the SSL-renegotiation theory is correct, what that should mean
is that the dump fails after transmitting 512MB worth of data. Is
that
consistent with what you're seeing?
561637949 is not too far away from it:
Am 13.03.2010 um 13:24 schrieb
BTW, if the SSL-renegotiation theory is correct, what that should mean
is that the dump fails after transmitting 512MB worth of data. Is that
consistent with what you're seeing?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make c
Am 13.03.2010 um 22:35 schrieb Tom Lane:
Have you recently updated the openssl library
on either the client or the server?
Yes, the client side got an update.
Is it practical for you to try a
dump across a non-SSL connection to see if that works, or is your
network too insecure for that?
I
Axel Rau writes:
> client:
> #0 0x9405de0e in poll$UNIX2003 ()
> #1 0x00044cfa in pqSocketCheck ()
> #2 0x00045101 in pqWaitTimed ()
> #3 0x00045167 in pqWait ()
> #4 0x0004b9b3 in pqGetCopyData3 ()
> #5 0x0001295f in dumpTableData_copy ()
> #6 0x00022a19 in _PrintTocData ()
> #7 0x0001ecd
Am 13.03.2010 um 19:45 schrieb Axel Rau:
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.
---
client:
#0 0x9405de0e in poll
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
Axel Rau 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 co
Hi all,
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:
--
TIME CMD
0:00.05 /usr/local/pgsql/bin/pg_dumpall -h db -i
0:21.45 /usr/local/pgsql/bin/pg_dump -h db -i -Fp database
