Message-ID: <44FA4E7B.4080400@commandprompt.com>
Date: Sat, 02 Sep 2006 20:39:39 -0700
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
User-Agent: Thunderbird 1.5.0.5 (X11/20060728)
MIME-Version: 1.0
To: Christopher Browne <cbbrowne@acm.org>
CC: pgsql-hackers@postgresql.org
Subject: Re: gBorg status?
References: <608xl5yny7.fsf@dba2.int.libertyrms.com>
	<20060902224155.GN84229@nasby.net>
	<878xl17jru.fsf@wolfe.cbbrowne.com>
In-Reply-To: <878xl17jru.fsf@wolfe.cbbrowne.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Christopher Browne wrote:
> Oops! jim@nasby.net ("Jim C. Nasby") was seen spray-painting on a wall:
>> On Thu, Aug 31, 2006 at 10:33:36AM -0400, Chris Browne wrote:
>>> What's up there?  It has been down all week.
>>>
>>> We're trying to get the Slony-I 1.2 release out, so we can then
>>> migrate over to pgFoundry.  But that doesn't working terribly well
>>> when gBorg's down...
>> Speaking of which, what's the status of the migration tools? Is that
>> ball still in Larry's court?
> 
> Which migration tools?  Were there migration tools specific to
> gBorg->pgFoundry?  Or something else?

There was, kind of, sort of. AFAIK they are dead and gone and the 
current method of thought on Gborg is here:

http://archives.postgresql.org/pgsql-general/2006-08/msg01167.php
-- 

    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/