Im trying to understand this section of the ecto documentation:

https://hexdocs.pm/ecto/Ecto.Query.html#preload/3-preload-functions

For many_to_many - the function receives the IDs of the parent association and it must return a tuple with the parent id as the first element and the association map or struct as the second. For example, if a post has many tags, when preloading the tags with a custom function, the function will receive a list of "post_ids" as the argument and it must return a tuple in the format of {post_id, tag}

By experimentation I’ve figured out that parent here refers to the post itself. Which leads to my first question.

Why does Repo.preload(my_post, tags: &my_custom_preloader/1) call my custom preloader with an array containing the id of my_post? When would it ever get more Ids?

Now to the second source of my confusion: the function will receive a list of "post_ids" as the argument and it must return a tuple in the format of {post_id, tag}

How do I go about transforming many post ids to one post id and one tag if the result somehow is to represent a many-to-many relationship?