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

From Jim Nasby
Subject Re: [HACKERS] Automatic cleanup of oldest WAL segments withpg_receivexlog
Date
Msg-id 8b028df1-8b7a-9fb3-e259-6eff89aa0a79@BlueTreble.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  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On 2/23/17 8:52 PM, Michael Paquier wrote:
> 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.

Why not provide % replacements that contain that info? pg_receivexlog 
has a much better shot at doing that correctly than some random user tool...

(%f could certainly be useful for other things)
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [HACKERS] btree_gin and btree_gist for enums
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Automatic cleanup of oldest WAL segments with pg_receivexlog