archive_command options?
| От | LEROY TENNISON |
|---|---|
| Тема | archive_command options? |
| Дата | |
| Msg-id | 1222332414.512321.1554322572303@mail.yahoo.com обсуждение исходный текст |
| Ответы |
Re: archive_command options?
Re: archive_command options? Re: archive_command options? Re: archive_command options? |
| Список | pgsql-admin |
Postgresql documentation lists the following as an archive command for log shipping:
archive_command = 'test ! -f /mnt/server/archivedir/%f && cp %p /mnt/server/archivedir/%f'
The problem is that it is very fragile. If anything breaks the copy (either system failing, network issues) then log shipping stops because the file exists in some intermediate state. The result is that logs build up on the source system filling disk space. I've had to deal with a few of these this week, in two cases the file system was 98% full. Is there a reason rsync isn't used? It has the ability to restart interrupted transfers. I don't want to use it only to find out i got myself into another predicament. Any other less-fragile options? Thanks for the help.
В списке pgsql-admin по дате отправления: