Hi, I'm going to be deploying Postgres in a semi-embedded system where end users might simply power the thing off from one moment to the next. Or the disk might start to go wonky, or any number of other problems. Because it's a standalone device, it may well run in an environment where we can't ship backups off of the machine. I've been reading this: http://www.postgresql.org/docs/9.2/static/continuous-archiving.html And it looks pretty good. It appears that, since I can't really back things up to a separate disk unit, it will "just work" unless the disk gets corrupted? In other words, in the case of someone pulling the power plug, it ought to be able to get things up and running more or less automatically, correct? Besides utilizing that, and keeping the fsync option set to true, what other steps can I take to make sure that data is not lost even in extraordinary circumstances? Having to manually fix things up is acceptable in the use case we're planning for, even if it's clearly preferable to not have to intervene. Thank you, -- David N. Welton http://www.welton.it/davidw/ http://www.dedasys.com/ -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
