Re: Todays git migration results

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alex Hunsaker <badalex(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Todays git migration results
Date: 2010-08-17 14:34:16
Message-ID: 12873.1282055656@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> It should get a bit faster if we reduce the number of branches it
> examines, which I assume is something we can do once we desupport 7.4
> and 8.0. We could also add a --since argument which would doubtless
> speed things up a lot, by truncating the history to, say, the last N
> years. Also, it could possibly be rewritten to be faster still if it
> started N simultaneous copies of git log simultaneously instead of in
> sequence, and processed them incrementally rather than throwing them
> into a giant hash table, which would also probably cut down memory
> usage quite a bit. However, I'm not really inclined to spend a lot of
> time on it unless it's actually bugging Tom.

FWIW, I would find a --since option useful (since I use the equivalent
option of cvs2cl), but those other refinements don't seem of interest.
14 seconds is already an order of magnitude or two faster than cvs2cl.

> So I think we should consider checking it into src/tools.

+1 ... but not today ;-)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2010-08-17 14:38:15 Re: Todays git migration results
Previous Message Tom Lane 2010-08-17 14:29:40 Re: PL/pgSQL EXECUTE '..' USING with unknown