From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Commitfest app reports wrong patch as latest |
Date: | 2022-04-21 21:17:47 |
Message-ID: | 3541007.1650575867@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Thu, Apr 21, 2022 at 1:34 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Maybe so, because I just went back to the CF entry's page to
>> close it, and now it shows the right thing.
> I've noticed that http caching (I believe we use Varnish for this) is
> often behind problems that I run into with our web based
> infrastructure. Not that I have problems all that often, mind you.
I don't think it was an http-level issue, because the page showed the
wrong thing from inception, and reloading it didn't help. I am guessing
it was built from a stale view of what the end-of-thread was. Anyway, the
problem did go away eventually, so it was a cache problem somewhere.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2022-04-22 07:37:22 | Re: Commitfest app reports wrong patch as latest |
Previous Message | Peter Geoghegan | 2022-04-21 21:09:02 | Re: Commitfest app reports wrong patch as latest |