pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Client not able to pick up
Date: Tue, 2 Jul 2024 07:51:49 -0600
Message-ID: <2B3F3D22-6435-4D1E-B45A-4C6FB7CDC00C@elevated-dev.com> (raw)
In-Reply-To: <CAJk5AtbJMX3ZzH-FH6G97PpRe9Eq5fimaMxTXR4B=mxWZiuttQ@mail.gmail.com>
References: <CAJk5AtY89NpL=syZTS9vSwndLF9Si2swLyZ0n6EdP08Opy76_Q@mail.gmail.com>
	<177F52B5-FCD8-4EAC-9277-52674A5952F9@elevated-dev.com>
	<CAJk5AtbJMX3ZzH-FH6G97PpRe9Eq5fimaMxTXR4B=mxWZiuttQ@mail.gmail.com>

> On Jul 2, 2024, at 7:25 AM, Rajesh Kumar <rajeshkumar.dba09@gmail.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.

view thread (9+ messages)  latest in thread

Message-ID: <2B3F3D22-6435-4D1E-B45A-4C6FB7CDC00C@elevated-dev.com>
Permalink:  ../2B3F3D22-6435-4D1E-B45A-4C6FB7CDC00C@elevated-dev.com/
Also on:    postgresql.org/message-id/2B3F3D22-6435-4D1E-B45A-4C6FB7CDC00C@elevated-dev.com

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: scott_ribe@elevated-dev.com, rajeshkumar.dba09@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Client not able to pick up
  In-Reply-To: <2B3F3D22-6435-4D1E-B45A-4C6FB7CDC00C@elevated-dev.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox