CQRS without event sourcing: a simpler approach?

We're exploring CQRS for a new service but want to avoid the full complexity of event sourcing, at least initially. Our thought is to have a traditional PostgreSQL database for writes, and then use something like Debezium for Change Data Capture (CDC) to stream changes into an Elasticsearch cluster for our read model. This gives us separate read/write models. Is this a valid implementation of CQRS without event sourcing? What are the potential pitfalls we should be aware of, especially around ensuring consistency between the write DB and the read store, and handling schema changes? I'm trying to understand if this simpler approach offers enough benefits of CQRS without inheriting the full operational overhead of an event store.