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: 
 <CAJk5AtbJMX3ZzH-FH6G97PpRe9Eq5fimaMxTXR4B=mxWZiuttQ@mail.gmail.com>
Date: Tue, 2 Jul 2024 07:51:49 -0600
Cc: pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B3F3D22-6435-4D1E-B45A-4C6FB7CDC00C@elevated-dev.com>
References: 
 <CAJk5AtY89NpL=syZTS9vSwndLF9Si2swLyZ0n6EdP08Opy76_Q@mail.gmail.com>
 <177F52B5-FCD8-4EAC-9277-52674A5952F9@elevated-dev.com>
 <CAJk5AtbJMX3ZzH-FH6G97PpRe9Eq5fimaMxTXR4B=mxWZiuttQ@mail.gmail.com>
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/2B3F3D22-6435-4D1E-B45A-4C6FB7CDC00C%40elevated-dev.com>
Precedence: bulk

> 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

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.=