When do race conditions actually occur?

Based on the information provided in the README:

> ❗️ This package is experimental. Generally it should work well, you might run into race conditions when your Client Component is still rendering in SSR, and already making overlapping queries on the browser.
> ...
> If you do not use suspense in your application, this will not be a problem to you.

When would such a scenario with race conditions happen exactly? Only when using `@defer`? Also, what do you mean if we're not using suspense? What will happen if I decide to wrap a component using a suspense boundary `` or by using the `loading.tsx` provided by the new Next.js app directory?

What problems might occur?

Start with the README sections describing SSR, overlapping queries, race conditions, suspense, and @defer. Compare those claims with the Next.js App Router behavior for Client Components, , and loading.tsx. Done means documenting when the scenario occurs, whether @defer is required, and what problems users can expect.

Written by the indexing model from the issue text.