How long a WritablePolicy::Prefer pool keeps rejecting read-only connections before
falling back, once no writable connection has succeeded since the last one (or since
startup).
True when setting (a Postgres transaction_read_only value, as read by SHOW transaction_read_only) marks the session as read-only. Anything other than "on" counts as
writable: this matches libpq’s target_session_attrs=read-write on pre-14 servers, and an
unexpected value shouldn’t take the service down.
Finds a sqlx::Error carrying SQLSTATE 25006 (cannot execute ... in a read-only transaction) anywhere in err’s chain – the error a write raises when its connection turned
read-only mid-query, after already passing this crate’s connect/acquire checks (e.g. an
instance demoted between before_acquire and the query, or a WritablePolicy::Prefer pool
that fell back to a replica on purpose).