RCORE-2152 Don't emit transaction log instructions for mutations on newly-created objects #7734

Nothing observes this table for notifications, so we don't need CT history. This is a pretty minor optimization unless we get a very large number of very small changests from the server.

…nger exists

…d objects The non-sync transaction logs are only used to drive notifications and notifications don't care about mutations on objects in the same commit as the objects were created it, so we don't need to emit the instructions at all. This significantly cuts the size of the transaction log for commits which are primarily inserting objects. This does a very basic check for "newly-created" which tracks the most recently created object for each table and skips mutation instructions for that object. This handles recursively creating an object and all of its embedded objects without the overhead of tracking every single object created within a transaction, and insertion workflows will typically not return to an object after creating another object in the same table. This requires adding an additional small amount of tracking for embedded objects, as Replication previously didn't know when new embedded objects were created.

These were used for converting to the file format where ObjKeys were derived from primary keys.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

RCORE-2152 Don't emit transaction log instructions for mutations on newly-created objects #7734

RCORE-2152 Don't emit transaction log instructions for mutations on newly-created objects #7734

Commits on Jun 4, 2024