Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ggRE5-0005pc-Gi for pgsql-admin@arkaria.postgresql.org; Mon, 07 Jan 2019 09:29:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ggRE3-0007EP-QQ for pgsql-admin@arkaria.postgresql.org; Mon, 07 Jan 2019 09:29:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ggOzm-00005E-Ok for pgsql-admin@lists.postgresql.org; Mon, 07 Jan 2019 07:06:46 +0000 Received: from mail-pl1-x62c.google.com ([2607:f8b0:4864:20::62c]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ggOzk-0004xu-2g for pgsql-admin@lists.postgresql.org; Mon, 07 Jan 2019 07:06:46 +0000 Received: by mail-pl1-x62c.google.com with SMTP id u6so20432308plm.8 for ; Sun, 06 Jan 2019 23:06:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0r4DOdF5nzdFSoL6DxonkJQn2xr7hJ8tSOxnWmMLGhk=; b=bATvbFvCQzz+1dxmexKM1B9cd8d5XUCSSJLqCxR1ucv+fs0QoQ5kYfS6fzssv3NUH/ pYyvv8z+Iv1G90queNlNa7rGGU26Eqgqq7ApTUtunQ8lePxrMtVOdm8l4ndCmnCeX6s5 K8gcftKds/gGyHutF3qlQ5iiAvwLqEKBhxOGKT3Lmxtub/3LP29q4GftXho1tYEuOsNK BEp0KcleJu6jC2n5GioejHTH0/MF2j1kJGmgV38SWijL0CxVI6ckY+XaRwmPAv6fQuk4 CtMeD6OPuAUmLunSuk9l/uLLCKbWCiss2i+JersMPryoICEBV9pcyVPK458jyZvNpRjA J5dA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0r4DOdF5nzdFSoL6DxonkJQn2xr7hJ8tSOxnWmMLGhk=; b=VaTFoXERq/emrOdpEgVg4xc/oBfU4+gmF/SJ1p5nFMX1UCnLf49dv5w/k+mjhqoKH6 ygQX9fYiCPt9JZowBG1josBOvpdLMyWQ9YGf1YVHqBnP/h1S+w+O0XKTyOdAX3xkeKgV BrChgRAApJCKjIEdRPZtci2ejO/oDyi9cfDTNYfdkxiESAs1KquBwXv+bh9d8SXrTZIA ucuowg7y9FMVh7rOiN2n/vN1gSDdtlRdvC+8ruoIbw/kYbNjsehZaLJVngUN7X/cHMgy oAhJG6ehB0plzrIu0LSt2eLzFFVFdB0HtrRVYOC//AKj/d9UWrI6ZSjfle0BH9sVy5Jh OMRA== X-Gm-Message-State: AJcUukfQnQaNwBrshzTiyQJqszziz9ba+2Hz9qekGvdf0Ja0OrRfSEBm YFGuTnILFsIW5RoyRoMQTeAV9jc2 X-Google-Smtp-Source: ALg8bN6oP0MekwUAkkSQdfp/AXVl1rI4pl+sCj9XwUy/Y934WPMQe0lqo6ULMDVwe1AfYQI+Us9t4Q== X-Received: by 2002:a17:902:9f89:: with SMTP id g9mr60812369plq.214.1546844801525; Sun, 06 Jan 2019 23:06:41 -0800 (PST) Received: from [192.168.10.53] ([1.129.131.215]) by smtp.gmail.com with ESMTPSA id c72sm115590606pfb.107.2019.01.06.23.06.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 06 Jan 2019 23:06:41 -0800 (PST) Content-Type: multipart/alternative; boundary=Apple-Mail-141C87E9-DB7A-4E5C-B748-B579DD6508DF Mime-Version: 1.0 (1.0) Subject: Re: Database connection pool expiration From: Calvin Kim X-Mailer: iPhone Mail (16C101) In-Reply-To: Date: Mon, 7 Jan 2019 18:06:31 +1100 Cc: pgsql-admin@lists.postgresql.org Content-Transfer-Encoding: 7bit Message-Id: <80E28CE6-DCE0-4E66-8B50-EFF65923E7DD@gmail.com> References: To: Shreeyansh Dba List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Apple-Mail-141C87E9-DB7A-4E5C-B748-B579DD6508DF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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 wrote= : >=20 > There may be several performance factors which might be causing the DB con= nection expired before completing long running transactions. However, you ca= n consider tweaking statement_timeout and idle_in_transaction_session_timeou= t parameter. >=20 > Thanks & Regards, > Shreeyansh DBA Team > www.shreeyansh.com >=20 >=20 >> On Mon, Jan 7, 2019 at 9:32 AM Kuk Hyun Kim wrote: >> Hi, >>=20 >> Recently, developers are saying that the DB connection is getting >> expired causing issue while running long transactions. >>=20 >> Is there a such configuration setting in Postgres and what would be >> the default and recommended value for this? >>=20 >> Regards, >> Calvin >>=20 --Apple-Mail-141C87E9-DB7A-4E5C-B748-B579DD6508DF Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi,

I have checked both a= nd they were all commented out, so they were disabled.

<= div>Could there be some other db config to check for?

Thanks.
Calvin

Sent from my iPhone

On 7 Jan 2019, at 6:0= 1 pm, Shreeyansh Dba <shreeya= nsh2014@gmail.com> wrote:

There may be several performance factors which mig= ht be causing the DB connection expired before completing long running trans= actions. However, you can consider tweaking statement_timeout and idle_in_tr= ansaction_session_timeout parameter.

<= div dir=3D"ltr">
Thanks & Reg= ards,
Shreeyansh DBA Team
www.shreeyansh.com


On Mon, Jan 7, 2019 at 9:32 AM Kuk Hyun Kim <khk800123@gmail.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

= --Apple-Mail-141C87E9-DB7A-4E5C-B748-B579DD6508DF--