Automatically terminate replication connections that are idle for more
than replication_timeout (a new GUC) milliseconds. The TCP timeout is often
too long, you want the master to notice a dead connection much sooner.
People complained about that in 9.0 too, but with synchronous replication
it's ev
Check that we've reached end-of-backup also when we're not performing
archive recovery.
It's possible to restore an online backup without recovery.conf, by simply
copying all the necessary WAL files to pg_xlog. "pg_basebackup -x" does that
too. That's the use case where this cross-check is useful.
Check that we've reached end-of-backup also when we're not performing
archive recovery.
It's possible to restore an online backup without recovery.conf, by simply
copying all the necessary WAL files to pg_xlog. "pg_basebackup -x" does that
too. That's the use case where this cross-check is useful.
Attempt to unbreak windows builds broken by commit 754baa2.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/382fb6a08f524327b5e3084b3652fba2e12f1ba2
Modified Files
--
src/backend/libpq/pqcomm.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Expand comment on how pg_upgrade is turning off autovacuum.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/d609b08ead450d78d4a567c48111aca6857ec59c
Modified Files
--
contrib/pg_upgrade/server.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
Mention pg_upgrade sets autovacuum_freeze_max_age to maximum.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/da3418cea9bd10e9ea3489b42f6278772942e745
Modified Files
--
contrib/pg_upgrade/server.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(
