On Thu, Feb 22, 2024 at 4:35 PM Bertrand Drouvot <bertranddrouvot...@gmail.com> wrote: > > On Thu, Feb 22, 2024 at 04:01:34PM +0530, shveta malik wrote: > > On Thu, Feb 22, 2024 at 3:44 PM Bertrand Drouvot > > <bertranddrouvot...@gmail.com> wrote: > > > > > > Hi, > > > > > > Thanks! > > > > > > Some random comments about v92_001 (Sorry if it has already been discussed > > > up-thread): > > > > Thanks for the feedback. The patch is pushed 15 minutes back. > > Yeah, saw that after I send the comments ;-) >
There is a BF failure. See https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-02-22%2010%3A13%3A03. The initial analysis suggests that for some reason, the primary went down after the slot sync worker was invoked the first time. See the below in the primary's LOG: 2024-02-22 10:59:56.896 UTC [2721639:29] standby1_slotsync worker LOG: 00000: statement: SELECT slot_name, plugin, confirmed_flush_lsn, restart_lsn, catalog_xmin, two_phase, failover, database, conflict_reason FROM pg_catalog.pg_replication_slots WHERE failover and NOT temporary 2024-02-22 10:59:56.896 UTC [2721639:30] standby1_slotsync worker LOCATION: exec_simple_query, postgres.c:1070 2024-02-22 11:00:26.967 UTC [2721639:31] standby1_slotsync worker LOG: 00000: statement: SELECT slot_name, plugin, confirmed_flush_lsn, restart_lsn, catalog_xmin, two_phase, failover, database, conflict_reason FROM pg_catalog.pg_replication_slots WHERE failover and NOT temporary 2024-02-22 11:00:26.967 UTC [2721639:32] standby1_slotsync worker LOCATION: exec_simple_query, postgres.c:1070 2024-02-22 11:00:35.908 UTC [2721435:309] LOG: 00000: received immediate shutdown request 2024-02-22 11:00:35.908 UTC [2721435:310] LOCATION: process_pm_shutdown_request, postmaster.c:2859 2024-02-22 11:00:35.911 UTC [2721435:311] LOG: 00000: database system is shut down 2024-02-22 11:00:35.911 UTC [2721435:312] LOCATION: UnlinkLockFiles, miscinit.c:1138 -- With Regards, Amit Kapila.
