Lazy propagate etags to all users except current one

[PVince81]

This PR #14764 introduces lazy etag propagation.
But in some cases it still updates the etag of other users who are not the current one (ex: owner).

To reduce the number of cache updates, we should make sure that the etag propagation is only done for the currently logged in user (the one who performed an action), and lazily do it for other users.

This came to mind after getting feedback from @butonic regarding excessive PostgreSQL cache updates.

@icewind1991

[PVince81]

There is a test plan here: #14764 (comment)
If you monitor the DB changes, you can notice that in some cases the etag is changed directly (non-lazily) for more than a user.

[guruz]

Sounds smart!

[PVince81]

@icewind1991 I guess this is obsolete thanks to the new "storage-only etag propagation" + "compute etag of all mounted storages" logic ?

[icewind1991]

Yes

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.