From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Automatic cleanup of oldest WAL segments with pg_receivexlog |
Date: | 2017-02-24 02:52:16 |
Message-ID: | CAB7nPqT6o5Hk2uEU_9rMxLC3vCdNmPhDharDKdB9Pos-oOW-tg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 24, 2017 at 1:10 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> I'm not sure this logic belongs in pg_receivexlog. If we put the decision
> making there, then we lock ourselves into one "type of policy".
>
> Wouldn't this one, along with some other scenarios, be better provided by
> the "run command at end of segment" function that we've talked about before?
> And then that external command could implement whatever aging logic would be
> appropriate for the environment?
OK, I forgot a bit about this past discussion. So let's say that we
have a command, why not also allow users to use at will a marker %f to
indicate the file name just completed? One use case here is to scan
the file for the oldest and/or newest timestamps of the segment just
finished to do some retention policy with something else in charge of
the cleanup.
The option name would be --end-segment-command? Any better ideas of names?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2017-02-24 02:56:03 | Re: Automatic cleanup of oldest WAL segments with pg_receivexlog |
Previous Message | Robert Haas | 2017-02-24 02:48:54 | Re: Documentation improvements for partitioning |