Tue Sep 19 04:08:04 PDT 2006
- Previous message: [Slony1-general] Migrating From gBorg
- Next message: [Slony1-general] Migrating From gBorg
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> -----Original Message----- > From: slony1-general-bounces at gborg.postgresql.org > [mailto:slony1-general-bounces at gborg.postgresql.org] On > Behalf Of Andrew Sullivan > Sent: 19 September 2006 11:44 > To: slony1-general at gborg.postgresql.org > Subject: Re: [Slony1-general] Migrating From gBorg > > On Mon, Sep 18, 2006 at 04:11:19PM -0700, Josh Berkus wrote: > > > > If your conclusion is that pgFoundry is borked and we need > to replace it > > with something else *in general*, then let's replace it. > > I think the conclusion is twofold: > > 1. pgFoundry is not sustainable in the long run, because of the > problems Chris raised. Why? Who says we've gotta keep upgrading? If we need any specific new features in the future then there's a good chance we'd have to scratch our own itch anyway, regardless of the status of the original project. > 2. We need something _right now_, because it's plain that gborg > isn't a reasonable holding pattern any more. Gborg is as secure as any of our other sites again. Believe it or not it really was a freak set of circumstances that led to the outage - and provisions have and are being put in place to prevent a recurrance. Regards, Dave.
- Previous message: [Slony1-general] Migrating From gBorg
- Next message: [Slony1-general] Migrating From gBorg
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list