use-db

To query PostgreSQL across environments for debugging, you can use environment routing to target local, QA, UAT, or prod databases. This provides a unified connection workflow and reusable query templates to support data verification and investigation.

Verifying read-model consistency between QA and production databases requires cross-environment queries to inspect the event-store and compare data states. This approach supports checking subscription lag and validating data synchronization safely.

Yes, you can inspect event-store data in a local environment by routing your PostgreSQL queries specifically to local. This enables event inspection and allows you to debug subscription lag or verify data states locally before checking higher environments.

Safely querying production PostgreSQL databases during an investigation involves using a connection workflow that preserves safe access to production data. It provides reusable query templates to inspect events and read-models without risking data integrity.

Yes, this method provides reusable query templates and references specifically for investigating subscription lag in PostgreSQL. These templates help you quickly query event-stores and read-models to identify synchronization delays across environments.