> One question to this: Why not simply use 'compressed protocol' for the
> connection?
Alright, the question below is regarding A) binlog size and B) transaction
log size as well as
bandwidth, the compressed client protocol does not address either issue,
but does make accessing the data transparent
One question to this: Why not simply use 'compressed protocol' for the
connection?
Peter
Webyog
On Fri, Sep 30, 2011 at 22:31, wrote:
> ---
> WORKLOG TASK
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
One question: why not use 'compressed protocol' then?
Peter
Webyog
On Fri, Sep 30, 2011 at 22:31, wrote:
> ---
> WORKLOG TASK
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
---
WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...: client-side compressed types
CREATION DATE..: Fri, 30 Sep 2011, 20:31
SUPERVISOR.:
IMPLEME
4 matches
Mail list logo