Re: Per thread Connection memory - Mailing list pgsql-admin

From Thorsten Schöning
Subject Re: Per thread Connection memory
Date
Msg-id 1690525.20160127153353@am-soft.de
Whole thread Raw
In response to Re: Per thread Connection memory  (Ankur Kaushik <ankurkaushik@gmail.com>)
Responses Re: Per thread Connection memory  (Ankur Kaushik <ankurkaushik@gmail.com>)
List pgsql-admin
Guten Tag Ankur Kaushik,
am Mittwoch, 27. Januar 2016 um 12:09 schrieben Sie:

> Application Using Java Program , They have there java Pool system ,
> when this Java pool memory full , tomcat need to restart in every 30- 60 min

So why do you think your problem is with Postgres? Client side
connections out of Java are not influenced by server side Postgres
configuration and Tomcat and Postgres don't share any memory.

Sounds like you should provide the exact error message you get.

> Please Let me know in Postgresql  pgbouncer  is essential use for
> handling multithread applications ?

No and you already successfully use your setup, else you wouldn't run
into problems, your only problem is with available resources and how
to balance them. But first you need to know where exactly your
bottleneck is and it sounds more like Java/Tomcat to me.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning       E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow



pgsql-admin by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: Insert in table with UNIQUE index
Next
From: Samed YILDIRIM
Date:
Subject: Re: Insert in table with UNIQUE index