On 11/2/14 8:26 AM, Magnus Hagander wrote:
> The idea is to have pg_receivexlog
> fire off an external command at the end of each segment - for example
> a command to gzip the file, or to archive it off into a Magic Cloud
> (TM) or something like that.
A simple facility to allow gzipping after the
On 2014-11-02 14:33:32 +0100, Magnus Hagander wrote:
> On Sun, Nov 2, 2014 at 2:31 PM, Andres Freund wrote:
> > This will nead some persistent state about the commands success -
> > similar to the current archive status stuff. Given retries and
> > everything it might end up to be easier to have a
On Sun, Nov 2, 2014 at 2:31 PM, Andres Freund wrote:
> On 2014-11-02 14:26:04 +0100, Magnus Hagander wrote:
>> I had a discussion with a few people recently about a hack I wrote for
>> pg_receivexlog at some point, but never ended up submitting, and in
>> cleaning that up realized I had an open it
On 2014-11-02 14:26:04 +0100, Magnus Hagander wrote:
> I had a discussion with a few people recently about a hack I wrote for
> pg_receivexlog at some point, but never ended up submitting, and in
> cleaning that up realized I had an open item on it.
>
> The idea is to add a switch to pg_receivexlo
I had a discussion with a few people recently about a hack I wrote for
pg_receivexlog at some point, but never ended up submitting, and in
cleaning that up realized I had an open item on it.
The idea is to add a switch to pg_receivexlog (in this case, -a, but
that can always be bikeshedded ot cour