1

I am configuring a bidirectional replication between node1 and node2. The configuration of node1 as publisher and node2 as subscriber is correct: the data is replicated and no errors occur. The reverse configuration (node2 as publisher and node1 as subscriber) is accepted but, when replication in this direction is required, the databases enter an automatic recovery loop.

I would like to understand whether this is actually a bug or if I am doing something wrong in the configuration. Thank you for your attention.

Below are the steps to reproduce my problem:

  • dbtest01 = node1
  • dbtest02 = node2

NB: The two nodes contain the same data. Two-way replication is on the same table (store_level) and is implemented using filters (on id_store field).

System info: OS: Linux myserver 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux Postgres: 15 pglogical: 2.4.2

Create databases

createdb -h 127.0.0.1 -U postgres dbtest01
createdb -h 127.0.0.1 -U postgres dbtest02

dbtest01: create tables

psql -h 127.0.0.1 -U postgres

\c dbtest01

create table store_level (
  id_item varchar(20) not null,
  id_store varchar(10) not null,
  quantity  decimal(12,3)
);

alter table store_level
add constraint pk_store_level
primary key (id_item, id_store);

dbtest01: add data

insert into store_level (id_item, id_store, quantity) values ('ITEM01', 'STORE_A', 10);
insert into store_level (id_item, id_store, quantity) values ('ITEM02', 'STORE_A', 11);
insert into store_level (id_item, id_store, quantity) values ('ITEM01', 'STORE_B', 12);
insert into store_level (id_item, id_store, quantity) values ('ITEM02', 'STORE_B', 13);
insert into store_level (id_item, id_store, quantity) values ('ITEM01', 'STORE_C', 14);
insert into store_level (id_item, id_store, quantity) values ('ITEM02', 'STORE_C', 15);

dbtest02: create tables

psql -h 127.0.0.1 -U postgres

\c dbtest02

create table store_level (
  id_item varchar(20) not null,
  id_store varchar(10) not null,
  quantity  decimal(12,3)
);

alter table store_level
add constraint pk_store_level
primary key (id_item, id_store);

dbtest02: add data

insert into store_level (id_item, id_store, quantity) values ('ITEM01', 'STORE_A', 10);
insert into store_level (id_item, id_store, quantity) values ('ITEM02', 'STORE_A', 11);
insert into store_level (id_item, id_store, quantity) values ('ITEM01', 'STORE_B', 12);
insert into store_level (id_item, id_store, quantity) values ('ITEM02', 'STORE_B', 13);
insert into store_level (id_item, id_store, quantity) values ('ITEM01', 'STORE_C', 14);
insert into store_level (id_item, id_store, quantity) values ('ITEM02', 'STORE_C', 15);

dbtest01: define publisher

\c dbtest01

CREATE EXTENSION IF NOT EXISTS pglogical;

GRANT USAGE ON SCHEMA pglogical TO postgres;
GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA pglogical TO postgres;

SELECT pglogical.create_node(
    node_name := 'node1',
    dsn := 'host=127.0.0.1 port=5432 dbname=dbtest01 user=postgres password=MyPassword'
);

SELECT pglogical.create_replication_set(
    set_name := 'replication_set_a1'
);


SELECT pglogical.replication_set_add_table(set_name := 'replication_set_a1', relation := 'public.store_level',     synchronize_data := false, row_filter := 'id_store <> ''STORE_B''');

dbtest02: define subscriber

\c dbtest02

CREATE EXTENSION IF NOT EXISTS pglogical;

GRANT USAGE ON SCHEMA pglogical TO postgres;
GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA pglogical TO postgres;

SELECT pglogical.create_node(
    node_name := 'node2',
    dsn := 'host=192.168.1.56 port=5432 dbname=dbtest02 user=postgres password=MyPassword'
);


SELECT pglogical.create_subscription(
    subscription_name := 'sub_node2_to_node1',
    provider_dsn := 'host=127.0.0.1 port=5432 dbname=dbtest01 user=postgres password=MyPassword',
    replication_sets := ARRAY['replication_set_a1'],
    synchronize_structure := false,
    synchronize_data := false
);

