On Wed, Jan 14, 2009 at 5:52 PM, Daniel Farina <drfarina@acm.org> wrote:
> On Wed, Jan 14, 2009 at 12:58 AM, Dave Page <dpage@pgadmin.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