On 02/03/2015 10:27 AM, Michael Paquier wrote:
On Tue, Feb 3, 2015 at 4:25 PM, Heikki Linnakangas
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
--status-interval
Yes, that's indeed
On Tue, Feb 3, 2015 at 4:25 PM, Heikki Linnakangas
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
> --status-interval
Yes, that's indeed better. As long as I am on it, attached is a
On 02/03/2015 05:59 AM, Michael Paquier wrote:
Hi all,
Per $subject, I noticed that a markup was missing in the description
of the option --synchronous.
+Issue sync commands as soon as there is WAL data which has
+not been flushed yet. Also status packets are sent back to the
Hi all,
Per $subject, I noticed that a markup was missing in the description
of the option --synchronous.
Patch is attached.
Regards,
--
Michael
diff --git a/doc/src/sgml/ref/pg_receivexlog.sgml b/doc/src/sgml/ref/pg_receivexlog.sgml
index be321b5..9405f0f 100644
--- a/doc/src/sgml/ref/pg_receive
