From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Automatic cleanup of oldest WAL segments with pg_receivexlog |
Date: | 2017-02-25 15:41:51 |
Message-ID: | CABUevEwvphmvrpf4+vYZbG_75G-pH=00+82pU-Tkg3W2_3FWbw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Feb 25, 2017 15:00, "Michael Paquier" <michael(dot)paquier(at)gmail(dot)com> wrote:
On Sat, Feb 25, 2017 at 10:32 PM, Magnus Hagander <magnus(at)hagander(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2017-02-25 16:17:36 | Re: Enabling parallelism for queries coming from SQL or other PL functions |
Previous Message | Bruce Momjian | 2017-02-25 14:12:42 | Re: Patch: Write Amplification Reduction Method (WARM) |