Re: calling store procedure / insert statement never complete

From: Ninad Shah <nshah(dot)postgres(at)gmail(dot)com>
To: Trang Le <trang(dot)le(at)evizi(dot)com>
Cc: Mladen Gogala <gogala(dot)mladen(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: calling store procedure / insert statement never complete
Date: 2021-09-02 14:49:46
Message-ID: CAOFEiBf=zL+FoVVRkViVvswAyE=D-QkP9agih=-ukNiW9Kb8Cg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Kindly consider checking tcp_keepalive in PostgreSQL as well as OS kernel.
By default, it is 2 hours(7200).

Regards,
Ninad Shah

On Thu, 2 Sept 2021 at 11:43, Trang Le <trang(dot)le(at)evizi(dot)com> wrote:

> Hi Mladen,
>
> I missed previous emails, so I am creating a new one.
>
> I think the problem is coming from front-end side. when I run store
> procedure, job in pg_locks is done, data is inserted, log table shows that
> job completed with number of insert. However, store procedure in front-end
> side is still show running until the sever closed connection. The same
> problem when I run the query statement only, insert about 190k rows, when
> check target table, data is insert, but in the front-end side is still show
> wait until server close connection.
>
> I use pgamin4 5.3.
>
> Error: Server closed the connection unexpectedly. This probably means the
> server terminated abnormally before or while processing the request.
>
> Could you please double check?
>
> Thanks and regards,
> Trang
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ninad Shah 2021-09-02 14:59:38 Re: memory consumption of memory for postgres db container
Previous Message Ninad Shah 2021-09-02 14:47:17 Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds