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
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
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
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
hrieb Axel Rau:
age 10:47:05, expires in 23:15:07, 199433:386306 pkts,
10820556:561637949 bytes, rule 172
(-; Axel
---
axel@chaos1.de PGP-Key:29E99DD6 +49 151 2300 9283 computing @
chaos claudius
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to
Am 13.03.2010 um 23:34 schrieb Axel Rau:
if the SSL-renegotiation theory is correct
It was completly correct, because it worked last night. (-:
Thank you for this excellent diagnosis.
Axel
---
axel@chaos1.de PGP-Key:29E99DD6 +49 151 2300 9283 computing @
chaos claudius
--
Sent
Hi dbas,
I changed hot_standby to "on" on the standby and learned on restart:
"hot standby is not possible because wal_level was not set to ""hot_standby""
on the master server"
After restarting the master with "wal_level = hot_standby",
I'm still getting the same error message on the standby.
Th
Am 08.11.2012 um 18:16 schrieb Fujii Masao:
> On Fri, Nov 9, 2012 at 1:13 AM, Axel Rau wrote:
>> Hi dbas,
>>
>> I changed hot_standby to "on" on the standby and learned on restart:
>> "hot standby is not possible because wal_level was not set t
