Re: contrib vs. gborg/pgfoundry for replication solutions

From: Joe Conway <mail(at)joeconway(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Magnus Hagander <mha(at)sollentuna(dot)net>, "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: contrib vs. gborg/pgfoundry for replication solutions
Date: 2004-04-22 04:43:36
Message-ID: 40874D78.7060109@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> I am thinking they could untar into a directory under pgsgl/ or have a
> way to point to a 'configure'-run source tree and pull values from
> there.

> If you include pg_config.h, or use Makefile.global, you have almost
> everything you need to compile your own, including flags, configure
> checks, and the location of the installation directory.

How hard would it be to have the individual cvs projects such that they
could be checked out all in one shot?

I'm thinking that if it was easy enough to maintain an up-to-date cvs
copy for all the individual projects, then it would be easy to grep the
entire mess when making backend changes. That way at least you could
determine the extent of the impact when making backend changes. And
since they are still individual projects, you don't need to get them all
if you're not interested.

Joe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2004-04-22 04:56:15 Re: contrib vs. gborg/pgfoundry for replication solutions
Previous Message Tom Lane 2004-04-22 04:39:21 Re: cannot drop active portal