People tend to think that a SELECT-operation is always a read. This might look obvious and make sense but does it actually hold true?

CYBERTEC PostgreSQL

A SELECT operation might not always be a read-only action, which has significant implications for load balancing and replication strategies in databases. The application must be aware of whether it is performing read or write operations to correctly execute load balancing. Additionally, synchronous replication does not guarantee immediate visibility of data changes on replicas, highlighting the complexity in designing effective replication and load balancing solutions.

Why "SELECT * FROM table" is NOT a read

Load balancing: How to do it the wrong way

Send reads to the secondary and writes to the primary?

So in the end, it is a read operation, unless you trick it for it not to be a read operation.

Exactly what Alan said, A select statement is a read, Unless you do some funky logic that makes it not a read?

Sounds like this can be avoided with the simple “don’t write from views” philosophy.