the publisher and the subscriber run on the same postgres instance. Regards, Fabrice
On Fri, Sep 17, 2021 at 12:26 PM Amit Kapila <amit.kapil...@gmail.com> wrote: > On Fri, Sep 17, 2021 at 3:29 PM Fabrice Chapuis <fabrice636...@gmail.com> > wrote: > > > > Hi, > > > > Logical replication is configured on one instance in version 10.18. > Timeout errors occur regularly and the worker process exit with an exit > code 1 > > > > 2021-09-16 12:06:50 CEST [24881]: [1-1] > user=postgres,db=foo,client=[local] LOG: duration: 1281408.171 ms > statement: COPY schem.tab (col1, col2) FROM stdin; > > 2021-09-16 12:07:11 CEST [12161]: [1-1] user=,db=,client= LOG: > automatic analyze of table "foo.schem.tab" system usage: CPU: user: 4.13 s, > system: 0.55 s, elapsed: 9.58 s > > 2021-09-16 12:07:50 CEST [3770]: [2-1] user=,db=,client= ERROR: > terminating logical replication worker due to timeout > > 2021-09-16 12:07:50 CEST [12546]: [11-1] user=,db=,client= LOG: worker > process: logical replication worker for subscription 24106654 (PID 3770) > exited with exit code 1 > > 2021-09-16 12:07:50 CEST [13872]: [1-1] user=,db=,client= LOG: logical > replication apply worker for subscription "subxxxx" has started > > 2021-09-16 12:07:50 CEST [13873]: [1-1] > user=repuser,db=foo,client=127.0.0.1 LOG: received replication command: > IDENTIFY_SYSTEM > > > > Can you share the publisher-side log as well? > > > -- > With Regards, > Amit Kapila. >
