On Thu, Feb 27, 2014 at 2:10 PM, Christophe Pettus <[email protected]> wrote: > > On Feb 27, 2014, at 2:01 PM, Daniel Farina <[email protected]> wrote: > >> All my postgresql.confs are systematically unique >> (including the paths), so the .conf of the old machine is *never* of >> use to me, and can even be harmful. > > Really? Every single system has a totally unique set of mount paths for > PostgreSQL volumes?
Yeah. And a randomly generated logging identity. Also they can be a different size and have different tuning (but not different max_connections, that's the one exception to the rule, but it's the only one I've seen so far). > I'll mention that the fact that this behavior is undocumented. One should try a restore-and-start at least once to flush it out, no? It doesn't have a subtle failure mode. It's discoverable. And in the worst case one is make the config if one employs laxity in this area. Send a patch if you want, but you are the first complainant and I have to be judicious about what information can be exhaustively placed in the README. It's already losing the crispness for users of any one storage backend already. -- 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.
