On Fri, Apr 4, 2014 at 2:38 PM, Joe Van Dyk <[email protected]> wrote: > On Friday, April 4, 2014 2:32:25 PM UTC-7, Daniel Farina wrote: >> The latter it never did make, because there are recovery.conf settings >> in there that WAL-E as-is doesn't know anything about, like hot >> standby or where the primary_conninfo ought to be or even how to load >> configuration for WAL-E. I agree it'd be nice to get to one-less-step >> without losing power somehow, but it's a new surface area that to date >> WAL-E has never had. >> >> >> As for avoiding postgresql.conf: my rationale is that it is full of >> absolute paths and settings that can be dangerous upon restore. > > > Maybe make recovery.conf.sample and postresql.conf.old files? > > recovery.conf.sample could use the sample recovery line in the > documentation, with some information gathered from how the current wal-e > backup-fetch process was started. > > And postgresql.conf.old could contain the original master postgresql.conf > file. > > Then, at the end of backup-fetch, tell users about two files and indicate > that they should restore them or make new ones?
That sounds like a kernel of a good idea to me. There's some fine tuning about the file names (as so one can overwrite or, alternatively not-back-up old sample files) after a failover, but I like the convenience to mechanism to power ratio in general. I'll think on it. >> >> But, pg_subtrans should show up if the primary had it. >> >> Any errors in the logs of the download? >> > >> > >> > No errors. Primary has it. >> >> Well that's disturbing. Uh. What's the exact path relative to >> $PGDATA that's missing? I think to catch this one we'll need some >> instrumentation, and if you can reproduce this then I don't want to >> let this go if you have the time. > > > ./pg_subtrans > > I'll see if it can be reproduced.. Thanks a lot for the help on that one. -- 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/d/optout.
