Magnus Hagander <magnus@hagander.net> writes:
> On Thu, Feb 19, 2015 at 5:01 PM, Andres Freund <andres@2ndquadrant.com>
> wrote:
>> It'll stay enabled/in effect for the future. But it'd be a good idea to
>> regularly schedule a repack independent of bitmaps - or enable automatic
>> gc's on push (not sure which version made that available). Right now
>> git.pg.o's postgresql.git is ~40MB bigger than my local one...
> Well, it does them now and then, IIRC? We haven't set up a cronjob for it,
> but I'm fairly certain I've gotten stuck with it doing GC during a commit
> someitme...
Yeah, I got one just a couple of minutes ago.
[postgres@sss1 pgsql]$ git push
Counting objects: 74, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (24/24), done.
Writing objects: 100% (24/24), 6.61 KiB | 0 bytes/s, done.
Total 24 (delta 20), reused 0 (delta 0)
Auto packing the repository for optimum performance.
To ssh://git@gitmaster.postgresql.org/postgresql.git c86f8f3..83c3115 REL9_2_STABLE -> REL9_2_STABLE
a196e67..f389b6e REL9_3_STABLE -> REL9_3_STABLE 66463a3..9c15a77 REL9_4_STABLE -> REL9_4_STABLE 64235fe..b26e208
master-> master
There was a noticeable delay after the "auto packing" message. I don't
mind this happening once in awhile, but I don't see a need to do it
on every commit; please let's not have auto-gc-on-commit. No opinion
about whether a cron job would be worth the trouble.
regards, tom lane
