[Question]standby mode apply log error

[marcohong]

pg_log messages

402874 2024-03-07 20:39:53.906 CST DEBUG: record known xact 4182810 latestObservedXid 4182810
402874 2024-03-07 20:39:53.906 CST CONTEXT: WAL redo at 13/400CD08
402874 2024-03-07 20:39:53.906 CST DEBUG: record known xact 4182810 latestObservedXid 4182810
402874 2024-03-07 20:39:53.906 CST CONTEXT: WAL redo at 13/400CD08
402874 2024-03-07 20:39:53.906 CST DEBUG: remove KnownAssignedXid 4182810
402874 2024-03-07 20:39:53.906 CST CONTEXT: WAL redo at 13/400CD08
402874 2024-03-07 20:39:53.906 CST DEBUG: record known xact 4182811 latestObservedXid 4182810
402874 2024-03-07 20:39:53.906 CST CONTEXT: WAL redo at 13/400CD30
402874 2024-03-07 20:39:53.906 CST DEBUG: polar_logindex_apply_page 42 13/4000000 13/400CD30, '[1663, 9346792, 9346800], 0, 4321'
402874 2024-03-07 20:39:53.906 CST DEBUG: '[1663, 9346792, 9346800], 0, 4321' search mem from tid=0
402874 2024-03-07 20:39:53.908 CST PANIC: Append buffer with a small oldest lsn than last buffer in flush list.
402874 2024-03-07 20:39:53.908 CST CONTEXT: WAL redo at 13/400CD30
402874 2024-03-07 20:39:53.908 CST BACKTRACE:
postgres(6544): startup recovering 000000010000001300000004(elog_finish+0x1b0) [0xa1c150]
postgres(6544): startup recovering 000000010000001300000004() [0x85519d]
postgres(6544): startup recovering 000000010000001300000004(polar_set_buffer_fake_oldest_lsn+0x7a) [0x84edaa]
postgres(6544): startup recovering 000000010000001300000004(MarkBufferDirty+0xd4) [0x84f084]
postgres(6544): startup recovering 000000010000001300000004() [0x4eda85]
postgres(6544): startup recovering 000000010000001300000004(heap_redo+0x2d5) [0x4fa8f5]
postgres(6544): startup recovering 000000010000001300000004(StartupXLOG+0xfe8) [0x5558f8]
postgres(6544): startup recovering 000000010000001300000004(StartupProcessMain+0x123) [0x7f1613]
postgres(6544): startup recovering 000000010000001300000004(AuxiliaryProcessMain+0x560) [0x594f40]
postgres(6544): startup recovering 000000010000001300000004() [0x7eca2f]
postgres(6544): startup recovering 000000010000001300000004(PostmasterMain+0xfce) [0x7f0f1e]
postgres(6544): startup recovering 000000010000001300000004(main+0x694) [0x4a9bc4]
/usr/lib64/libc.so.6(__libc_start_main+0xe7) [0x7f03348dab27]
postgres(6544): startup recovering 000000010000001300000004(_start+0x2a) [0x4a9c7a]
402879 2024-03-07 20:39:53.912 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:53.922 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:53.932 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:53.942 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:53.952 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:53.962 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:53.973 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:53.993 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:54.012 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:54.022 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:54.040 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:54.056 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:54.067 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402879 2024-03-07 20:39:54.077 CST DEBUG: polar_logindex_bg_dispatch: forward bg_replayed_lsn to 130400CD30
402875 2024-03-07 20:39:54.083 CST DEBUG: vfs_allocate_vfd. cache size 32

When starting in standby mode, the following error occurs: Append buffer with a small oldest lsn than last buffer in flush list

[polardb-bot]

Hi @marcohong ~ Thanks for opening this issue! 🎉

Please make sure you have provided enough information for subsequent discussion.

We will get back to you as soon as possible. ❤️