Re: Investigate postgres 9.6.3 repmgr lag 4.0.4

From: Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Investigate postgres 9.6.3 repmgr lag 4.0.4
Date: 2018-06-25 06:51:54
Message-ID: CA+t6e1=JjrJG3nceVhjH53oSpb=-3yOMtpRpsdej0rzPiaT9SQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Moreover what of the next options do you recommend using in repmgr :
1)Using replication slots
2)Using barman

Thanks.

2018-06-25 9:44 GMT+03:00 Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com>:

> To be honest I used most of the default settings of repmgr and didnt focus
> on replication slot because I didnt saw that is was mentioned in the
> documentation. I will schedule soon a maintenance work to upgrade the
> cluster to version 10. I dont have any firewalls between all the nodes. So
> the optimal use is configure replication slot. Another question , "have
> it fail over to using the archived WALs instead of full database restore"
> How do I configure this ?
>
> Thanks , Mariel.
>
> 2018-06-24 19:37 GMT+03:00 Ron <ronljohnsonjr(at)gmail(dot)com>:
>
>> On 06/24/2018 11:22 AM, Flavio Henrique Araque Gurgel wrote:
>> [snip]
>>
>>
>> Actually there are just two simple questions for the OP: Why you're not
>> running the latest 9.6
>>
>>
>> Besides "he hasn't gotten around to it", there *are* companies that
>> allocate a few hours of downtime once per year (usually on Christmas Day)
>> for critical databases managing process control in factories.
>>
>> --
>> Angular momentum makes the world go 'round.
>>
>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message JD 2018-06-25 12:00:39 : : ReplicationSlots: :
Previous Message Mariel Cherkassky 2018-06-25 06:44:02 Re: Investigate postgres 9.6.3 repmgr lag 4.0.4