Re: [patch] pg_copy - a command for reliable WAL archiving

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, MauMau <maumau307(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [patch] pg_copy - a command for reliable WAL archiving
Date: 2014-08-15 15:47:51
Message-ID: 1408117671.17900.YahooMailNeo@web122304.mail.ne1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:

> Direct I/O and posix_fadvise are used only for destination file.
> But why not source file? That might be useful especially for
> restore_command case.

That would prevent people from piping the file through a
compression utility.  We should support piped I/O for input (and if
we want to use it on the recovery side, for the output, too), at
least as an option.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2014-08-15 15:52:46 Re: pg_dump bug in 9.4beta2 and HEAD
Previous Message Pavel Stehule 2014-08-15 15:31:54 Re: pg_dump bug in 9.4beta2 and HEAD