Jobin Augustine wrote:
Voting for these views..
this is a must have feature to monitor replication.
suppose one logfile is missed in transmission or corrupt in DR side.
(i mean, checksum is failing for unknown reason)
Hi! Due to your comment above, I've added a column for the
transaction's checksum to the TRANSACTION_LOG_TRANSACTIONS view.
There is only a single log file in Drizzle's transaction log, unlike the
segmented MySQL binlog. So, there is only a single record in the
TRANSACTION_LOG view.
and want to know the content of that file (Entires).
how will the query look like?
I have written a UDF which outputs the raw information contained in the
Transaction message called PRINT_TRANSACTION_MESSAGE(). I'll post
examples of usage later on tomorrow after I'm done with the new test
cases validating the new I_S views.
Cheers!
jay
resending because i missed the team.
Thank You Jay,
-Jobin
2009/11/7 Jay Pipes <[email protected]>
Hi all,
I'm in the process of adding INFORMATION_SCHEMA tables/views to facilitate
getting information about the log and its contents via a standard SELECT
statement.
Here is what I have come up with in regards to the structure of the views.
Please let me know if you'd like other information or have suggestions for
column naming or anything else. Thanks!
CREATE TABLE INFORMATION_SCHEMA.TRANSACTION_LOG (
FILE_NAME VARCHAR NOT NULL
, FILE_LENGTH BIGINT NOT NULL
, NUM_LOG_ENTRIES BIGINT NOT NULL
, NUM_TRANSACTIONS BIGINT NOT NULL
, MIN_TRANSACTION_ID BIGINT NOT NULL
, MAX_TRANSACTION_ID BIGINT NOT NULL
, MIN_TIMESTAMP BIGINT NOT NULL
, MAX_TIMESTAMP BIGINT NOT NULL
);
CREATE TABLE INFORMATION_SCHEMA.TRANSACTION_LOG_ENTRIES (
ENTRY_OFFSET BIGINT NOT NULL
, ENTRY_TYPE VARCHAR NOT NULL
, ENTRY_LENGTH BIGINT NOT NULL
);
CREATE TABLE INFORMATION_SCHEMA.TRANSACTION_LOG_TRANSACTIONS (
ENTRY_OFFSET BIGINT NOT NULL
, TRANSACTION_ID BIGINT NOT NULL
, SERVER_ID INT NOT NULL
, START_TIMESTAMP BIGINT NOT NULL
, END_TIMESTAMP BIGINT NOT NULL
, NUM_STATEMENTS INT NOT NULL
);
In addition to the above views, I am creating a UDF called
PRINT_TRANSACTION_MESSAGE() which will output the raw contents of the
transaction messages in the transaction log.
What the above means is that no separate mysqlbinlog-type program will be
necessary to fully query the transaction log state on a server. This should
make reporting and monitoring of the transaction log easier and more
self-contained, allowing tool-makers to issue standard SELECT statements for
querying the transaction log.
FYI, don't confuse the above views with the replication system. While the
replication system may use the transaction log, it will have separate views
which provide replication-specific information (similar to SHOW MASTER
STATUS etc.)
Cheers, and thanks in advance for any input!
Jay
_______________________________________________
Mailing list:
https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss>
Post to : [email protected]
Unsubscribe :
https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss>
More help : https://help.launchpad.net/ListHelp
------------------------------------------------------------------------
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
