Re: Connections - Postgres 9.2

From: Lucas Possamai <drum(dot)lucas(at)gmail(dot)com>
To: Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Connections - Postgres 9.2
Date: 2016-05-23 21:34:23
Message-ID: CAE_gQfVKMcwgrWXG-jkgr=jUT6o_uNeH6YW_rCxeW5sL_jKBCg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 17 May 2016 at 22:24, Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com>
wrote:

> Hi
>
> I control this way
>
> if "state_change" is from longtime and "state" is idle then I use
>
> function:
> *pg_terminate_backend ( integer ) * ==> return TRUE if
> killed-successful else FALSE
>
> example:
> # select pg_terminate_backend ( pid ) from pg_stat_activity where
> state='idle' and state_change < (current_timestamp - interval '1 hour');
>
> may be helpful
>
> NOTE: we come to decision to kill sessions in idle state more then "1
> hour" after lot of discussion with application / implementation /
> stake-holders team
>
> *removed history as thrown error due to mail length
>
>
> Thanks
> Sridhar
> OpenText
>
>
>
Hi Sridhar!

Thanks for your help...

I also control the same way.. But was wondering if a pooler would bring me
performance improvements...

cheers

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Lucas Possamai 2016-05-23 21:37:43 Re: index on ILIKE/LIKE - PostgreSQL 9.2
Previous Message Lucas Possamai 2016-05-23 21:32:29 Re: Increased I/O / Writes