If a batch apex is called with size say 200 (default size). And we have a DML operation (say update) in execute method of the batch. So the trigger which is set to run before/after update will share the same governor limit used in a batch (for a chunk)?
Each chunk of the batch on execute method runs and updates 200 records (what no. of times is really depends on the record QueryLocator returns).
Then, would after update trigger set for the object only be able to update 9800 record? Since, Salesforce only allow to perform DML up-to 10000 record/transaction and here 200 has been already consumed by the batch for a chunk?
As per my test this is what it is going to happen but I didn't find any clear documentation regarding Trigger behavior after a batch runs, thus wanted to check if my understanding is correct.