On 05/11/2017 07:32 AM, Vibhor Kumar wrote:
On May 11, 2017, at 10:17 AM, Adrian Klaver <adrian.kla...@aklaver.com
<mailto:adrian.kla...@aklaver.com>> wrote:
Not sure how deep you are into your present situation. The only thing
I can think of is to install Postgres using the PGDG repos and then
migrating the data from the EDB install to the RPM install. You would
probably have to change the port numbers, at least temporarily, while
you do the migration. This way you could use the packaging system
without resorting to work-arounds.
I don’t think Martin has to migrate database. He has installed > PostgreSQL
9.6 using EDB one-click installer. I can see two options here:
1. Install PostgreSQL using RPM as mentioned by Adrian. Stop the
PostgreSQL using one click installer binaries and start using RPM
binary. After that Martin can install repmgr using RPM.
From OP:
"I have now been tasked with putting repmgr onto this box and converting
it from a standalone to a multiple node setup (I have two additional
servers lurking in the background ready for use ). "
That to me says there is data in the clusters that would need to be
migrated from the EDB instance(s) to the RPM instance(s). That could be
as simple as a dump/restore.
2. Compile repmgr with existing installation.
https://github.com/2ndQuadrant/repmgr
Thanks & Regards,
Vibhor Kumar
Blogs:https://vibhorkumar.blog
--
Adrian Klaver
adrian.kla...@aklaver.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
