From: | "Daniel Farina" <drfarina(at)acm(dot)org> |
---|---|
To: | "Dave Page" <dpage(at)pgadmin(dot)org> |
Cc: | jd(at)commandprompt(dot)com, pgsql-www(at)postgresql(dot)org |
Subject: | Re: Errors when trying to use git.postgresql |
Date: | 2009-01-14 19:25:16 |
Message-ID: | 7b97c5a40901141125n3150f43die86566782bd117dd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Wed, Jan 14, 2009 at 11:10 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Afterward though, yes, I do run gc occasionally, though I haven't
> tried --aggressive yet.
Oh, okay -- I just thought it was because you put the ulimit change in
your .profile that you needed it permanently to keep things
rolling. After the first gc (which I think should have repacked
everything into one file) the 'ulimit -n' change should be obsolete.
'--aggressive' will take minutes to an hour if you have packed all the
packs together before so that the 'counting objects' phase doesn't
take forever. It should result in substantial repository size
reduction, presuming you have delta chains similar to that in the
git.postgresql.org repository.
My '.git' directory is 110M in total, for reference.
fdr
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-01-15 10:26:57 | Re: PostgreSQL GIT mirror status |
Previous Message | Dave Page | 2009-01-14 19:10:09 | Re: Errors when trying to use git.postgresql |