Thread: Database connection pool expiration

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

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@gmail.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@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

Upgrading from RHEL5 Postgres v.9.5 to RHEL7 v10.3 on VMs.

While the database objects have been created on the new VM I'm having issues getting the data moved over.  I've tried a data only pg dump and restore it fails.

Any ideas as to how to accomplish this

Thank you in advance for any assistance,

Denise