| From: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fan Liu <fan(dot)liu(at)ericsson(dot)com> |
| Cc: | Sergei Kornilov <sk(at)zsrv(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: why wal_max_size does not work? |
| Date: | 2020-03-27 06:36:25 |
| Message-ID: | CAJGNTeNUr_HSRR+heFUZzb6sLbhX=KPWQovRp4tjEJn31rDEWg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, 27 Mar 2020 at 01:10, Fan Liu <fan(dot)liu(at)ericsson(dot)com> wrote:
>
> So, I wan to know under what kind of scenario that there will not be recycling old WAL files.
> Is there any way I can check the recycling? For example, logs?
>
please, i would like to see the contents of postgresql.base.conf',
maybe is changing a parameter that is not touched in postgresql.conf,
and postgresql.auto.conf for the same reason
also, show us the output of: select * from pg_replication_slots
if there's any replication slot not connected to the server is
protecting, primary will keep the wals until the server comes back
finally, while this seems not to be your case, a high
wal_keep_segments can cause this problem too
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fan Liu | 2020-03-27 07:12:02 | RE: why wal_max_size does not work? |
| Previous Message | Fan Liu | 2020-03-27 06:10:05 | RE: why wal_max_size does not work? |