From: | Slavcho Trnkovski <strnkovski(at)gmail(dot)com> |
---|---|
To: | Bert <biertie(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: WAL retention |
Date: | 2016-06-21 15:26:12 |
Message-ID: | CACwHmfGiEDE4kTR+uAeBQThw0aOft4wkNVHXp6xu5cfEbMJHzQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
I use version 9.4.
If I create physical replication slot, I'll need standby server to use it.
I can use pg_receivexlog but it will not prevent removing WAL files, it
will just stream it to some other location.
Do you maybe have an idea how backup can use replication slot (without
standby)?
Regards,
Slavcho
On Mon, Jun 20, 2016 at 3:52 PM, Bert <biertie(at)gmail(dot)com> wrote:
> 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 | Keith | 2016-06-21 15:37:18 | Re: WAL retention |
Previous Message | Tom Lane | 2016-06-21 14:09:40 | Re: Too many Open files error for postgres |