Re: Git migration timeline
| От | Robert Haas |
|---|---|
| Тема | Re: Git migration timeline |
| Дата | |
| Msg-id | AANLkTi=mvwSSp-BABGg9aOKAojGppCWQuhPxFwP7gdeP@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Git migration timeline (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
On Mon, Aug 16, 2010 at 10:15 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Magnus Hagander <magnus@hagander.net> writes: >> On Mon, Aug 16, 2010 at 15:58, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> I can see the point of wanting to be dead certain the repository isn't >>> changing under you during the data migration. Perhaps we need an agreed >>> window between last call for commits and the actual lock-out. > >> To prevent that, I just need to shut it down for 2 minutes to rsync >> the latest changes off it and onto the new git box. Maybe that's how >> we should do it. > > That sounds like a reasonable scheme to me, especially since it leaves > the cvs repository functional. Dunno about you, but I want a fallback > plan in case this turns into a disaster ... I don't think anybody proposed permanently deleting the CVS repository. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: