Re: [HACKERS] Automatic cleanup of oldest WAL segments with pg_receivexlog

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [HACKERS] Automatic cleanup of oldest WAL segments with pg_receivexlog
Дата
Msg-id CA+TgmoYy1oDM68Au_YK7_oLggkizY4YRBwrhqw7P36==en6RTg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Automatic cleanup of oldest WAL segments withpg_receivexlog  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: [HACKERS] Automatic cleanup of oldest WAL segments withpg_receivexlog  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
On Tue, Mar 7, 2017 at 11:08 AM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 3/6/17 17:16, Robert Haas wrote:
>> What if we told pg_receivewal (or pg_receivexlog, whatever that is) a
>> maximum number of segments to retain before removing old ones?  Like
>> pg_receivewal --limit-retained-segments=50GB, or something like that.
>
> That would be doable, but would it solve anyone's problem?  I think
> pg_receivewal retention would usually be governed either by the
> available base backups, or by some time-based business metric.

Well, if the problem you're trying to solve is "retain WAL for as long
as possible without running out of disk space and having everything go
kablooey", then it would solve that problem, and I think that's a very
reasonable problem to want to solve.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] Parallel bitmap heap scan
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] Partitioned tables and relfilenode