Oh sorry, I already did that to fix the WAL confusion so now only the servers that should use this prefix are using it. I changed the prefix on master did a backup push. Changed the prefix on the slave and did a backup_fetch latest. When I do a backup_list I get the correct backups.
However I am not see why postgres isn't starting up now. Since it was running earlier and I didn't change any config files for postgres. On Wed, Feb 12, 2014 at 1:30 PM, Daniel Farina <[email protected]> wrote: > On Wed, Feb 12, 2014 at 11:29 AM, Kevin Harriss <[email protected]> > wrote: > > Thanks that looks like it might have fixed the pulling the wrong wal file > > now. However, postgres still wont start after I deleted the PGDATA and > did a > > recovery. The last entries in the log file are from the two new wal > segments > > that got pulled down during the backup-fetch. > > Once one has a confused prefix in their possession, all bets are off. > You are probably best reassigning all servers that co-mingled that > prefix to brand new prefixes known to be unique. > > -- > 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. > -- 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.
