From: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
---|---|
To: | scott_ribe(at)elevated-dev(dot)com |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Client not able to pick up |
Date: | 2024-07-02 13:25:40 |
Message-ID: | CAJk5AtbJMX3ZzH-FH6G97PpRe9Eq5fimaMxTXR4B=mxWZiuttQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)elevated-dev(dot)com> wrote:
> > On Jul 1, 2024, at 11:57 PM, Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com>
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2024-07-02 13:51:49 | Re: Client not able to pick up |
Previous Message | Scott Ribe | 2024-07-02 12:42:46 | Re: Client not able to pick up |