ping
On 1/24/19 1:28 PM, Martijn van Duren wrote:
> ping
>
> On 11/20/18 8:27 AM, Martijn van Duren wrote:
>> ping
>>
>> repmgrd now also tested correctly.
>>
>> On 11/12/18 4:34 PM, Martijn van Duren wrote:
>>> On 11/12/18 4:30 PM, Martijn van Duren wrote:
When trying a new test-setup I
ping
On 11/20/18 8:27 AM, Martijn van Duren wrote:
> ping
>
> repmgrd now also tested correctly.
>
> On 11/12/18 4:34 PM, Martijn van Duren wrote:
>> On 11/12/18 4:30 PM, Martijn van Duren wrote:
>>> When trying a new test-setup I found that our repmgr is quite out of
>>> date. Here's a simple
ping
repmgrd now also tested correctly.
On 11/12/18 4:34 PM, Martijn van Duren wrote:
> On 11/12/18 4:30 PM, Martijn van Duren wrote:
>> When trying a new test-setup I found that our repmgr is quite out of
>> date. Here's a simple update to version 4.2.
>>
>> I haven't tested it with upgrading
On 11/12/18 4:30 PM, Martijn van Duren wrote:
> When trying a new test-setup I found that our repmgr is quite out of
> date. Here's a simple update to version 4.2.
>
> I haven't tested it with upgrading from our current version, but I have
> tested it very basically on a streaming replication
When trying a new test-setup I found that our repmgr is quite out of
date. Here's a simple update to version 4.2.
I haven't tested it with upgrading from our current version, but I have
tested it very basically on a streaming replication setup with setup,
failover, and switchover via repmgr.
