[MDEV-15963] mysql.transaction_registry is not documented in KB Created: 2018-04-21  Updated: 2018-04-26  Resolved: 2018-04-26

Status: Closed
Project: MariaDB Server
Component/s: Documentation, Versioned Tables
Affects Version/s: 10.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Ian Gilfillan
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-16024 transaction_registry.begin_timestamp ... Closed

 Description   

mysql.transaction_registry table exists and is used for transaction-precise versioning, but can't be found anywhere in the KB by search. Please document it, specifically the difference between transaction_id and commit_id, and between begin_timestamp and commit_timestamp – they seem to be not as obvious as they sound.

begin_timestamp name appears misleading. In the context of transactions, one would expect that it's time when the transaction was started (implicitly or explicitly via BEGIN / START TRANSACTION), but experimentation shows it's not so. My best guess is that begin_timestamp is when execution of COMMIT started, and commit_timestamp is when execution of COMMIT finished. If this is indeed meant to be so, the naming is quite unfortunate.



 Comments   
Comment by Aleksey Midenkov [ 2018-04-25 ]

BEGIN_TIMESTAMP is the timestamp of transaction begin (i.e. BEGIN statement). This is the subject of MDEV-16024.

Generated at Thu Feb 08 08:25:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.