Date: Thu, 3 Sep 2026 08:10:16 -0500
From: Nathan Bossart <nathandbossart@gmail.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-www@postgresql.org
Subject: Re: archives frequently do not load today's messages
Message-ID: <aplxuPRx6dSRgVKN@nathan>
References: <aph9VVyVnatWGtPz@nathan>
 <CABUevEy_n=KcbOzEGy_T=tyKuuE1fQSazAhqpth-TNbkJjYP5w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CABUevEy_n=KcbOzEGy_T=tyKuuE1fQSazAhqpth-TNbkJjYP5w@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/aplxuPRx6dSRgVKN%40nathan>
Precedence: bulk

On Thu, Sep 03, 2026 at 01:07:31AM +0200, Magnus Hagander wrote:
> You're on the right track, but that's not the actual bug. But the
> increasing of the cache time has exposed a bug that has been there all
> along.
> 
> The bug is that *someone* hits the URL, in this case for Sep 2, when there
> are zero messages from Sep 2 yet. When that happens the empty page is
> cached but it's cached *without* the key that say it's in September. So
> when the first Sep 2 message actually arrives, it failes to to purge it
> because it purges everything in September only. Not in NULL.

Got it.

> I've pushed a fix for this now, I think (
> https://git.postgresql.org/gitweb/?p=pgarchives.git;a=commit;h=51485f825d7012fc5701900c2dfd562609fb1a06
> ).
> 
> It will take up to 12 hours for all the incorrectly taggred pages to expire
> from the cache.
> 
> Thanks for the report!

Thanks for fixing!

-- 
nathan