Re: pg_update to a new machine?
От | Ron Johnson |
---|---|
Тема | Re: pg_update to a new machine? |
Дата | |
Msg-id | 8b083b6c-2774-ffd4-cac1-61affc3996af@cox.net обсуждение исходный текст |
Ответ на | pg_update to a new machine? (Ron Johnson <ron.l.johnson@cox.net>) |
Ответы |
Re: pg_update to a new machine?
|
Список | pgsql-general |
On 02/24/2018 03:10 PM, Stephen Frost wrote: [snip] >> To set up log shipping on 8.4, I do this, which works well: >> >> select pg_start_backup('some_meaningful_tag'); >> nohup rsync -avz /var/lib/pgsql/data/* postgres@${DESTIP}:/var/lib/pgsql/data/ & >> select pg_stop_backup(); > That's not log shipping, for log shipping you need to specify an > archive_command and actually capture all of the WAL generated, or, at a > minimum, the WAL generated between the start and stop backup calls. That's steps #8, 9 and 10 (in our checklist) of setting up log shipping. Step #4 is configuring the archive_* statements in postgresql.conf. -- Angular momentum makes the world go 'round.
В списке pgsql-general по дате отправления: