1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
Transaction Log
===============
Description
-----------
The Drizzle Transaction Log contains a sequence of
`Google Protocol Buffer <http://code.google.com/p/protobuf/>`_
messages that describe the transactions which have been run.
Configuration
-------------
Several server variables control the transaction log.
**transaction-log.enable**
Enable transaction log.
**transaction-log.enable-checksum**
Enable CRC32 Checksumming of each written transaction log entry
**transaction-log.file**
Path to the file to use for transaction log. The default will be
:file:`transaction.log`.
**transaction-log.use-replicator**
Name of the replicator plugin to use (default='default_replicator')
**transaction-log.flush-frequency**
* 0 : rely on operating system to sync log file (default)
* 1 : sync file at each transaction write
* 2 : sync log file once per second
**transaction-log.num-write-buffers**
Number of slots for in-memory write buffers (default=8).
Transaction Log Messages
------------------------
Replication events are recorded using messages in the `Google Protocol Buffer
<http://code.google.com/p/protobuf/>`_ (GPB) format. See the :doc:`Replication
documentation </replication>` for more information.
Transaction Log Format
----------------------
Currently, the transaction log file uses a simple, single-file, append-only
format. The format of each entry in the transaction log file is::
4-bytes 4-bytes
+--------------+--------------+----------------------+
| Entry Type | Length | Serialized Message |
+--------------+--------------+----------------------+
The fields in the entry are:
* **Entry Type** - Type of message this entry contains. Currently,
this is always a Transaction GPB message.
* **Length** - The length, in bytes, of the serialized message.
* **Serialized Message** - The actual message data.
|