Re: Client not able to pick up
| От | Rajesh Kumar |
|---|---|
| Тема | Re: Client not able to pick up |
| Дата | |
| Msg-id | CAJk5Atatgc=PwTcfD-JRumy9b_spWP7+yaVJ6j291SGaPQiR_Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Client not able to pick up (Scott Ribe <scott_ribe@elevated-dev.com>) |
| Ответы |
Re: Client not able to pick up
|
| Список | pgsql-admin |
Can this problem due to issues with HAproxy?
On Tue, 2 Jul 2024, 19:22 Scott Ribe, <scott_ribe@elevated-dev.com> wrote:
> 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.
В списке pgsql-admin по дате отправления: