Re: [HACKERS] Automatic cleanup of oldest WAL segments with pg_receivexlog - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: [HACKERS] Automatic cleanup of oldest WAL segments with pg_receivexlog
Date
Msg-id CABUevEwvphmvrpf4+vYZbG_75G-pH=00+82pU-Tkg3W2_3FWbw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Automatic cleanup of oldest WAL segments with pg_receivexlog  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] Automatic cleanup of oldest WAL segments with pg_receivexlog
List pgsql-hackers
On Feb 25, 2017 15:00, "Michael Paquier" <michael.paquier@gmail.com> wrote:
On Sat, Feb 25, 2017 at 10:32 PM, Magnus Hagander <magnus@hagander.net> wrote:
> Oh, I definitely think such a command should be able to take a placeholder
> like %f telling which segment it has just processed. In fact, I'd consider
> it one of the most important features of it :)

I cannot think about any other meaningful variables, do you?

Not offhand. But one thing that could go to the question of parameter name - what if we finish something that's not a segment. During a time line switch for example, we also get other files don't we? We probably want to trigger at least some command in that case - either with an argument or by a different parameter? 

/Magnus 

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)
Next
From: Dilip Kumar
Date:
Subject: Re: [HACKERS] Enabling parallelism for queries coming from SQL orother PL functions