On Feb 27, 2014, at 12:40 AM, Daniel Farina <[email protected]> wrote: > Is that file actually portable between systems and configurations?
In the modern world of on-demand instances, I think it largely is... or, at least, the work of properly configuring it is less than the work of recreating it from scratch on a new system. In particular, it seems strange to me that WAL-E will back up random files that just happen to be in PGBASE, but excludes files that are actually required to fire the server up. People who have custom hardware running on Centos systems may have trouble, yes. On the other hand, that's a pretty well-understood trouble, whereas "Where did the postgresql.conf go?" is surprising. It's a non-issue on Debian, as I'm not suggesting that the backup walk over to /etc/postgresql to grab everything, but a policy of "Everything under PGBASE is backed up except for this random set of *.conf files documented in the code" seems hard to justify. -- -- Christophe Pettus [email protected] -- 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.
