Re: Compilation of optional packages - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Compilation of optional packages
Date
Msg-id AANLkTi=dWHmegEMHQVLSMPtT+nuYB=T64Ja4iHBrrTYt@mail.gmail.com
Whole thread Raw
In response to Compilation of optional packages  (Jutta Buschbom <jutta.buschbom@vti.bund.de>)
Responses Re: Compilation of optional packages  (Jutta Buschbom <jutta.buschbom@vti.bund.de>)
List pgsql-general
On Wed, Oct 6, 2010 at 1:24 AM, Jutta Buschbom
<jutta.buschbom@vti.bund.de> wrote:
> Hallo,
>
> At our institute we decided to use PostGreSQL as our new server-based
> database system. The installation of PostGreSQL 9.0.0 on SLES 10 x64 went
> fine. However, before I start configuring the system and start creating
> databases, users etc. I am wondering, which functionality I need to give the
> system right from the start that I cannot add later. The problem is that I
> don’t know what users might need in the future and being new to database
> management I might find out that some administrative functionality is
> necessary later on.
>
> Thus, my question: using “./configure –help” quite a lot of optional
> packages are listed for language support (PL/xxx) and network
> access/authentication, plus there is the feature to enable native language
> support. Do I install all these, just in case, or is there a possibility to
> add those packages and features later on as necessary? How does one go about
> this? Thanks a lot for your advice in advance.

You can install them later.  The only things you can't change without
a dump and reload are architectural, like integer datestamps and 32
versus 64 bit.

pgsql-general by date:

Previous
From: Jutta Buschbom
Date:
Subject: Compilation of optional packages
Next
From: Craig Ringer
Date:
Subject: Re: Compilation of optional packages