Do you happen to have a record of the time you first saw the problem?
I can see that the file you got has been in the closest cache for a bit over two hours. When you sent your report in an hour ago, was that right when you had the problem, or could there have been time between when you got the error out and when you sent the email, and that the actual attempt could have been more than 2 hours ago?
If not - some weird behavior happened. I have multiple psql clusters hidden under same public IP (NAT) and now I can't see the same behavior at any node of the farm.
Thank you.
Vojtěch Dušátko
On 18/02/26 15:17, Magnus Hagander wrote:
On Wed, 18 Feb 2026 at 14:41, Christoph Berg <myon@debian.org> wrote:
Re: Vojtěch Dušátko > Release file created at: Thu, 12 Feb 2026 11:13:19 +0000
We've had several reports about this problems, afaict all with this timestamp. The actual file is newer.
The cloud CDN in front is probably caching bad things there...
Maybe the PG infra admins could check?
Hi!
This problem is still ongoing, right? Could you run: