On Wed, Feb 12, 2014 at 9:57 AM, Kevin Harriss <[email protected]> wrote: > I do have a recovery.conf setup and it looks correct. It is included below. > Postgres has access to read the file as well. > > standby_mode = 'on' # enables stand-by (readonly) mode > > # Connect to the master postgres server using the replicator user we > created. > primary_conninfo = 'host=<host> port=<port> user=<user> password=<password>' > > # Specifies a trigger file whose presence should cause streaming replication > to > # end (i.e., failover). > trigger_file = '/tmp/pg_failover_trigger' > > # Shell command to execute an archived segment of WAL file series. > # Required for archive recovery if streaming replication falls behind too > far. > restore_command = '/usr/bin/envdir /etc/wal-e.d/env /usr/local/bin/wal-e > wal-fetch "%f" "%p"' > archive_cleanup_command = 'pg_archivecleanup > /var/lib/postgresql/9.3/archive/ %r'
Is WAL-E spamming you with progress updates like before? The only thing that comes to mind is if somehow your default 'psql' connects to the wrong database on "backup-push" so the database cluster being backed up and the database cluster being told to "select pg_start_backup()" are not the same. Another hairy sharp edge that comes to mind is that tablespaces don't work in WAL-E v0.6...and relatively silently so. v0.7 does support them, though. -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
