På fredag 15. januar 2016 kl. 16:04:00, skrev Shulgin, Oleksandr <oleksandr.shulgin@xxxxxxxxxx>:
On Fri, Jan 15, 2016 at 3:41 PM, Andreas Joseph Krogh <andreas@xxxxxxxxxx> wrote:På fredag 15. januar 2016 kl. 14:33:24, skrev Shulgin, Oleksandr <oleksandr.shulgin@xxxxxxxxxx>:On Fri, Jan 15, 2016 at 1:02 PM, Andreas Joseph Krogh <andreas@xxxxxxxxxx> wrote:I see that wal_level = 'logical', and that is a problem for us as we already use wal_level = 'hot_standby' on this installation as it replicates to another server.Is it possible to use pglogical together with hot_standby streaming-replication?Well, the wal_level change is just a matter of database restart: you got to do that once in a while anyway, e.g. for minor version updates. I would expect you only need this wal_level on the walsender side, thus for pglogical_output, the logical decoding plugin.My point is that we cannot not have streaming-replication, so we need to keep wal_level = 'hot_standby' AFAIU. Is there a way to do both streaming-replication and pglogical for just replicating one of may databases in the same cluster?But logical is "greater than" hot_standby, so you can still have streaming replication with wal_level = logical.
This answers my initial question, thanks.
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
