Hello.
But please, detalize how Slony uses LISTEN/NOTIFY and why, if it uses
LISTEN/NOTIFY, it still generates poll queries instead of sitting and
waiting for a NOTIFY event. I cannot find this information in the Slony
documentation.
My main goal is NOT to reduce the lag to zero, but - reduce it as much as
possible without bombing the master by polling queries. E.g. lag 0.2s is
allowed, but 5 polling queries per second is too much.
On 5/12/07, Andrew Sullivan <[EMAIL PROTECTED]> wrote:
On Sat, May 12, 2007 at 02:47:14AM +0400, Dmitry Koterov wrote:
> So, the question is: how to make the Slony to update slaves as fast as
> possible without bombing the master with periodical queries? And - what
is
> the detailed meaning of sync_interval?
There isn't a way to update the slaves as fast as possible without
the queries, although more recent code reduces the LISTEN/NOTIFY
dependency. But this is _async_ replication. If you want perfect
copies, it can't do what you want. It's always going to lag some.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
Everything that happens in the world happens at some place.
--Jane Jacobs
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
