Re: Database connection pool expiration

From: Calvin Kim <khk800123(at)gmail(dot)com>
To: Shreeyansh Dba <shreeyansh2014(at)gmail(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Database connection pool expiration
Date: 2019-01-07 07:06:31
Message-ID: 80E28CE6-DCE0-4E66-8B50-EFF65923E7DD@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi,

I have checked both and they were all commented out, so they were disabled.

Could there be some other db config to check for?

Thanks.
Calvin

Sent from my iPhone

> On 7 Jan 2019, at 6:01 pm, Shreeyansh Dba <shreeyansh2014(at)gmail(dot)com> wrote:
>
> There may be several performance factors which might be causing the DB connection expired before completing long running transactions. However, you can consider tweaking statement_timeout and idle_in_transaction_session_timeout parameter.
>
> Thanks & Regards,
> Shreeyansh DBA Team
> www.shreeyansh.com
>
>
>> On Mon, Jan 7, 2019 at 9:32 AM Kuk Hyun Kim <khk800123(at)gmail(dot)com> wrote:
>> Hi,
>>
>> Recently, developers are saying that the DB connection is getting
>> expired causing issue while running long transactions.
>>
>> Is there a such configuration setting in Postgres and what would be
>> the default and recommended value for this?
>>
>> Regards,
>> Calvin
>>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message vinod awasare 2019-01-07 09:04:19 postgres installation issue
Previous Message Shreeyansh Dba 2019-01-07 07:01:52 Re: Database connection pool expiration