From: | "Dave Page" <dpage(at)pgadmin(dot)org> |
---|---|
To: | "Daniel Farina" <drfarina(at)acm(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:10:09 |
Message-ID: | 937d27e10901141110x2f5a70bbpf9043d40b5d8702f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Wed, Jan 14, 2009 at 5:52 PM, Daniel Farina <drfarina(at)acm(dot)org> wrote:
> On Wed, Jan 14, 2009 at 12:58 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>> This happens on the local machine presumably? I used to suffer that
>> problem and resolved it with 'ulimit -n 1024' in my bash profile.
>
> This is because the number of packs in the git.postgresql.org repo is
> enormous, which also slows down clones and many other git operations.
> Try running "git gc --aggressive" to fix this on your local copy (this
> will take a while -- probably hours -- unless you've done it before).
Not much opportunity for that during the initial clone :-)
Afterward though, yes, I do run gc occasionally, though I haven't
tried --aggressive yet.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Farina | 2009-01-14 19:25:16 | Re: Errors when trying to use git.postgresql |
Previous Message | Daniel Farina | 2009-01-14 17:52:54 | Re: Errors when trying to use git.postgresql |