Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCbqP-00067m-8D for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2013 20:18:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UCbqO-0005oG-Og for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2013 20:18:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCbqN-0005nZ-RR for pgsql-www@postgresql.org; Mon, 04 Mar 2013 20:18:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCbqI-0007HH-4m for pgsql-www@postgresql.org; Mon, 04 Mar 2013 20:18:43 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id r24KI6tC016678; Mon, 4 Mar 2013 15:18:06 -0500 (EST) From: Tom Lane To: Magnus Hagander cc: Alvaro Herrera , Andres Freund , Kevin Grittner , Peter Eisentraut , PostgreSQL WWW , Stephen Frost Subject: Re: gitweb is no longer a real-time view In-reply-to: References: <20130304020324.GE16142@tamriel.snowman.net> <2480.1362363162@sss.pgh.pa.us> <20130304023335.GH16142@tamriel.snowman.net> <20130304125013.GB3943@awork2.anarazel.de> <20130304143349.GX9507@alvh.no-ip.org> <20130304143852.GH3943@awork2.anarazel.de> <20130304145842.GZ9507@alvh.no-ip.org> <20130304150344.GK3943@awork2.anarazel.de> <20130304151127.GB9507@alvh.no-ip.org> <5564.1362410250@sss.pgh.pa.us> Comments: In-reply-to Magnus Hagander message dated "Mon, 04 Mar 2013 16:31:15 +0100" Date: Mon, 04 Mar 2013 15:18:06 -0500 Message-ID: <16677.1362428286@sss.pgh.pa.us> X-Pg-Spam-Score: -2.5 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-www Precedence: bulk Sender: pgsql-www-owner@postgresql.org Magnus Hagander writes: > And yes, the cache purging appears to be broken *as well*. The reason > for that one seems to be that I forgot to update the port number for > cache invalidation when I moved it into production. Oops. That should > start working on the next commit that someone does. Seemed to work when I pushed the tm2timestamp fix just now --- the front page updated almost immediately after the next top-of-minute. Thanks. regards, tom lane -- Sent via pgsql-www mailing list (pgsql-www@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www