Let's ignore pgbouncer. I am getting the same error for client who are connected directly
On Tue, 2 Jul 2024, 18:12 Scott Ribe, <scott_ribe@xxxxxxxxxxxxxxxx> wrote:
> On Jul 1, 2024, at 11:57 PM, Rajesh Kumar <rajeshkumar.dba09@xxxxxxxxx> wrote:
>
> 2. Why client is stucked with the message " cannot execute update in read only transaction" , eventhough master is up and running.
Because a client set a connection to read only, then later that pgbouncer -> server connection was assigned to a different client. You have to either:
- reset connections in pgbouncer when they are reassigned, which has its own downsides--see the docs
- fix the client so it doesn't leave connections in read only state
- have those clients connect directly to PG
