docs: suggest target_session_attrs=read-write
when using HA and psql
#126
Labels
target_session_attrs=read-write
when using HA and psql
#126
===
However, a word of caution!
target_session_attrs=read-write
is absolutely critical. Without itlibpq
correctly switches to a second node, but has a chance to end up on a read-only replica. When I tested this, the constant write attempts eventually took downrepmgr
and even the entire PSQL container.I'm not sure how the databroker works under the hood; perhaps on large installs it can make use of read-only replicas for load balancing? However, attempting to write on a read-only connection makes no sense to me. Arguably this behavior should be changed, or at the least the docs can be clarified in the docs to stress using
target_session_attrs=read-write
when using HA.Originally posted by @alexrudd2 in pomerium/pomerium#3634 (comment)
The text was updated successfully, but these errors were encountered: