From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> |
Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: postgres source code installation vs rpm based installation |
Date: | 2019-06-04 20:58:45 |
Message-ID: | CAKFQuwYx0OjXvM9O9gTY_n6XUWo1qfgBNL457GoXTjBupmaFsg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Jun 4, 2019 at 1:50 PM Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> wrote:
> Hello Ron,
>
> >>>>>>>Are you a Windows DBA with no Linux or Postgres experience? (I ask
> that so
> >>>>>>>that we know "where you are" in regards to installing software on
> Linux.)
>
> I am not Windows DBA. I have very good experience on Linux and working
> on postgres.
> I installed postgres in both way's rpm based and source code installation.
>
> I prefer source code for below reason
> I will have control on postgres software location
> few parameter I can modify with source code installation (like
> wal-segsize).
> I can install same version postgres on multiple times as per our
> need.
>
Installing the same binaries multiple times to different locations on the
same machine goes against the design of PostgreSQL.
If you need to change things that can only be changed at compile time then
your decision has been made.
Otherwise I'd stick with packages as the most well understood installation
and upgrade mechanism for your platform.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2019-06-04 21:26:16 | Re: postgres source code installation vs rpm based installation |
Previous Message | Pavan Kumar | 2019-06-04 20:49:23 | Re: postgres source code installation vs rpm based installation |