Re: pg_update to a new machine?

From: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: pg_update to a new machine?
Date: 2018-02-25 00:35:43
Message-ID: 8b083b6c-2774-ffd4-cac1-61affc3996af@cox.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)${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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2018-02-25 00:40:09 Re: pg_update to a new machine?
Previous Message Stephen Frost 2018-02-24 21:10:08 Re: pg_update to a new machine?