| From: | Jakub Janeček <jakub(dot)janecek(at)comgate(dot)cz> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL Cascade streaming replication problem |
| Date: | 2018-04-03 06:10:45 |
| Message-ID: | CANmq+oYmHE6PpT2O0S_3+CdWigkdaaNAeCEtjcJ35V3gH6EfBA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi everyone,
problem is solved.
There was a delay between setup (drop replication slot) and execution.
Jakub
2018-04-03 4:43 GMT+02:00 Michael Paquier <michael(at)paquier(dot)xyz>:
> On Sun, Apr 01, 2018 at 06:26:51PM +0000, Jakub Janeček wrote:
> > What did i do wrong? I need stop comulating WAL files and remove old WAL
> > files, which are processed and are only "waiting"..
>
> Perhaps wal_keep_segments is set and you forgot about it or you used a
> replication slot that you forgot to drop on slave 1?
> --
> Michael
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kein Name | 2018-04-03 06:36:45 | Autovacuum Problem |
| Previous Message | Jakub Janeček | 2018-04-03 05:56:06 | Re: PostgreSQL Cascade streaming replication problem |