On 12.07.18 00:56, Mai Peng wrote:
> We discovered our pg_wal partition was full few days after setting our
> first logical publication on a PG 10.4 instance.
> Then, we can not synchronise our slave to the master, it triggers a
> segfault on the slave. We had to drop manually the subscription on slave
> and the slot on master.
> Then, we wanted to find the cause of this bug, stop connection between
> master and slave , after 30 minutes, the slave had a segfault and could
> not synchronise.
> Why does the slave can not synchronise without a complete creation
> subscription after dropping the slot?
Can you get a backtrace from the core dump produced by the segfault?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services