Does --sink support multi-host connection strings with target_session_attrs=read-write?

[Timz2009]

Hello,

We are considering using a Patroni cluster as the storage backend for pgwatch metrics (the --sink database). Our goal is to ensure high availability so that if the current primary node fails, pgwatch can automatically start writing metrics to the new primary without manual intervention.

In standard PostgreSQL clients (libpq), this can be achieved using a multi-host connection string with the target_session_attrs=read-write parameter, for example:
postgresql://pgwatch:password@host1:5432,host2:5432,host3:5432/pgwatch_metrics?target_session_attrs=read-write

We have searched the documentation but could not find a clear statement on whether the --sink parameter supports this syntax.

Our questions are:

1. Does --sink support multi-host connection strings with target_session_attrs=read-write?
2. If not, what would be the recommended way to configure pgwatch to write metrics to a Patroni cluster with automatic failover?
3. Are there any known limitations or caveats we should be aware of when using a Patroni cluster as the metrics storage backend?

For context, we are using pgwatch version 5.2.0 and our --sink is currently configured as a single host:
postgres://pgwatch@127.0.0.1:5432/pgwatch_metrics

Thank you for your time and guidance!

[pashagolub]

Hello.

Yes, pgwatch connection strings support all parameters.