Re: Compilation of optional packages

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Jutta Buschbom <jutta(dot)buschbom(at)vti(dot)bund(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Compilation of optional packages
Date: 2010-10-06 08:16:23
Message-ID: AANLkTi=dWHmegEMHQVLSMPtT+nuYB=T64Ja4iHBrrTYt@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Oct 6, 2010 at 1:24 AM, Jutta Buschbom
<jutta(dot)buschbom(at)vti(dot)bund(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2010-10-06 08:17:54 Re: Compilation of optional packages
Previous Message Scott Marlowe 2010-10-06 08:14:32 Re: Slony-I Doubt