Re: OK, lets talk portability.

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: Hannu Krosing <hannu(at)tm(dot)ee>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: jm(dot)poure(at)freesurf(dot)fr, mlw <markw(at)mohawksoft(dot)com>, Dann Corbit <DCorbit(at)connx(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: OK, lets talk portability.
Date: 2002-05-09 10:03:20
Message-ID: 200205090603.20557.lamar.owen@wgcr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday 09 May 2002 04:56 am, Hannu Krosing wrote:
[snip other good ideas....]

> And instead of initdb we could just install ready-made $PGSQL/data
> directory.

From experience with the RPMset I can tell you that this is a bad idea, and it
comes down to one word:

upgrades.

Now if the installation location is _versioned_ we might can talk of a
pre-populated $PGDATA. I'm taking a really hard look right now at versioned
installation locations for the RPMset -- you can then have more than one
version installed at a time, and even running at one time if you're careful.
I haven't implemented it yet, but I am taking a long hard look at what I
would have to do in order to make it work.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Manfred Koizar 2002-05-09 10:07:58 Re: Number of attributes in HeapTupleHeader
Previous Message Henshall, Stuart - WCP 2002-05-09 09:46:03 PG+Cygwin Production Experience (was RE: Path to PostgreSQL porta biliy)