From: | Bert <biertie(at)gmail(dot)com> |
---|---|
To: | Slavcho Trnkovski <strnkovski(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: WAL retention |
Date: | 2016-06-20 13:52:44 |
Message-ID: | CAFCtE1n2L7i6ySD+3F=e-KRm6POCC6Wu+U3FshRHN_hmpAsPZw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello,
Which version of PostgreSQL are you using?
If you are using version 9.4 or newer you can use the concept of
'replication slots' to block the removal or archiving of WAL files.
But do not forgot to remove the slot again, else PostgreSQL will never
remove the wall files again!
Bert
On Mon, Jun 20, 2016 at 10:38 AM, Slavcho Trnkovski <strnkovski(at)gmail(dot)com>
wrote:
> Hi Guys,
>
> Is there a way to set retention policy for removing WAL files in
> hours/days instead of number of WAL files (wal_keep_segments)?
>
> I have a problem when backup is running, it complains that some files are
> missing. The problem is that i have situation when data load is running and
> a lot of WAL files are generated.
>
> Regards,
> Slavcho
>
>
--
Bert Desmet
0477/305361
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Malek | 2016-06-20 14:15:22 | Re: problems using pg_start_backup/pg_stop_backup and pg_basebackup at same time |
Previous Message | Michael JOIGNY | 2016-06-20 10:29:01 | RAM/CPU running queries |