Hey everybody,
I've an app where an own db gets created for each user which gets
replicated continuously to a big central db.
This works great, it gives me fantastic possibilities that wouldn't be
possible with other databases, I love it.
My problem is though, that at some point I run into the
On Tue, Dec 6, 2011 at 9:56 AM, Gregor Martynus gre...@martynus.net wrote:
Hey everybody,
I've an app where an own db gets created for each user which gets
replicated continuously to a big central db.
This works great, it gives me fantastic possibilities that wouldn't be
possible with other
Thanks Benoit, I know about this setting. But at some point, this won't
work anymore. My question is if there is any way to stop continuous
replications to keep the db files active changes have been replicated? Does
that make sense?
On Tue, Dec 6, 2011 at 10:08 AM, Benoit Chesneau
On Tue, Dec 6, 2011 at 10:11 AM, Gregor Martynus gre...@martynus.net wrote:
Thanks Benoit, I know about this setting. But at some point, this won't
work anymore. My question is if there is any way to stop continuous
replications to keep the db files active changes have been replicated? Does
Thanks Gregor for raising this question. I have a very similar setup and
I am also concerned about how it will scale.
g jo
Am Dienstag, den 06.12.2011, 10:29 +0100 schrieb Gregor Martynus:
Thanks Benoit!
I'm sorry to keep bugging ...
The problem is, at least for me, that I can't simply
On Tue, Dec 6, 2011 at 9:29 AM, Gregor Martynus gre...@martynus.net wrote:
What I really don't understand is, _why_ the continuous replication keep
the db files open? I'm not an Erlang developer at all, sorry if this is a
dump question/thought, but shouldn't the continuous replication be
