Re: limit connections pgpool - Mailing list pgsql-performance

From Tatsuo Ishii
Subject Re: limit connections pgpool
Date
Msg-id 20131011.123840.1613479503494305756.t-ishii@sraoss.co.jp
Whole thread Raw
In response to limit connections pgpool  (Jeison Bedoya Delgado <jeisonb@audifarma.com.co>)
List pgsql-performance
> Hi, i want to know what is the pgpool parameter for close the
> connections directly in the database, because the pgpool II close fine
> the the childs with the life time, but the connection in the database
> continue open in idle state.

That's the result of connection cache functionality of pgpool-II. If
you don't need the connection cache of pgpool-II at all, you could
turn it off:

connection_cache = off

Or you could set following to non 0.

connection_life_time

After an idle connection to PostgreSQL backend lasts for
connection_life_time seconds, the connection will be turned off.

If you have further questions, you'd better to subscribe and post the
question:

http://www.pgpool.net/mailman/listinfo/pgpool-general
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> this is my pool config
>
> num_init_children = 100
> max_pool = 8
> child_life_time = 60
> child_max_connections = 0
> connection_life_time = 0
> client_idle_limit = 60
>
>
> and this is my postgresql.conf
>
> max_connections = 800
> shared_buffers =  2048MB
> temp_buffers =  64MB
> work_mem = 2048MB
> maintenance_work_mem = 2048MB
> wal_buffers = 256
> checkpoint_segments = 103
>
>
> thanks
>
>
> --
> Sent via pgsql-performance mailing list
> (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance


pgsql-performance by date:

Previous
From: Michael Paquier
Date:
Subject: Re: limit connections pgpool
Next
From: Tony Kay
Date:
Subject: CPU spikes and transactions