[8.x] Explain eager/lazy load behavior when serializing models in a queued job (laravel#7653)

* Update queues.md

* Update queues.md

Co-authored-by: Taylor Otwell <[email protected]>

Author: driesvints

queues.md

@@ -221,7 +221,7 @@ If you would like to take total control over how the container injects dependenc
 > {note} Binary data, such as raw image contents, should be passed through the `base64_encode` function before being passed to a queued job. Otherwise, the job may not properly serialize to JSON when being placed on the queue.
 
 <a name="handling-relationships"></a>
-#### Handling Relationships
+#### Queued Relationships
 
 Because loaded relationships also get serialized, the serialized job string can sometimes become quite large. To prevent relations from being serialized, you can call the `withoutRelations` method on the model when setting a property value. This method will return an instance of the model without its loaded relationships:
 
@@ -236,6 +236,8 @@ Because loaded relationships also get serialized, the serialized job string can
         $this->podcast = $podcast->withoutRelations();
     }
 
+Furthermore, when a job is deserialized and model relationships are re-retrieved from the database, they will be retrieved in their entirety. Any previous relationship constraints that were applied before the model was serialized during the job queueing process will not be applied when the job is deserialized. Therefore, if you wish to work with a subset of a given relationship, you should re-constrain that relationship within your queued job.
+
 <a name="unique-jobs"></a>
 ### Unique Jobs