Write-heavy operations like COPY will use a non-default `buffer access strategy` which intentionally causes the write-heavy process to write its own buffers.

This is so that, if you write a billion rows into a table, that table growth doesn't shove the entire rest of the database out of the cache.

Is your question just based on curiosity, or do you think the current behavior is causing a problem?