Hi Jeff.
Thanks for the clarification.
I'll adjust wal_keep_segments for the expected biggest table in the backup.
Best regards,
Mads
From: Jeff Janes jeff.ja...@gmail.com
To: mads.tand...@schneider-electric.com
mads.tand...@schneider-electric.com,
Cc: Albe Laurenz
HiThanks for your reply. Do you know of any options that I could give pg_dump/psql to avoid creating one big transaction? I'm using the plain text format for pg_dump.Best regards,Mads-pgsql-general-ow...@postgresql.org skrev: -Til: Albe Laurenz laurenz.a...@wien.gv.atFra: Jeff Janes
Hi all
I have a question about sync streaming replication.
I have 2 postgresql 9.1 servers set up with streaming replication. On the
master node the slave is configured as a synchronous standby. I've verified
that pg_stat_replication shows sync_state = sync for the slave node.
It all seems to
Hi AllI'm trying to understand the implications of the latest security fix to postgresql [1].We have a setup were we in pg_hba.conf have limited the allowed IP addresses of the clients. But does anyone know ifCVE-2013-1899 allows an arbitrary attacker to use the exploits described in [1]?We are
Hi Bruce.Didn't catch that in the announcement.Thanks for clearing out the confusion.Best regards,Mads
Hi All
I've set up a 3 postgresql nodes 1 master and 2 slaves. They have been
configured for streaming replication with synchronous on. I've set up an
virtual IP that points to the current master node.
When I kill the master node. The slave that was synchronous gets promoted
to master and gets
