Re: Fix slot synchronization with two_phase decoding enabled

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix slot synchronization with two_phase decoding enabled
Date: 2025-05-03 17:23:51
Message-ID: 2183957.1746293031@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

BF member mule just showed what seems an identical failure [1]:

2025-05-03 17:46:20.088 CEST [24308:3] LOG: database system is ready to accept read-only connections
2025-05-03 17:46:20.091 CEST [24321:1] LOG: slot sync worker started
2025-05-03 17:46:20.100 CEST [24322:1] LOG: started streaming WAL from primary at 0/6000000 on timeline 1
2025-05-03 17:46:20.117 CEST [24321:2] LOG: starting logical decoding for slot "lsub1_slot"
2025-05-03 17:46:20.117 CEST [24321:3] DETAIL: Streaming transactions committing after 0/60049C8, reading WAL from 0/5000048.
2025-05-03 17:46:20.117 CEST [24321:4] LOG: logical decoding found consistent point at 0/5000048
2025-05-03 17:46:20.117 CEST [24321:5] DETAIL: There are no running transactions.
TRAP: failed Assert("slot->data.two_phase_at <= slot->data.confirmed_flush"), File: "slotsync.c", Line: 311, PID: 24321
postgres: standby1: slotsync worker (ExceptionalCondition+0x59)[0x556c3b8cb3e9]
postgres: standby1: slotsync worker (+0x4cb100)[0x556c3b706100]
postgres: standby1: slotsync worker (+0x4cba4c)[0x556c3b706a4c]
postgres: standby1: slotsync worker (ReplSlotSyncWorkerMain+0x258)[0x556c3b707598]
postgres: standby1: slotsync worker (postmaster_child_launch+0x102)[0x556c3b6d6962]
postgres: standby1: slotsync worker (+0x49daea)[0x556c3b6d8aea]
postgres: standby1: slotsync worker (+0x49fb3d)[0x556c3b6dab3d]
postgres: standby1: slotsync worker (PostmasterMain+0xd3f)[0x556c3b6dc04f]
postgres: standby1: slotsync worker (main+0x1ca)[0x556c3b3bee1a]
/lib/x86_64-linux-gnu/libc.so.6(+0x2724a)[0x7fe08da4824a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7fe08da48305]
postgres: standby1: slotsync worker (_start+0x21)[0x556c3b3bf421]
2025-05-03 17:46:20.337 CEST [24308:4] LOG: slot sync worker process (PID 24321) was terminated by signal 6: Aborted

regards, tom lane

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mule&dt=2025-05-03%2015%3A30%3A02

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tanin Na Nakorn 2025-05-03 18:30:44 pg_dump to support "on conflict do update"
Previous Message Bruce Momjian 2025-05-03 16:56:16 Re: PG 18 release notes draft committed