Open steve-chavez opened 2 months ago
Edit: fixed the issue
Wait, this is wrong. We actually set target_session_attrs=read-write
internally.
It's the db-uri
on the docs the one that's set to read-only
: https://postgrest.org/en/v12/references/listener.html#listener-on-read-replicas
I'll fix this by putting warning on the docs.
Problem
The docs instruct to add
target_session_attrs=read-only
to thedb-uri
, but this will fail on an instance with libpq < 14:(uses the ubuntu-aarch64 release)
This happens because
target_session_attrs
only acceptsread-only
starting from libpq 14.target_session_attrs
only supports read-write on libpq13, see https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-TARGET-SESSION-ATTRS.Solution
Warn about this limitation on the docs.