mirror of
https://github.com/mongodb/mongo.git
synced 2024-12-01 01:21:03 +01:00
7d687264de
Now that we execute multikey catalog updates in a side transaction, we need to give them some suitable timestamp. In normal replication, we can grab the latest value of the LogicalClock. In startup recovery, though, we may replay a prepared transaction that does a multikey write, but the LogicalClock may not have been initialized yet. Thus, we use the prepare timestamp of the transaction for the multikey write, since that timestamp is guaranteed to be less than or equal to the commit timestamp of the transaction. |
||
|---|---|---|
| .. | ||
| aggregation | ||
| auth | ||
| change_streams | ||
| client_encrypt | ||
| concurrency | ||
| core | ||
| core_standalone | ||
| decimal | ||
| disk | ||
| fail_point | ||
| free_mon | ||
| gle | ||
| hooks | ||
| httpinterface | ||
| libs | ||
| multiVersion | ||
| noPassthrough | ||
| noPassthroughWithMongod | ||
| parallel | ||
| perf | ||
| readonly | ||
| replsets | ||
| serial_run | ||
| sharding | ||
| slow1 | ||
| ssl | ||
| sslSpecial | ||
| tool | ||
| watchdog | ||