GCSAdmin writes:
> We add new event types to support compress the binlog as follow:
> QUERY_COMPRESSED_EVENT,
> WRITE_ROWS_COMPRESSED_EVENT_V1,
> UPDATE_ROWS_COMPRESSED_EVENT_V1,
> DELETE_POWS_COMPRESSED_EVENT_V1,
> WRITE_ROWS_COMPRESSED_EVENT,
>> +#define BINLOG_COMPRESSED_HEADER_LEN 1
>> +#define BINLOG_COMPRESSED_ORIGINAL_LENGTH_MAX_BYTES 4
>> +/**
>> + Compressed Record
>> +Record Header: 1 Byte
>> + 0 Bit: Always 1, mean compressed;
>> + 1-3 Bit: Reversed, compressed algorithm??Always
0,
How easy will it be for this to use a lower latency compression algorithm
like lz4, Snappy or zstandard?
On Thu, Oct 20, 2016 at 2:52 PM, Daniel Black
wrote:
> >> +#define BINLOG_COMPRESSED_HEADER_LEN 1
> >> +#define BINLOG_COMPRESSED_ORIGINAL_LENGTH_MAX_BYTES 4
> >>
3 matches
Mail list logo