dbtest01: update data

After applying the following update, replication behaves correctly. update store_level set quantity = 100 + quantity;

INVERSE REPLICATION: FROM NODE2 TO NODE1

dbtest02: define publisher

SELECT pglogical.create_replication_set(
    set_name := 'replication_set_a2'
);


SELECT pglogical.replication_set_add_table(set_name := 'replication_set_a2', relation := 'public.store_level',
synchronize_data := false, row_filter := 'id_store = ''STORE_B''');

dbtest01: define subscriber

\c dbtest01

SELECT pglogical.create_subscription(
    subscription_name := 'sub_node1_to_node2',
    provider_dsn := 'host=127.0.0.1 port=5432 dbname=dbtest02 user=postgres password=MyPassword',
    replication_sets := ARRAY['replication_set_a2'],
    synchronize_structure := false,
    synchronize_data := false
);

dbtest02: update data

The following instruction causes the error and sends the database into a loop. update store_level set quantity = 1000 + quantity;

Log content follows (/etc/postgresql/15/main/postgresql.conf)


2025-10-13 11:06:00.743 CEST [92108] [sconosciuto]@postgres LOG:  manager worker [92108] at slot 2 generation 9 detaching cleanly
2025-10-13 11:06:00.743 CEST [92109] [sconosciuto]@dbtest01 LOG:  starting apply for subscription sub_node1_to_node2
2025-10-13 11:06:00.752 CEST [92112] [sconosciuto]@template1 LOG:  manager worker [92112] at slot 2 generation 11 detaching cleanly
2025-10-13 11:06:00.786 CEST [92115] postgres@dbtest02 LOG:  la decodifica logica ha trovato un punto consistente a D/B5208258
2025-10-13 11:06:00.786 CEST [92115] postgres@dbtest02 DETTAGLI:  Non ci sono transazioni in corso.
2025-10-13 11:06:00.786 CEST [92115] postgres@dbtest02 ISTRUZIONE:  CREATE_REPLICATION_SLOT "pgl_dbtest01_node2_sub_nodeeb86277" LOGICAL pglogical_output
2025-10-13 11:06:00.787 CEST [92115] postgres@dbtest02 LOG:  snapshot di decidifica logica esportati: "00000016-0000E67E-1" con 0 ID di transazione
2025-10-13 11:06:00.787 CEST [92115] postgres@dbtest02 ISTRUZIONE:  CREATE_REPLICATION_SLOT "pgl_dbtest01_node2_sub_nodeeb86277" LOGICAL pglogical_output
2025-10-13 11:06:00.807 CEST [92119] postgres@dbtest02 LOG:  avvio della decodifica logica per lo slot "pgl_dbtest01_node2_sub_nodeeb86277"
2025-10-13 11:06:00.807 CEST [92119] postgres@dbtest02 DETTAGLI:  Commit delle transazioni streaming dopo D/B5208290, lettura del WAL dopo D/B5208258.
2025-10-13 11:06:00.807 CEST [92119] postgres@dbtest02 ISTRUZIONE:  START_REPLICATION SLOT "pgl_dbtest01_node2_sub_nodeeb86277" LOGICAL D/B5208290 (expected_encoding 'UTF8', min_proto_version '1', max_proto_version '1', startup_params_format '1', "binary.want_internal_basetypes" '1', "binary.want_binary_basetypes" '1', "binary.basetypes_major_version" '1500', "binary.sizeof_datum" '8', "binary.sizeof_int" '4', "binary.sizeof_long" '8', "binary.bigendian" '0', "binary.float4_byval" '0', "binary.float8_byval" '1', "binary.integer_datetimes" '0', "hooks.setup_function" 'pglogical.pglogical_hooks_setup', "pglogical.forward_origins" '"all"', "pglogical.replication_set_names" 'replication_set_a2', "relmeta_cache_size" '-1', pg_version '150002', pglogical_version '2.4.2', pglogical_version_num '20402', pglogical_apply_pid '92109')
2025-10-13 11:06:00.807 CEST [92119] postgres@dbtest02 LOG:  la decodifica logica ha trovato un punto consistente a D/B5208258
2025-10-13 11:06:00.807 CEST [92119] postgres@dbtest02 DETTAGLI:  Non ci sono transazioni in corso.
2025-10-13 11:06:00.807 CEST [92119] postgres@dbtest02 ISTRUZIONE:  START_REPLICATION SLOT "pgl_dbtest01_node2_sub_nodeeb86277" LOGICAL D/B5208290 (expected_encoding 'UTF8', min_proto_version '1', max_proto_version '1', startup_params_format '1', "binary.want_internal_basetypes" '1', "binary.want_binary_basetypes" '1', "binary.basetypes_major_version" '1500', "binary.sizeof_datum" '8', "binary.sizeof_int" '4', "binary.sizeof_long" '8', "binary.bigendian" '0', "binary.float4_byval" '0', "binary.float8_byval" '1', "binary.integer_datetimes" '0', "hooks.setup_function" 'pglogical.pglogical_hooks_setup', "pglogical.forward_origins" '"all"', "pglogical.replication_set_names" 'replication_set_a2', "relmeta_cache_size" '-1', pg_version '150002', pglogical_version '2.4.2', pglogical_version_num '20402', pglogical_apply_pid '92109')
2025-10-13 11:06:50.529 CEST [92109] [sconosciuto]@dbtest01 LOG:  CONFLICT: remote UPDATE on relation public.store_level (local index pk_store_level). Resolution: apply_remote.
2025-10-13 11:06:50.529 CEST [92109] [sconosciuto]@dbtest01 DETTAGLI:  existing local tuple {id_item[varchar]:ITEM01 id_store[varchar]:STORE_B quantity[numeric]:112.000} xid=537434,origin=0,timestamp=2025-10-13 10:59:16.883319+02; remote tuple {id_item[varchar]:ITEM01 id_store[varchar]:STORE_B quantity[numeric]:1012.000} in xact origin=7,timestamp=2025-10-13 11:06:50.527877+02,commit_lsn=0/B5208C10
2025-10-13 11:06:50.529 CEST [92109] [sconosciuto]@dbtest01 CONTESTO:  apply UPDATE from remote relation public.store_level in commit before D/B5208C10, xid 537442 committed at 2025-10-13 11:06:50.527877+02 (action #2) from node replorigin 7
2025-10-13 11:06:50.530 CEST [92109] [sconosciuto]@dbtest01 LOG:  CONFLICT: remote UPDATE on relation public.store_level (local index pk_store_level). Resolution: apply_remote.
2025-10-13 11:06:50.530 CEST [92109] [sconosciuto]@dbtest01 DETTAGLI:  existing local tuple {id_item[varchar]:ITEM02 id_store[varchar]:STORE_B quantity[numeric]:113.000} xid=537434,origin=0,timestamp=2025-10-13 10:59:16.883319+02; remote tuple {id_item[varchar]:ITEM02 id_store[varchar]:STORE_B quantity[numeric]:1013.000} in xact origin=7,timestamp=2025-10-13 11:06:50.527877+02,commit_lsn=0/B5208C10
2025-10-13 11:06:50.530 CEST [92109] [sconosciuto]@dbtest01 CONTESTO:  apply UPDATE from remote relation public.store_level in commit before D/B5208C10, xid 537442 committed at 2025-10-13 11:06:50.527877+02 (action #3) from node replorigin 7
2025-10-13 11:06:50.532 CEST [92010] postgres@dbtest01 LOG:  ricezione dati dal client fallita: Connessione interrotta dal corrispondente
2025-10-13 11:06:50.532 CEST [92010] postgres@dbtest01 ISTRUZIONE:  START_REPLICATION SLOT "pgl_dbtest02_node1_sub_node3f3d779" LOGICAL D/B5201308 (expected_encoding 'UTF8', min_proto_version '1', max_proto_version '1', startup_params_format '1', "binary.want_internal_basetypes" '1', "binary.want_binary_basetypes" '1', "binary.basetypes_major_version" '1500', "binary.sizeof_datum" '8', "binary.sizeof_int" '4', "binary.sizeof_long" '8', "binary.bigendian" '0', "binary.float4_byval" '0', "binary.float8_byval" '1', "binary.integer_datetimes" '0', "hooks.setup_function" 'pglogical.pglogical_hooks_setup', "pglogical.forward_origins" '"all"', "pglogical.replication_set_names" 'replication_set_a1', "relmeta_cache_size" '-1', pg_version '150002', pglogical_version '2.4.2', pglogical_version_num '20402', pglogical_apply_pid '91999')
2025-10-13 11:06:50.532 CEST [92010] postgres@dbtest01 LOG:  fine del file inaspettato sulla connessione di standby
2025-10-13 11:06:50.532 CEST [92010] postgres@dbtest01 ISTRUZIONE:  START_REPLICATION SLOT "pgl_dbtest02_node1_sub_node3f3d779" LOGICAL D/B5201308 (expected_encoding 'UTF8', min_proto_version '1', max_proto_version '1', startup_params_format '1', "binary.want_internal_basetypes" '1', "binary.want_binary_basetypes" '1', "binary.basetypes_major_version" '1500', "binary.sizeof_datum" '8', "binary.sizeof_int" '4', "binary.sizeof_long" '8', "binary.bigendian" '0', "binary.float4_byval" '0', "binary.float8_byval" '1', "binary.integer_datetimes" '0', "hooks.setup_function" 'pglogical.pglogical_hooks_setup', "pglogical.forward_origins" '"all"', "pglogical.replication_set_names" 'replication_set_a1', "relmeta_cache_size" '-1', pg_version '150002', pglogical_version '2.4.2', pglogical_version_num '20402', pglogical_apply_pid '91999')
2025-10-13 11:06:50.532 CEST [57369] LOG:  processo di lavoro in background "pglogical apply 1272091:1060992920" (PID 91999) è stato terminato dal segnale 11: Errore di segmentazione
2025-10-13 11:06:50.532 CEST [57369] LOG:  interruzione di tutti gli altri processi attivi del server
2025-10-13 11:06:50.587 CEST [57369] LOG:  tutti i processi server sono terminati; re-inizializzazione
2025-10-13 11:06:51.055 CEST [92130] LOG:  il database è stato interrotto; l'ultimo segno di vita risale alle 2025-10-13 11:00:30 CEST
2025-10-13 11:06:53.899 CEST [92130] LOG:  il database non è stato arrestato correttamente; ripristino automatico in corso
2025-10-13 11:06:53.902 CEST [92130] LOG:  stato di replica ripristinato dal nodo 1 a 4/43E38E0
2025-10-13 11:06:53.902 CEST [92130] LOG:  stato di replica ripristinato dal nodo 2 a C/90274FF0
2025-10-13 11:06:53.902 CEST [92130] LOG:  stato di replica ripristinato dal nodo 3 a C/90210310
2025-10-13 11:06:53.902 CEST [92130] LOG:  stato di replica ripristinato dal nodo 4 a B/6BD06ED8
2025-10-13 11:06:53.902 CEST [92130] LOG:  stato di replica ripristinato dal nodo 5 a C/9020EA10
2025-10-13 11:06:53.902 CEST [92130] LOG:  stato di replica ripristinato dal nodo 6 a D/B5201C50
2025-10-13 11:06:53.925 CEST [92130] LOG:  il redo inizia in D/B5202050
2025-10-13 11:06:53.926 CEST [92130] LOG:  lunghezza del record a D/B5208F30 non valida: atteso 24, ricevuto 0
2025-10-13 11:06:53.926 CEST [92130] LOG:  ripetizione eseguita con utilizzo del sistema D/B5208EE8: CPU: utente: 0.00 s, sistema: 0.00 s, passati: 0.00 s
2025-10-13 11:06:53.973 CEST [92131] LOG:  inizio checkpoint: end-of-recovery immediate wait
2025-10-13 11:06:54.010 CEST [92131] LOG:  checkpoint completato: ha scritto 42 buffer (0.0%); 0 file WAL aggiunti, 0 rimossi, 0 riciclati; scrittura=0.029 s, sincronizzazione=0.004 s, totale=0.039 s; file di sincronizzazione=36, più lungo=0.002 s, medio=0.001 s; distanza=27 kB, stima=27 kB
2025-10-13 11:06:54.015 CEST [57369] LOG:  il database è pronto ad accettare connessioni
2025-10-13 11:06:54.016 CEST [92135] LOG:  starting pglogical supervisor
2025-10-13 11:06:54.023 CEST [92137] [sconosciuto]@postgres LOG:  manager worker [92137] at slot 0 generation 1 detaching cleanly
2025-10-13 11:06:54.040 CEST [92139] [sconosciuto]@template1 LOG:  manager worker [92139] at slot 0 generation 3 detaching cleanly
2025-10-13 11:06:54.090 CEST [92145] [sconosciuto]@dbtest01 LOG:  starting pglogical database manager for database dbtest01
2025-10-13 11:06:54.094 CEST [92146] [sconosciuto]@dbtest01 LOG:  starting apply for subscription sub_node1_to_node2
2025-10-13 11:06:54.115 CEST [92147] postgres@dbtest02 LOG:  avvio della decodifica logica per lo slot "pgl_dbtest01_node2_sub_nodeeb86277"
2025-10-13 11:06:54.115 CEST [92147] postgres@dbtest02 DETTAGLI:  Commit delle transazioni streaming dopo D/B5208860, lettura del WAL dopo D/B5208860.
2025-10-13 11:06:54.115 CEST [92147] postgres@dbtest02 ISTRUZIONE:  START_REPLICATION SLOT "pgl_dbtest01_node2_sub_nodeeb86277" LOGICAL D/B5208C40 (expected_encoding 'UTF8', min_proto_version '1', max_proto_version '1', startup_params_format '1', "binary.want_internal_basetypes" '1', "binary.want_binary_basetypes" '1', "binary.basetypes_major_version" '1500', "binary.sizeof_datum" '8', "binary.sizeof_int" '4', "binary.sizeof_long" '8', "binary.bigendian" '0', "binary.float4_byval" '0', "binary.float8_byval" '1', "binary.integer_datetimes" '0', "hooks.setup_function" 'pglogical.pglogical_hooks_setup', "pglogical.forward_origins" '"all"', "pglogical.replication_set_names" 'replication_set_a2', "relmeta_cache_size" '-1', pg_version '150002', pglogical_version '2.4.2', pglogical_version_num '20402', pglogical_apply_pid '92146')
2025-10-13 11:06:54.115 CEST [92147] postgres@dbtest02 LOG:  la decodifica logica ha trovato un punto consistente a D/B5208860
2025-10-13 11:06:54.115 CEST [92147] postgres@dbtest02 DETTAGLI:  Non ci sono transazioni in corso.
2025-10-13 11:06:54.115 CEST [92147] postgres@dbtest02 ISTRUZIONE:  START_REPLICATION SLOT "pgl_dbtest01_node2_sub_nodeeb86277" LOGICAL D/B5208C40 (expected_encoding 'UTF8', min_proto_version '1', max_proto_version '1', startup_params_format '1', "binary.want_internal_basetypes" '1', "binary.want_binary_basetypes" '1', "binary.basetypes_major_version" '1500', "binary.sizeof_datum" '8', "binary.sizeof_int" '4', "binary.sizeof_long" '8', "binary.bigendian" '0', "binary.float4_byval" '0', "binary.float8_byval" '1', "binary.integer_datetimes" '0', "hooks.setup_function" 'pglogical.pglogical_hooks_setup', "pglogical.forward_origins" '"all"', "pglogical.replication_set_names" 'replication_set_a2', "relmeta_cache_size" '-1', pg_version '150002', pglogical_version '2.4.2', pglogical_version_num '20402', pglogical_apply_pid '92146')
2025-10-13 11:06:55.089 CEST [92148] [sconosciuto]@dbtest02 LOG:  starting pglogical database manager for database dbtest02
2025-10-13 11:06:55.092 CEST [92149] [sconosciuto]@dbtest02 LOG:  starting apply for subscription sub_node2_to_node1
2025-10-13 11:06:55.110 CEST [92150] postgres@dbtest01 LOG:  D/B5201C50 has been already streamed, forwarding to D/B5208860
2025-10-13 11:06:55.110 CEST [92150] postgres@dbtest01 ISTRUZIONE:  START_REPLICATION SLOT "pgl_dbtest02_node1_sub_node3f3d779" LOGICAL D/B5201C50 (expected_encoding 'UTF8', min_proto_version '1', max_proto_version '1', startup_params_format '1', "binary.want_internal_basetypes" '1', "binary.want_binary_basetypes" '1', "binary.basetypes_major_version" '1500', "binary.sizeof_datum" '8', "binary.sizeof_int" '4', "binary.sizeof_long" '8', "binary.bigendian" '0', "binary.float4_byval" '0', "binary.float8_byval" '1', "binary.integer_datetimes" '0', "hooks.setup_function" 'pglogical.pglogical_hooks_setup', "pglogical.forward_origins" '"all"', "pglogical.replication_set_names" 'replication_set_a1', "relmeta_cache_size" '-1', pg_version '150002', pglogical_version '2.4.2', pglogical_version_num '20402', pglogical_apply_pid '92149')
2025-10-13 11:06:55.111 CEST [92150] postgres@dbtest01 LOG:  avvio della decodifica logica per lo slot "pgl_dbtest02_node1_sub_node3f3d779"
2025-10-13 11:06:55.111 CEST [92150] postgres@dbtest01 DETTAGLI:  Commit delle transazioni streaming dopo D/B5208860, lettura del WAL dopo D/B5208860.
2025-10-13 11:06:55.111 CEST [92150] postgres@dbtest01 ISTRUZIONE:  START_REPLICATION SLOT "pgl_dbtest02_node1_sub_node3f3d779" LOGICAL D/B5201C50 (expected_encoding 'UTF8', min_proto_version '1', max_proto_version '1', startup_params_format '1', "binary.want_internal_basetypes" '1', "binary.want_binary_basetypes" '1', "binary.basetypes_major_version" '1500', "binary.sizeof_datum" '8', "binary.sizeof_int" '4', "binary.sizeof_long" '8', "binary.bigendian" '0', "binary.float4_byval" '0', "binary.float8_byval" '1', "binary.integer_datetimes" '0', "hooks.setup_function" 'pglogical.pglogical_hooks_setup', "pglogical.forward_origins" '"all"', "pglogical.replication_set_names" 'replication_set_a1', "relmeta_cache_size" '-1', pg_version '150002', pglogical_version '2.4.2', pglogical_version_num '20402', pglogical_apply_pid '92149')
2025-10-13 11:06:55.111 CEST [92150] postgres@dbtest01 LOG:  la decodifica logica ha trovato un punto consistente a D/B5208860
2025-10-13 11:06:55.111 CEST [92150] postgres@dbtest01 DETTAGLI:  Non ci sono transazioni in corso.
2025-10-13 11:06:55.111 CEST [92150] postgres@dbtest01 ISTRUZIONE:  START_REPLICATION SLOT "pgl_dbtest02_node1_sub_node3f3d779" LOGICAL D/B5201C50 (expected_encoding 'UTF8', min_proto_version '1', max_proto_version '1', startup_params_format '1', "binary.want_internal_basetypes" '1', "binary.want_binary_basetypes" '1', "binary.basetypes_major_version" '1500', "binary.sizeof_datum" '8', "binary.sizeof_int" '4', "binary.sizeof_long" '8', "binary.bigendian" '0', "binary.float4_byval" '0', "binary.float8_byval" '1', "binary.integer_datetimes" '0', "hooks.setup_function" 'pglogical.pglogical_hooks_setup', "pglogical.forward_origins" '"all"', "pglogical.replication_set_names" 'replication_set_a1', "relmeta_cache_size" '-1', pg_version '150002', pglogical_version '2.4.2', pglogical_version_num '20402', pglogical_apply_pid '92149')
2025-10-13 11:06:55.112 CEST [57369] LOG:  processo di lavoro in background "pglogical apply 1272091:1060992920" (PID 92149) è stato terminato dal segnale 11: Errore di segmentazione
2025-10-13 11:06:55.112 CEST [57369] LOG:  interruzione di tutti gli altri processi attivi del server
2025-10-13 11:06:55.116 CEST [57369] LOG:  tutti i processi server sono terminati; re-inizializzazione
2025-10-13 11:06:55.315 CEST [92151] LOG:  il database è stato interrotto; l'ultimo segno di vita risale alle 2025-10-13 11:06:54 CEST
2025-10-13 11:06:58.173 CEST [92151] LOG:  il database non è stato arrestato correttamente; ripristino automatico in corso
2025-10-13 11:06:58.176 CEST [92151] LOG:  stato di replica ripristinato dal nodo 1 a 4/43E38E0
2025-10-13 11:06:58.176 CEST [92151] LOG:  stato di replica ripristinato dal nodo 2 a C/90274FF0
2025-10-13 11:06:58.176 CEST [92151] LOG:  stato di replica ripristinato dal nodo 3 a C/90210310
2025-10-13 11:06:58.176 CEST [92151] LOG:  stato di replica ripristinato dal nodo 4 a B/6BD06ED8
2025-10-13 11:06:58.176 CEST [92151] LOG:  stato di replica ripristinato dal nodo 5 a C/9020EA10
2025-10-13 11:06:58.176 CEST [92151] LOG:  stato di replica ripristinato dal nodo 6 a D/B5201C50
2025-10-13 11:06:58.176 CEST [92151] LOG:  stato di replica ripristinato dal nodo 7 a D/B5208C40
2025-10-13 11:06:58.198 CEST [92151] LOG:  lunghezza del record a D/B5208FA8 non valida: atteso 24, ricevuto 0
2025-10-13 11:06:58.198 CEST [92151] LOG:  redo non richiesto
2025-10-13 11:06:58.245 CEST [92152] LOG:  inizio checkpoint: end-of-recovery immediate wait
2025-10-13 11:06:58.278 CEST [92152] LOG:  checkpoint completato: ha scritto 2 buffer (0.0%); 0 file WAL aggiunti, 0 rimossi, 0 riciclati; scrittura=0.027 s, sincronizzazione=0.002 s, totale=0.035 s; file di sincronizzazione=3, più lungo=0.001 s, medio=0.001 s; distanza=0 kB, stima=0 kB
2025-10-13 11:06:58.283 CEST [57369] LOG:  il database è pronto ad accettare connessioni

... -> loop
Improve this question
1
  • 2
    No idea about pglogical, but with normal logical replication you need at least v16, so that you can create the subscription with origin = none to avoid loops. Commented Oct 13 at 11:05

1 Answer 1

Reset to default
1

Through testing, we were able to determine that the problem was in the default value of the forward_origins parameter of the SELECT pglogical.create_subscription(...) procedure.

The documentation at https://github.com/2ndQuadrant/pglogical specifies that the forward_origins parameter identifies an "array of origin names to forward" and, by default, value is'{all}'.

In our tests, we set it to a null array '{}' and the replication works. Therefore, the correct subscription (in any direction) is:

SELECT pglogical.create_subscription(
    subscription_name := 'sub_node1_to_node2',
    provider_dsn := 'host=127.0.0.1 port=5432 dbname=dbtest02 user=postgres password=MyPAssword',
    replication_sets := ARRAY['replication_set_a2'],
    synchronize_structure := false,
    synchronize_data := false, 
    forward_origins := '{}' 
);
Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.