On 13.06.2012 14:28, Andres Freund wrote:
A logical WALReceiver is started directly by Postmaster when we enter PM_RUN
state and the new parameter multimaster_conninfo is set. For now only one of
those is started, but the code doesn't rely on that. In future multiple ones
should be allowed.
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
On 13.06.2012 14:28, Andres Freund wrote:
A logical WALReceiver is started directly by Postmaster when we
enter PM_RUN state and the new parameter multimaster_conninfo is
set. For now only one of those is started, but the code
On Friday, June 29, 2012 05:16:11 PM Heikki Linnakangas wrote:
On 13.06.2012 14:28, Andres Freund wrote:
A logical WALReceiver is started directly by Postmaster when we enter
PM_RUN state and the new parameter multimaster_conninfo is set. For now
only one of those is started, but the code
On 29.06.2012 18:28, Kevin Grittner wrote:
It would be nice if there was at least a thin layer of the sender
portion which could by used by a stand-alone program. I can think
of lots of useful reasons to T the WAL stream -- passing through
the stream with little or no modification to at least
From: Andres Freund and...@anarazel.de
A logical WALReceiver is started directly by Postmaster when we enter PM_RUN
state and the new parameter multimaster_conninfo is set. For now only one of
those is started, but the code doesn't rely on that. In future multiple ones
should be allowed.
To
