Horton
Menu

Re: Two issues leading to discrepancies in FSM data on the standby server

Melanie Plageman <melanieplageman@gmail.com>

View thread
From: Melanie Plageman <melanieplageman@gmail.com>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Alexey Makhmutov <a.makhmutov@postgrespro.ru>, Andrey Borodin <x4mmm@yandex-team.ru>, pgsql-hackers@postgresql.org
Date: 2026-04-30T21:57:19Z
Lists: pgsql-hackers 
On Wed, Apr 22, 2026 at 10:15 AM Melanie Plageman
<melanieplageman@gmail.com> wrote:
>
> On Wed, Apr 22, 2026 at 8:32 AM Alexander Korotkov <aekorotkov@gmail.com> wrote:
>
> > > It is a bug that is causing overly optimistic FSM
> > > numbers, but it's not a correctness issue like wrong results/data
> > > corruption etc. So, I think you could make an argument either way
> > > about fixing it.
> >
> > It has user-visible effect of increased insertion time after replica
> > promotion.  I think this is quite a reason to backpatch.
>
> Right, since it's not invasive, I'm fine with backpatching.

Alexander, are you planning on committing this?

- Melanie

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Mark modified the FSM buffer as dirty during recovery