[Bucardo-general] Latency on delete
Greg Sabino Mullane
greg at endpoint.com
Sun Jan 19 22:10:04 UTC 2014
On Fri, Jan 17, 2014 at 11:27:39AM -0500, Alex Balashov wrote:
> But still, am I right to assume that the deletion of any given row
> won't return, as a statement, until the trigger that pushes that
> delta into the Bucardo tables returns? It's a fairly "synchronous"
> process, right?
Yes, that's correct. But that's a pretty fast process, the big delay
I was referring to was when Bucardo has to delete lots of rows on
the targets. That number of rows means a fairly long query.
> >If you are using the latest Bucardo and going to multiple targets,
> >I just pushed an optimization that should help that case, so git pull
> >and try again :)
> I'm not, I'm using the 4.5.0 tarball from the web site. What's the
Rather than delete from the targets one by one, we now do all of them
at once by using asychronous queries. It's not so much a new optimization
as a bug fix, as we meant to be doing that all along. :)
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 163 bytes
Desc: Digital signature
More information about the Bucardo-general