Tom,
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> It used to be that http://git.postgresql.org/gitweb/?p=postgresql.git
> would update within a minute or so after somebody pushed something.
The cronjob which syncs the between the git master and
git.postgresql.org appears to run once every 15 minutes (unchanged since
mid-2011). Given that commits simply aren't that frequent, I do
wonder if we could set that up as a trigger or similar instead of
polling for updates.
> This seems to have been broken for the last week or so; not only do
> commits not show up for a random amount of time, but the displayed
> age of the last commit is noticeably wrong.
The recent change was the addition of varnish to do cacheing in front
of git.postgresql.org to reduce load on the system. The cacheing was
set to 30m/1h, which does seem a bit high. I've lowered it down to
15m/30m. That should help some, but obviously isn't going to give
within-a-minute response time. I'll talk with the other admins and see
what we can do to improve it further.
Thanks,
Stephen