Re: Moving to pgfoundry
От | Dave Cramer |
---|---|
Тема | Re: Moving to pgfoundry |
Дата | |
Msg-id | F9137C5B-7895-4DF1-92DA-768A14046E8D@fastcrypt.com обсуждение исходный текст |
Ответ на | Re: Moving to pgfoundry (Christopher Browne <cbbrowne@acm.org>) |
Список | pgsql-jdbc |
On 6-Sep-06, at 9:55 PM, Christopher Browne wrote: > The world rejoiced as pg@fastcrypt.com (Dave Cramer) wrote: >> On 6-Sep-06, at 5:14 PM, Oliver Jowett wrote: >> >>> Dave Cramer wrote: >>>> On 6-Sep-06, at 4:14 PM, Oliver Jowett wrote: >>>>> Dave Cramer wrote: >>>>>> It would appear this is inevitable. >>>>>> What do we need to do to make this happen ? >>>>>> Move CVS >>>>>> anything else ? >>>>> >>>>> Isn't this a question you should be asking the gborg/pgfoundry >>>>> maintainers? >>>> The question is do we want to retain CVS history ? If not this is >>>> trivial. If so; not so trivial. >>> >>> We would need to retain the CVS branches we have, and we'd need >>> *access* to CVS history even if it's not actually live in the >>> repository that we use. >>> >>> What's the issue with preserving history? >> >> The two machines are physically different, so consider this moving >> the repository. My recollection is that you have to physically move >> the entire repository; is there another way ? >> >> I don't think we can count on having the history available on gborg, >> they're planning on pulling the plug. > > If the recovery goes OK, it *ought* to be possible to copy the CVS > repository as set of files from old server to new server. Right > We're hoping for that for Slony-I; we'd certainly like to be able to > preserve that old history. > > I'm hearing mixed reviews as to the merits of pgFoundry as an > alternative; apparently it's already somewhat overloaded, so that some > of the admins are concerned about adding more to it. There's some new > hardware (an AMD-64 box of some sort), but it hasn't been fully tested > out yet. > > On the Slony-I side, we're talking over some other options than > pgFoundry; JDBC seems important enough that I would urge making sure > you maintain remote backups of CVS whatever your direction is. What are the other options you are discussing ? We may be interested too. > > One failure: Shame on them; if it falls over again, and there aren't > good backups, *that* gets embarrassing... > -- > let name="cbbrowne" and tld="gmail.com" in String.concat > "@" [name;tld];; > http://cbbrowne.com/info/lsf.html > Implementing systems is 95% boredom and 5% sheer terror. > > ---------------------------(end of > broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org >
В списке pgsql-jdbc по дате отправления: