On 10/10/21 10:19, Anil wrote:
Please reply to list also.
Ccing list.
For future reference do not include images for textual information. Copy
and paste the errors as text.
Response in line.
Thanks for the response.
1. I am facing with both (pgAdmin and in python). pgAdmin is throwing
this window.
image.png
2. Python is throwing below error very often, so I had to create a
pool object again, which is slowing down my application 45 times.
*OperationalError: server closed the connection unexpectedly
*
*This probably means the server terminated abnormally
before or while processing the request.*
3. I don't see anything in log (from pgAdmin).
image.png
I tried to use the connection pool but it was still the same. Could
you help?
Per my response to Ron, the answer to this is going to be found on the
server side not the client side.
You need to look at the Postgres server log as well as the OS system log.
Thanks,
Anil
On Sun, Oct 10, 2021 at 1:56 AM Adrian Klaver
<adrian.klaver@xxxxxxxxxxx> wrote:
On 10/9/21 9:01 AM, Anil wrote:
> Hi Team,
>
> I am using Postgres (AWS instance, version: PostgreSQL 12.7 on
> x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.3 20140911 (Red Hat
> 4.8.3-9), 64-bit) with python for programming and pgAdmin for
querying.
> However facing below error very often but did not see any aborted
> information in log (in server activity, pdAdmin
dashboard). Tried to get
> support from open community but no luck so writing to you, could
you
> help me?
What does the actual Postgres log show?
When does the error occur, with the Python program, the pgAdmin query
or both?
>
> *OperationalError: server closed the connection unexpectedly
> *
> *This probably means the server terminated abnormally
> before or while processing the request.*
>
> Thanks,
> Anil
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
