Function ProcessBatchUpdate

pg_documentdb/src/commands/update.c:1609–1637

* ProcessBatchUpdate iterates over the updates array and executes each * update in a subtransaction, to allow us to continue after an error. * * If batchSpec->isOrdered is false, we continue with remaining tasks on * error. * * Using subtransactions is slightly different from Mongo, which effectively * does each update operation in a separate transaction, but it has roughly * the same over

 * the same overall UX.
 */
static void
ProcessBatchUpdate(MongoCollection *collection, BatchUpdateSpec *batchSpec,
				   text *transactionId, BatchUpdateResult *batchResult,
				   ExprEvalState *stateForSchemaValidation,
				   WriteMode writeMode)
{
	MemoryContext oldContext = MemoryContextSwitchTo(batchResult->resultMemoryContext);
	BuildUpdates(batchSpec);
	MemoryContextSwitchTo(oldContext);

	/* Check if we can inline the updates */
	if (transactionId == NULL && collection->shardKey == NULL)
	{
		/* Technically ShareLock is okay here since we use SPI internally for the updates
		 * However, if we end up building the AST directly, then easier to use RowExclusiveLock.
		 */
		batchSpec->shardTableOid = TryGetCollectionShardTable(collection,
															  RowExclusiveLock);
	}

	List *updates = batchSpec->updates;
	bool isOrdered = batchSpec->isOrdered;

	/* We are in sharded scenario so we need to go through the planner to do the writes and then call the worker. */
	bool forceInlineWrites = false;
	ProcessBatchUpdateCore(collection, updates, transactionId, batchResult, isOrdered,
						   forceInlineWrites, stateForSchemaValidation,
						   writeMode);
}


/*