Re: New repmgr packages - Mailing list pgsql-pkg-yum

From Martín Marqués
Subject Re: New repmgr packages
Date
Msg-id 5331E9AF.60309@2ndquadrant.com
Whole thread Raw
In response to Re: New repmgr packages  (Christian Kruse <christian@2ndquadrant.com>)
Responses Re: New repmgr packages
List pgsql-pkg-yum
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

El 21/03/14 04:39, Christian Kruse escribió:
> Hi,
>
> On 20/03/14 18:51, Martín Marqués wrote:
>> Now, I started thinking of something that maybe Christian or
>> Jaime can answer which is not related to packaging (at least not
>> directly) but has big influence in it: Do we need different
>> repmgr compilations for the different versions of PostgreSQL?
>
> This is a good question.
>
> After checking it three times it should be safe doing that. We're
> only using some version-dependent macros which get resolved by
> compile-time, and the changes on that macros are
> backwards-compatible.
>
> That said I have to admit that I didn't test it. Before doing so I
> would definitely want to test it.

Well, in any case, we need to have -devel package installed, and
AFAICS the packages are compiled for each version of PG, or at least
there is a mention of the PG version to use for checking on include
files (check for the -devel package to be installed) and the bindir.

On debian's repmgr package from pgdg, binaries go to /usr/bin/, but on
RHEL they go with the binaries of the version they were compiled
against, i.e. /usr/pgsql-9.3/bin/ for 9.3. If they are compatible, we
could just make 1 package for any version on PG.

Also checking through both packaging, I think we should add some
examples (repmgr.conf.sample) to the rpm. Does are sometimes very
valuable.

P.D.: Will send comments and files on another reply.

Regards,

- --
Martín Marqués                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTMemnAAoJEHsDtEgBAFTSLEMH/0e6aAkYfIl/9gm+sxtPSDoj
8MrjMR61Dz4u2kJ9dNNh/pGtb8HrAAlwV26cgXrYdt5GejYxLC6FSAeWtjpETPsH
y2KwvE8du6yUVIjUNn+xfFQOX0NavOLPh/89hoZt/r1gpJHC3pLiCRzMTbwPodhn
d4QxjBeQT+YZjWdrBw/6+yQSx9nQeZCCNZkbmcDpq4UDGRJK4iBz0HqWI1vDVKI0
ZTlAqz5Gcn0J2v2ztvCO539OAkGQYyMfQ9i8hmzfQQKS1m/9CN/92cqnTOAqJ6Gp
QJsvk3F8OfUSH4Ow6AZ+7muvH3Rnbx1k94N9LQWKWQD8vYVAWLeFIpajkHXNt3k=
=RXQa
-----END PGP SIGNATURE-----


pgsql-pkg-yum by date:

Previous
From: Christian Kruse
Date:
Subject: Re: New repmgr packages
Next
From: Martín Marqués
Date:
Subject: Re: New repmgr packages