Re: Automatic cleanup of oldest WAL segments with pg_receivexlog

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, 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:58:11
Message-ID: 8b028df1-8b7a-9fb3-e259-6eff89aa0a79@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-02-24 03:01:12 Re: Automatic cleanup of oldest WAL segments with pg_receivexlog
Previous Message Andrew Dunstan 2017-02-24 02:57:26 Re: btree_gin and btree_gist for enums