From: | Benjamin Acquaye <benjaminacquaye2(at)gmail(dot)com> |
---|---|
To: | M Sarwar <sarwarmd02(at)outlook(dot)com> |
Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: |
Date: | 2023-10-05 20:55:34 |
Message-ID: | CAEDPGRKs+n9E+Ykc0KAkEvUGt7dOugo9QPiovBdpagB1jNzuZA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ok, thanks for the reply.
On Thu, Oct 5, 2023 at 2:48 PM M Sarwar <sarwarmd02(at)outlook(dot)com> wrote:
> That sounds like a database based timeout.
> I do not have more information on this at this time.
> Thanks,
> Sarwar
>
> ------------------------------
> *From:* Benjamin Acquaye <benjaminacquaye2(at)gmail(dot)com>
> *Sent:* Thursday, October 5, 2023 1:48 PM
> *To:* pgsql-admin(at)lists(dot)postgresql(dot)org <pgsql-admin(at)lists(dot)postgresql(dot)org>
> *Subject:*
>
> I have 8 client using the same connection. However, only one client facing
> this issue on postgresql15.
>
> Can someone help
>
> [image: image.png]
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pablo Delgado | 2023-10-07 21:54:15 | Error "public.powa_take_snapshot()" in PostgreSQL |
Previous Message | Nikhil Ingale | 2023-10-05 19:12:03 | BDR |