Re: Error with GIT Repository - Mailing list pgsql-hackers

From Daniel Farina
Subject Re: Error with GIT Repository
Date
Msg-id AANLkTims8dSu_LtM3g6jisN47NuAvv9o1be_-9PS1eXY@mail.gmail.com
Whole thread Raw
In response to Re: Error with GIT Repository  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Fri, Jun 11, 2010 at 10:19 AM, Magnus Hagander <magnus@hagander.net> wrote:
>>> Especially if someone has a clue how to do it. The last time I fixed
>>> it by runnin repack, but that didn't work this time. I have no clue
>>> why it's asking for a file that doesn't exist.
>> Does the repo run  'update-server-info'  in some hook?
>
> Yup, it runs after every time it pulls from cvs.

Is this still a problem? I was just noticing this thread
unceremoniously died, and a long time ago now I remembering discussing
a problem involving the Postgres git mirror accumulating packfiles
eternally. It seemed that whatever repacking scheme was used would get
rid of loose objects, turning them into packs but never consolidate
packs.

Why not just run 'git gc'? This is probably the only quasi-regularly
required maintenance command, so much so that git (I think) runs it
from time to time when certain thresholds are passed in modern day.
(For a clone-source it is probably a good idea to run it a bit more
liberally)

fdr


pgsql-hackers by date:

Previous
From: Gibheer
Date:
Subject: Re: LLVM / clang
Next
From: Peter Eisentraut
Date:
Subject: Re: Check constraints on non-immutable keys