Re: Client not able to pick up

How are you using HAProxy??? PostgreSQL can only have one master taking writes. So if you're sending write transactions to HAProxy to split among master & replicas, then yeah, there's your problem.

--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
https://www.linkedin.com/in/scottribe/

> On Jul 3, 2024, at 11:27 AM, Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> wrote:
>
> Can this problem due to issues with HAproxy?
>
> On Tue, 2 Jul 2024, 19:22 Scott Ribe, <scott_ribe(at)elevated-dev(dot)com> wrote:
> > On Jul 2, 2024, at 7:25 AM, Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> wrote:
> >
> > Let's ignore pgbouncer. I am getting the same error for client who are connected directly
>
> Principle is the same, something is setting the read only state.
>
> - Either the database is read only, as for a hot standby for instance;
> - Or the user is set to default to read only;
> - Or the client is setting read only and not subsequently setting read write.
>
> Ignoring pg bouncer just means excluding the possibility that the read only state was set by some client other than the one reporting the error.