Thread

Re: 035_standby_logical_decoding might fail due to FATAL message lost inside libpq

Alexander Lakhin <exclusion@gmail.com> — 2026-05-27T17:00:01Z

Hello Kuroda-san,

27.05.2026 08:43, Hayato Kuroda (Fujitsu) wrote:
> Hi Alexander,
>
> I applied your reproducer atop my HEAD (12d00048), but I could not reproduce.
> ...
>
> The build can be done if I restore changes in src/meson.build, but I could not
> reproduce the failure if I run 035_standby_logicaldecoding.pl. Am I missing something?

I'm sorry, it looks like I had messed up with the patch. Please try the fixed one.
It makes the unmodified 035_standby_logical_decoding.pl fail for me as below:
  CPPFLAGS="-O0" ./configure -q --enable-debug --enable-tap-tests --enable-injection-points && make -s -j8 && 
PROVE_TESTS="t/035*" make -s check -C src/test/recovery/
...
# pg_recvlogical: error: could not send replication command "START_REPLICATION SLOT "drop_db_activeslot" LOGICAL 
0/00000000 ("include-xids" '0', "skip-empty-xacts" '1')": server closed the connection unexpectedly
#       This probably means the server terminated abnormally
#       before or while processing the request.
# pg_recvlogical: error: disconnected
# '
#     doesn't match '(?^:conflict with recovery)'
t/035_standby_logical_decoding.pl .. 87/? # Looks like you failed 1 test of 89.
t/035_standby_logical_decoding.pl .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/89 subtests

Best regards,
Alexander