Using pre-configured vs building Postgres

From: Armin Resch <reschab(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Using pre-configured vs building Postgres
Date: 2013-01-07 18:17:33
Message-ID: CAGo0LBTE3MU0cMrSMB+UF-z6rjasQiup_iRVaYusM=SvJ1eBeA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi all,

I am running custom applications on a Linux platform which essentially have
Perl and Postgres as prerequisites. In the past, we used an arcane Linux
distro which left me with no other option than to build Perl + 50 odd CPAN
modules + Postgres myself. I prefixed the stack under a common path like
this:

/osstack/perl/5.12.1
/osstack/postgresql/9.0.4

Yet, now, we switch to a more modern distro (OpenSuse 12.1), which does
have the RPM for Perl 5.14.2 pre-installed with the option to install more
RPMs such as

perl-DBI-1.616-7.1.3
perl-DBD-Pg-2.18.0-3.1.4
postgresql-9.1.1-3.1.4

Once our custom applications are tested and behave, the idea is to freeze
all prerequisites until we go to a different generation (potentially
different distro altogether in >= 5 years).

Before I try to obtain a handful of CPAN modules which are missing or
'unsupported' in OpenSuse, my question to this admin forum is what pro's
and con's to consider when deciding whether to use a pre-configured
postgresql versus building it ourselves.

Best,
-ar

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2013-01-07 18:37:27 Re: Using pre-configured vs building Postgres
Previous Message Tom Lane 2013-01-07 16:01:54 Re: Mapping a Data File Back to a Table