A computer-implemented method, comprising: determining that a source table of a database instance requires transaction-consistent change capture within a replication log table storing a change history of transactions for the source table; detecting a first database change operation of a first transaction of the transactions, the first database change operation writing first record data to the source table using a record buffer that temporarily stores the first record data during the first database change operation; extracting the first record data from the record buffer; generating, using the extracted first record data, a first replication log entry that includes first metadata characterizing the first record data, including a corresponding first transaction commit identifier, CID, for the first transaction; storing the first replication log entry within the replication log table; and providing the first replication log entry to a subscriber to the replication log table for the source table, and based on a relational query specifying the first replication log table, wherein the CID for each transaction of the transactions is determined at a time of transaction commit of the respective each transaction, wherein the method further comprises: creating, for each respective transaction of the transactions, an object for the respective transaction configured to store the CID value of the respective transaction and to link to each respective record data for the respective transaction; and linking each respective record data in the source table to the respective transaction object for the respective transaction, wherein before the respective transaction commits, the CID in the object for the respective transaction is set as null, wherein, when the CID value of the respective transaction is determined, the CID value of the respective transaction is written to the object for the respective transaction in an atomic way, and wherein the CID value of the respective transaction is copied back asynchronously in a background process from the object for the respective transaction to each respective record data for the respective transaction. determining that a source table of a database instance requires transaction-consistent change capture within a replication log table storing a change history of transactions for the source table; detecting a first database change operation of a first transaction of the transactions, the first database change operation writing first record data to the source table using a record buffer that temporarily stores the first record data during the first database change operation; extracting the first record data from the record buffer; generating, using the extracted first record data, a first replication log entry that includes first metadata characterizing the first record data, including a corresponding first transaction commit identifier, CID, for the first transaction; storing the first replication log entry within the replication log table; and providing the first replication log entry to a subscriber to the replication log table for the source table, and based on a relational query specifying the first replication log table, wherein the CID for each transaction of the transactions is determined at a time of transaction commit of the respective each transaction, wherein the method further comprises: creating, for each respective transaction of the transactions, an object for the respective transaction configured to store the CID value of the respective transaction and to link to each respective record data for the respective transaction; and linking each respective record data in the source table to the respective transaction object for the respective transaction, wherein before the respective transaction commits, the CID in the object for the respective transaction is set as null, wherein, when the CID value of the respective transaction is determined, the CID value of the respective transaction is written to the object for the respective transaction in an atomic way, and wherein the CID value of the respective transaction is copied back asynchronously in a background process from the object for the respective transaction to each respective record data for the respective transaction. creating, for each respective transaction of the transactions, an object for the respective transaction configured to store the CID value of the respective transaction and to link to each respective record data for the respective transaction; and linking each respective record data in the source table to the respective transaction object for the respective transaction, wherein before the respective transaction commits, the CID in the object for the respective transaction is set as null, wherein, when the CID value of the respective transaction is determined, the CID value of the respective transaction is written to the object for the respective transaction in an atomic way, and wherein the CID value of the respective transaction is copied back asynchronously in a background process from the object for the respective transaction to each respective record data for the respective transaction.