Re: Postgres 10, slave not catching up with master

Yes, as stated, the lag went very much down after disabling wal compression, it's manageable at least. Network is 10GB. Lep pozdrav, *Boris Sagadin* InfoSplet, informacijske tehnologije, d.o.o. *www.infosplet.com* | Tel: 0590 / 45 800, GSM: 041 / 337 848 On Wed, Oct

Re: Postgres 10, slave not catching up with master

Hi El mié., 24 de oct. de 2018 a la(s) 00:39, Boris Sagadin ( bo...@infosplet.com) escribió: > Yes, times are all identical, set to UTC, ntpd is used. > > log_delay > --- > 15.788175 > > This is delay at this moment, but we graph replication delay and it's > fluctuating between 0 and

Re: Postgres 10, slave not catching up with master

Yes, times are all identical, set to UTC, ntpd is used. log_delay --- 15.788175 This is delay at this moment, but we graph replication delay and it's fluctuating between 0 and 30s. Before I turned off wal compression, lag was much bigger (0 to up to 8 minutes). We have lots of tables

Re: Postgres 10, slave not catching up with master

Hi Both servers are configured with the same date, time and time configuration? El mar., 23 de oct. de 2018 a la(s) 13:16, Hellmuth Vargas (hiv...@gmail.com) escribió: > Hi > > which result you get from the following query: > > SELECT CASE WHEN pg_last_wal_receive_lsn() =

Re: Postgres 10, slave not catching up with master

Hi which result you get from the following query: SELECT CASE WHEN pg_last_wal_receive_lsn() = pg_last_wal_replay_lsn() THEN 0 ELSE EXTRACT (EPOCH FROM now() - pg_last_xact_replay_timestamp()) END AS log_delay; source: https://severalnines.com/blog/postgresql-streaming-replication-deep-dive

Re: Postgres 10, slave not catching up with master

Nothing special, just: standby_mode = 'on' primary_conninfo = 'host=... user=repmgr application_name=nodex' recovery_target_timeline = 'latest' Boris On Tue, Oct 23, 2018 at 3:10 PM, Hellmuth Vargas wrote: > Hi > > can share recovery.conf file settings?? > > El mar., 23 de oct. de 2018 a

Re: Postgres 10, slave not catching up with master

Hi can share recovery.conf file settings?? El mar., 23 de oct. de 2018 a la(s) 00:28, Boris Sagadin ( bo...@infosplet.com) escribió: > Yes, turning wal_compression off improves things. Slave that was mentioned > unfortunately lagged too much before this setting was applied and was > turned off.

Re: Postgres 10, slave not catching up with master

Yes, turning wal_compression off improves things. Slave that was mentioned unfortunately lagged too much before this setting was applied and was turned off. However the remaining slave lags less now, although still occasionally up to a few minutes. I think single threadedness of recovery is a big

Re: Postgres 10, slave not catching up with master

On 10/21/18 2:06 AM, Boris Sagadin wrote: Hello, I have a database running on i3.8xlarge (256GB RAM, 32 CPU cores, 4x 1.9TB NVMe drive) AWS instance with about 5TB of disk space occupied, ext4, Ubuntu 16.04. Multi-tenant DB with about 4 tables, insert heavy. I started a new slave with

Postgres 10, slave not catching up with master

Hello, I have a database running on i3.8xlarge (256GB RAM, 32 CPU cores, 4x 1.9TB NVMe drive) AWS instance with about 5TB of disk space occupied, ext4, Ubuntu 16.04. Multi-tenant DB with about 4 tables, insert heavy. I started a new slave with identical HW specs, SR. DB started syncing from