| From: | Vik Fearing <vik(at)2ndquadrant(dot)fr> |
|---|---|
| To: | Scott Moynes <scott(at)vmfarms(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: WAL files not being recycled |
| Date: | 2016-05-17 01:31:30 |
| Message-ID: | 573A7472.30400@2ndquadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 17/05/16 00:54, Scott Moynes wrote:
> wal_keep_segments is set to 32.
>
> Here is the replication slot:
>
> slot_name |
> n6lbb2vmohwuxoyk_00018732_f58b5354_79ad_4e6e_b18b_47acb1d7ce1f
> plugin | test_decoding
> slot_type | logical
> datoid | 18732
> database | omitted
> active | f
> xmin |
> catalog_xmin | 84884044
> restart_lsn | 1B3/4300CA60
>
> Can an inactive replication slot cause WALs to be retained?
Absolutely! That's what they're for.
If you don't expect this slot to re-become active, you should drop it.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Kehlet | 2016-05-17 01:57:26 | Re: preventing ERROR: multixact "members" limit exceeded |
| Previous Message | Alvaro Herrera | 2016-05-17 01:18:45 | Re: preventing ERROR: multixact "members" limit exceeded |