Greetings,
* Christoph Moench-Tegeder (cmt@burggraben.net) wrote:
> ## Yashwanth Govinda Setty (ygovindasetty@commvault.com):
>
> > 2. Restore the server with transaction logs
>
> This is missing a lot of details. If you do it right - see your email
> thread from one week ago - you will be able to recover the database
> server to a state as of the _end_ of the backup process (as marked by
> the return of the pg_stop_backup() command).
> If you do not follow the backup/restore documentation to the letter,
> the database will be corrupted and will not start (sometimes people
> report with haphazard backup schemes, but that's just more luck than
> they deserve, and nobody should rely on that).
Please also note that the PG documentation provided, when it comes to
the examples, are purely for usage demonstration only and shouldn't be
considered a good idea when it comes to implementing an actual solution.
Using only "cp" for archive_command is a particularly bad idea as it
doesn't sync the file to disk. Be sure to also heed the recommendation
about using the non-exclusive backup method and *not* using the
exclusive backup method.
Thanks!
Stephen
