Re: pg_receivelwal vs synchronous

2019-06-27 Thread Jesper Pedersen
Hi Magnus, On 6/27/19 8:37 AM, Magnus Hagander wrote: What am I missing here ? I believe your problem is remote_apply. pg_receivewal never *applies* any WAL, so it just updates the write and flush locations. Notice how the replay_lsn remains NULL. So you need synchronous_commit to be 'on' o

Re: pg_receivelwal vs synchronous

2019-06-27 Thread Magnus Hagander
On Wed, Jun 26, 2019 at 5:06 PM Jesper Pedersen wrote: > Hi, > > PostgreSQL 11.4 > > Given, > > postgresql.conf: > > wal_level = replica > synchronous_commit = remote_apply > synchronous_standby_names = '*' > > > CREATE ROLE repluser WITH LOGIN REPLICATION PASSWORD 'mypwd'; > SEL

pg_receivelwal vs synchronous

2019-06-26 Thread Jesper Pedersen
Hi, PostgreSQL 11.4 Given, postgresql.conf: wal_level = replica synchronous_commit = remote_apply synchronous_standby_names = '*' CREATE ROLE repluser WITH LOGIN REPLICATION PASSWORD 'mypwd'; SELECT pg_create_physical_replication_slot('replica1'); Execute pg_receivewal -D