On Mon, Aug 16, 2010 at 9:58 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> 1. Tuesday evening, around 19:00 central european time, which is 17:00 >> GMT or 12:00 EST, I will freeze the current cvs repository. I will do >> this by disabling committer login on that box, so please note that >> this will also make it impossible for committers to do a "cvs update" >> from the authenticated repository. > > That's not really going to do, especially since it will also lock out > "cvs log". I certainly want to do a final update and cvs2cl after the > last commits have happened, and I imagine other people will want that > too. If there were a way to make the repository read-only that would be > nice, but I think what we're going to need to settle for is relying on > the committers to not do any more commits after the specified time. > > 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.
I would feel a lot more comfortable if the CVS repository was locked down before we start running the migration. Any accidental commits would be a nuisance. However, giving a window between last call for commits and actual lock-out seems reasonable. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
