Re: [Bucardo-general] doubts about target db?
Thanks Rosser for your answer.
Other thing, with bucardo what is the difference between in a
master-master replica vs master-slave, at the end in both ways the
user has a 2nd DB with R/W permission?
Thanks.
On Thu, Oct 13, 2016 at 9:40 PM, Rosser Schwarz
<rosser.schwarz@gmail.com> wrote:
On Thursday, October 13, 2016, Periko Support <pheriko.support@gmail.com>
wrote:1) My target db must have all the tables created without data on it before
sync?Yes, tables must exist on the target. Generally, it's easiest to have them
empty, but the bigger concern is conflicts with data from the master.2) In a master-master or master slave, bucardo is best to be reside in the
main master side?It doesn't really matter, as long as it can reach all the dbs it's
managing. I've run it on the master, on the slave, and on another host
entirely.rls
--
:wq
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Import Notes
Reply to msg id not found: CAFnxYwh85uo1UjmFvVP98Er-G1xwdjUZtUj86ZjoyHOYVp7DnA@mail.gmail.comReference msg id not found: CAK2yrTb7EBTFgTk7dnU85Trpd9POE1sH-QRD8rnSjU8qGVtMZg@mail.gmail.comReference msg id not found: CAFnxYwh85uo1UjmFvVP98Er-G1xwdjUZtUj86ZjoyHOYVp7DnA@mail.gmail.com
Other thing, with bucardo what is the difference between in a
master-master replica vs master-slave, at the end in both ways the
user has a 2nd DB with R/W permission?
I think in a M-M mode, updates from both dbs will be replicated to the other db.
In other words they will be eventually consistent.
In a M-S mode, even though Slaves can be updated by the app, its updates will
not be replicated back to the master. While updates from M->S will happen all
the time, updates from S will not go to M.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Thanks Rakesh.
Let me explain my reason to have a replica server.
We run odoo server 7.x with ubuntu 14.
But we are working on a BI system right now(Pentaho), them we want to
run those heavy reports on the replica and let the current production
system on the master.
This is why I was thinking on a M-S setup.
Why don't u use PSQL built in replica tools? We try but exist a lets
behavior of odoo that if u run a report he try to update some internal
tables and won't allow us to run our reports in the slave(streaming
replica).
Because the slave is in a ReadOnly mode.
Them we start searching for a solution and we came to bucardo.
Now, the BI server will just for that.
What setup guys recommend, M-M or M-S for my solution?
Now let me think in the future, I can think on a M-M-S, If the
master-1 fails we have the 2nd and nothing happen right and our
current S will continue running, bucardo let me do this?
Now let me back in the setup of bucardo, we u are in the setup, how
can I told to bucardo is a M-M or M-S?
Sorry for to much question, I want to understand all this and make my
own manual, I see a lot of settings of bucardo in the man page but not
to much examples.
youtube and google are giving me a lot info.
Thanks for your time and help!!!
On Fri, Oct 14, 2016 at 8:54 AM, Rakesh Kumar
<rakeshkumar464@outlook.com> wrote:
Other thing, with bucardo what is the difference between in a
master-master replica vs master-slave, at the end in both ways the
user has a 2nd DB with R/W permission?I think in a M-M mode, updates from both dbs will be replicated to the other db.
In other words they will be eventually consistent.
In a M-S mode, even though Slaves can be updated by the app, its updates will
not be replicated back to the master. While updates from M->S will happen all
the time, updates from S will not go to M.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general