| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:09:02 |
| Message-ID: | CAH2-WzmNMAqfucyWP4EYk4njSGQyEFpcBAB-3x7E_JAZwoc1Cg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
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.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-04-21 21:17:47 | Re: Commitfest app reports wrong patch as latest |
| Previous Message | Tom Lane | 2022-04-21 20:34:48 | Re: Commitfest app reports wrong patch as latest |