Re: PostgreSQL 13 - Logical Replication - ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF detected

Le ven. 19 mai 2023 à 05:02, Kyotaro Horiguchi a écrit : > At Thu, 18 May 2023 21:00:08 +0100, FOUTE K. Jaurès > wrote in > > Hello everyone, > > > > I have a replication between PostgreSQL 12 to 13 in the production > system. > > Using Ubuntu 18.04 LTS > > We have this error today. > > > > > >

Re: PostgreSQL 13 - Logical Replication - ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF detected

At Thu, 18 May 2023 21:00:08 +0100, FOUTE K. Jaurès wrote in > Hello everyone, > > I have a replication between PostgreSQL 12 to 13 in the production system. > Using Ubuntu 18.04 LTS > We have this error today. > > > > *2023-05-18 18:34:04.374 WAT [117322] ERROR: could not receive data from

PostgreSQL 13 - Logical Replication - ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF detected

Hello everyone, I have a replication between PostgreSQL 12 to 13 in the production system. Using Ubuntu 18.04 LTS We have this error today. *2023-05-18 18:34:04.374 WAT [117322] ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF detected2023-05-18 18:34:04.381 WAT [118393] L

Re: Logical replication - ERROR: could not send data to WAL stream: cannot allocate memory for input buffer

Thanks for the comment. from what I was able to monitor memory usage was almost stable and there were about 20GB allocated as cached memory. Memory overcommit is disabled on the database server. Might it be a memory issue, since wit was synchronizing newly added tables with a sum of 380 GB of data

Replication error

I"m running postgres DB on docker & database replication have been enabled. After configuring repmgr not able to switch over/failover operation.DB & errors details are provided below. Please help on this. * ssh -o Batchmode=yes -q -o ConnectTimeout=10 10.0.0.76 /usr/lib/postgresql/9.4/bin/repmg

Re: Logical replication - ERROR: could not send data to WAL stream: cannot allocate memory for input buffer

On Fri, Jun 05, 2020 at 10:57:46PM +0200, Aleš Zelený wrote: > we are using logical replication for more than 2 years and today I've found > new not yet know error message from wal receiver. The replication was in > catchup mode (on publisher side some new tables were created and added to > publica

Logical replication - ERROR: could not send data to WAL stream: cannot allocate memory for input buffer

Hello, we are using logical replication for more than 2 years and today I've found new not yet know error message from wal receiver. The replication was in catchup mode (on publisher side some new tables were created and added to publication, on subscriber side they were missing). RDBMS version:P

Logical Replication ERROR reporting issue

Hello Folks, We are having the issue with Logical Replication in Postgres 10.11 production environment that unable to get around. Following is the production environment configuration *PostgreSQL Version: 10.11OS: Ubuntu 16.04.3 LTS (Xenial Xerus)* The error message frequently occurring in the