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

From Peter Eisentraut
Subject Re: [HACKERS] Automatic cleanup of oldest WAL segments withpg_receivexlog
Date
Msg-id d39bcee1-e028-ab3d-b4ed-acdc6574da46@2ndquadrant.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/27/17 00:32, Michael Paquier wrote:
> On Sun, Feb 26, 2017 at 8:24 AM, Michael Paquier
> <michael.paquier@gmail.com> wrote:
>> To be consistent with archive_command and restore_command I'd rather
>> not do that. The command called can decide by itself what to do by
>> looking at the shape of the argument string.
> Just before the CF begins, I have taken some time to build up a patch
> that implements this --end-segment-command, with %f as placeholder.

I think this repeats all the mistakes of archive_command, which
ironically pg_receivexlog was intended to fix, such as: shell commands
not fully portable, improper fsync support, poor error handling, lack of
integration with synchronous replication, inability to handle multiple
actions properly.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] PATCH: two slab-like memory allocators
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Use asynchronous connect API in libpqwalreceiver