Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: Client not able to pick up
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <CAJk5Atatgc=PwTcfD-JRumy9b_spWP7+yaVJ6j291SGaPQiR_Q@mail.gmail.com>
Date: Wed, 3 Jul 2024 12:42:55 -0600
Cc: pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0FC6C4CA-FCCD-4C20-B177-477627D5123B@elevated-dev.com>
References: 
 <CAJk5AtY89NpL=syZTS9vSwndLF9Si2swLyZ0n6EdP08Opy76_Q@mail.gmail.com>
 <177F52B5-FCD8-4EAC-9277-52674A5952F9@elevated-dev.com>
 <CAJk5AtbJMX3ZzH-FH6G97PpRe9Eq5fimaMxTXR4B=mxWZiuttQ@mail.gmail.com>
 <2B3F3D22-6435-4D1E-B45A-4C6FB7CDC00C@elevated-dev.com>
 <CAJk5Atatgc=PwTcfD-JRumy9b_spWP7+yaVJ6j291SGaPQiR_Q@mail.gmail.com>
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/0FC6C4CA-FCCD-4C20-B177-477627D5123B%40elevated-dev.com>
Precedence: bulk

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@elevated-dev.com
https://www.linkedin.com/in/scottribe/


> On Jul 3, 2024, at 11:27=E2=80=AFAM, Rajesh Kumar =
<rajeshkumar.dba09@gmail.com> wrote:
>=20
> Can this problem due to issues with HAproxy?
>=20
> On Tue, 2 Jul 2024, 19:22 Scott Ribe, <scott_ribe@elevated-dev.com> =
wrote:
> > On Jul 2, 2024, at 7:25=E2=80=AFAM, Rajesh Kumar =
<rajeshkumar.dba09@gmail.com> wrote:
> >=20
> > Let's ignore pgbouncer. I am getting the same error for client who =
are connected directly
>=20
> Principle is the same, something is setting the read only state.
>=20
> - 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.
>=20
> 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.