On Tue, Feb 3, 2015 at 4:25 PM, Heikki Linnakangas
<[email protected]> wrote:
> Flush the WAL data to disk immediately after it's being received. Also send
> a status packet back to the server immediately after flushing, regardless of
> <literal>--status-interval</>
Yes, that's indeed better. As long as I am on it, attached is a patch
for that...
--
Michael
diff --git a/doc/src/sgml/ref/pg_receivexlog.sgml b/doc/src/sgml/ref/pg_receivexlog.sgml
index be321b5..0c99744 100644
--- a/doc/src/sgml/ref/pg_receivexlog.sgml
+++ b/doc/src/sgml/ref/pg_receivexlog.sgml
@@ -139,9 +139,9 @@ PostgreSQL documentation
<term><option>--synchronous</option></term>
<listitem>
<para>
- Issue sync commands as soon as there is WAL data which has not been
- flushed yet. Also status packets are sent back to the server just after
- WAL data is flushed whatever <literal>--status-interval</> is set to.
+ Flush the WAL data to disk immediately after it has been received. Also
+ send a status packet back to the server immediately after flushing,
+ regardless of <literal>--status-interval</>.
</para>
</listitem>
</varlistentry>
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
