From: | Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_receivewal documentation |
Date: | 2019-07-18 12:39:48 |
Message-ID: | e62fcdf7-556c-d4e1-73cd-fc325f89374d@redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Laurenz,
On 7/17/19 5:21 PM, Laurenz Albe wrote:
> That's factually wrong. "on" (wait for WAL flush) works fine with
> pg_receivewal, only "remote_apply" doesn't.
>
Please, try
mkdir /tmp/wal
initdb /tmp/pgsql
pg_ctl -D /tmp/pgsql -l /tmp/logfile start
psql postgres
SELECT pg_create_physical_replication_slot('replica1');
CREATE ROLE repluser WITH LOGIN REPLICATION PASSWORD 'replpass';
\q
synchronous_commit = on
synchronous_standby_names = 'replica1'
pg_ctl -D /tmp/pgsql -l /tmp/logfile restart
pg_receivewal -D /tmp/wal -S replica1 --synchronous -h localhost -p 5432
-U repluser -W
psql -c 'SELECT * FROM pg_stat_replication;' postgres
psql -c 'SELECT * FROM pg_replication_slots;' postgres
psql -c 'CREATE DATABASE test' postgres
In what scenarios do you see 'on' working ?
Best regards,
Jesper
From | Date | Subject | |
---|---|---|---|
Next Message | Jesper Pedersen | 2019-07-18 12:40:36 | Re: pg_receivewal documentation |
Previous Message | Konstantin Knizhnik | 2019-07-18 12:10:35 | Re: Built-in connection pooler |