MIME-Version: 1.0
In-Reply-To: 
 <CABUevEwtGteDPeGbGi9=_KiRnYynY5k9i0RjF0F8teanNDQmQQ@mail.gmail.com>
References: 
 <CAA-aLv5=zyB6S4Oa-xerqGPb3ek1qSOt7RLHBYTcuVX-pC-ACQ@mail.gmail.com>
	<8080.1362941506@sss.pgh.pa.us>
	<CA+OCxoyw8MYjf4cyKM5kGpz--xQ44V_wvM-sUxmHDFCrj4tbHg@mail.gmail.com>
	<CAA-aLv6N81KcAL_8mb56EaVp3SdCoZsaLckyrPMYATKpRacJmA@mail.gmail.com>
	<CABUevEwtGteDPeGbGi9=_KiRnYynY5k9i0RjF0F8teanNDQmQQ@mail.gmail.com>
Date: Sat, 13 Apr 2013 16:50:12 +0200
Message-ID: 
 <CABUevExCmnohMdUwwmN24EdTbpyNFCaUymcYNcQbFnA=sBM9iw@mail.gmail.com>
Subject: Re: Git lag
From: Magnus Hagander <magnus@hagander.net>
To: Thom Brown <thom@linux.com>
Cc: Dave Page <dpage@pgadmin.org>, Tom Lane <tgl@sss.pgh.pa.us>,
	"w^3" <pgsql-www@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org

On Tue, Mar 12, 2013 at 3:12 PM, Magnus Hagander <magnus@hagander.net> wrote:
> On Sun, Mar 10, 2013 at 7:56 PM, Thom Brown <thom@linux.com> wrote:
>> On 10 March 2013 18:54, Dave Page <dpage@pgadmin.org> wrote:
>>> On Sun, Mar 10, 2013 at 6:51 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>>> Thom Brown <thom@linux.com> writes:
>>>>> There was a commit by Tom Lane approximately 30 mins ago, yet I'm
>>>>> still unable to pull those changes into my local repo.  I'm told it's
>>>>> up-to-date, but the latest commit was Magnus' pg_hba line number
>>>>> logging change.
>>>>
>>>> That's really weird, because that commit did show up on
>>>> http://git.postgresql.org/gitweb/?p=postgresql.git
>>>> almost immediately.  I had the idea that gitweb was looking at the
>>>> same anonymous-access git repo that non-committers should pull from.
>>>> Maybe there's a third repo involved?
>>>
>>> There's not, but there is some caching that can happen if you're
>>> pulling the repo via http (I forget the exact details). Try using the
>>> git:// URL instead Thom.
>>
>> Ah okay, yes, changed my .git/config to use git:// and all is well
>> again.  Sorry for the noise.
>
> Not at all - Dave is actually at least partially wrong here, and I'm
> pretty sure I broke something. There were stil some issues before with
> http pulls, but they have unfortunately been made quite a lot worse :)
> I'll look at getting that sorted as soon a I can.
>
> Basically, there used to be an update issue. But now that we do full
> caching on the data, the fixes that are in there to work around the
> previous issue, don't necessarily work anymore...

With lots of delay, this should be fixed now. Sorry about that.

Other ways of pulling are still *faster* than http, but there should
be no extra delay in it.

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


-- 
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www