| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Pedro Sam <pesam(at)rim(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, senthilnathan <senthilnathan(dot)t(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Timeline Conflict |
| Date: | 2011-08-02 20:18:50 |
| Message-ID: | CA+U5nMLvj3KwfFC-oNozKiPZPrCeTNE97WZxshq6hOj4m-FhXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Aug 2, 2011 at 8:17 PM, Pedro Sam <pesam(at)rim(dot)com> wrote:
> I've been trying to use repmgr for just that purpose. Looks like it simply creates/modifies a recovery.conf pointing primary_conninfo to the new master, and then restart. It does not seem to have the ability to resolve any timeline conflicts at all.
>
> Am I using repmgr incorrectly?
It would appear so.
repmgr is not a fix for a problem situation, it is a management system
that will avoid the problems in the first place.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-08-02 20:21:47 | Re: Timeline Conflict |
| Previous Message | Merlin Moncure | 2011-08-02 19:41:28 | Re: Timeline Conflict |