PostgreSQL keeps WAL segments not required by any replication slot
| От | Andrey Zhidenkov |
|---|---|
| Тема | PostgreSQL keeps WAL segments not required by any replication slot |
| Дата | |
| Msg-id | CAJw4d1UCqk1t5BzJKjw-9oZ+rQ8o=EPwRKwqsLBA74rWA1N11g@mail.gmail.com обсуждение исходный текст |
| Список | pgsql-admin |
I have wal_keep_segments set to 3000. But directory pg_xlog contains more than 6000 WAL segments. Interesting thing that there are ~ 3000 files dated after Aug 14, so files dated before Aug 14 should not be exists, I guess. Also these files have an executable bit set. $ ls -al pg_xlog | grep -A2 -B2 00000001000034DB0000003B -rwx------ 1 postgres postgres 16777216 Jul 19 07:58 00000001000034DB00000039 -rwx------ 1 postgres postgres 16777216 Jul 19 07:58 00000001000034DB0000003A -rwx------ 1 postgres postgres 16777216 Jul 19 07:58 00000001000034DB0000003B -rw------- 1 postgres postgres 16777216 Aug 14 19:17 0000000100003826000000EA -rw------- 1 postgres postgres 16777216 Aug 14 19:17 0000000100003826000000EB ``` This cluster has no replication slots, archive_mode is enabled but archive_command is set to /bin/true. I think the new WAL segments are recycled and total amount is about 6000 but postgres does not delete the old files for some reason. Any ideas? -- With best regards, Andrey Zhidenkov.
В списке pgsql-admin по дате отправления: