From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Logical replication and wal segment retention |
Date: | 2019-02-27 12:40:26 |
Message-ID: | 695C083D-AFB5-431B-B022-ED442CE94794@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello, folks,
Yesterday, I had a small file system fill up, due to some logical replication testing we had been performing. We had been testing IBM’s IIDR system and apparently it had built a logical replication slot on my server. When the test was completed, nobody removed the slot, so WAL segments stopped being dropped. Now I can understand the difficulty separating what physical versus logical replication needs from the WAL segments, but as logical replication is database specific not cluster wide, this behavior was a little unexpected, since the WAL segments are cluster wide. Are WAL segments going to pile up whenever something drops a logical replication connection? I’ve seen it, but it seems like this could be a bad thing.
-
Jay
Sent from my iPhone
From | Date | Subject | |
---|---|---|---|
Next Message | Johannes Truschnigg | 2019-02-27 12:52:42 | Re: Logical replication and wal segment retention |
Previous Message | Pepe TD Vo | 2019-02-27 11:37:51 | Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL |