[Pgpool-general] new connections are not accepted

Martin Badie martinbadie at yahoo.com
Fri Jun 5 06:27:07 UTC 2009


Hi,
Yes my application uses persistent connections.How can I found out how many 
connections are used in a certain time and how can I detect  maximum 
simultaneous connections from pgpool.conf so I can tweak my application 
for that maximum connection number.

I haven't found a documentation for that so I am asking here.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Badie a écrit :
> Hi,
>
> I have an application that I want to have more performance. For about 10
> minutes it works perfect but after certain amount of time I get no
> connection and when I try to login using 9999 port I can't connect
> (using psql -U pgsql -h  127.0.0.1 -p 9999). But I can connect to 5432
> without any problem. Here is my configuration file. Can someone guide me
> about what I am doing wrong here?
>

Hi,

Do you use persistent connections within your application?

>(...)

Regards,
- --
Stéphane Schildknecht
PostgreSQLFr - http://www.postgresql.fr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKJ98FA+REPKWGI0ERAnbcAKDhoXF8004DXJwe4gqGRIuEu3ZaqACeJC1j
6Qnfn9ghScY/YcK5Gy5RcrQ=
=vM5L
-----END PGP SIGNATURE-----




________________________________
From: Martin Badie <martinbadie at yahoo.com>
To: pgpool-general at pgfoundry.org
Sent: Thursday, June 4, 2009 5:44:26 PM
Subject: new connections are not accepted


Hi,

I have an application that I want to have more performance. For about 10 minutes it works perfect but after certain amount of time I get no connection and when I try to login using 9999 port I can't connect (using psql -U pgsql -h  127.0.0.1 -p 9999). But I can connect to 5432 without any problem. Here is my configuration file. Can someone guide me about what I am doing wrong here?


#
# pgpool-II configuration file sample


# Host name or IP address to listen on: '*' for all, '' for no TCP/IP
# connections
listen_addresses = 'localhost'

# Port number for pgpool
port = 9999

# Port number for pgpool communication manager
pcp_port = 9898

# Unix domain socket path.  (The Debian package defaults to
# /var/run/postgresql.)
socket_dir = '/tmp'

# Unix domain socket path for pgpool communication manager.
# (Debian package defaults to /var/run/postgresql)
pcp_socket_dir = '/tmp'

# Unix domain socket path for the backend. Debian package defaults to /var/run/postgresql!
backend_socket_dir = '/tmp'

# pgpool communication manager timeout. 0 means no timeout, but strongly not recommended!
pcp_timeout = 10

# number of pre-forked child process
num_init_children = 40

# Number of connection pools allowed for a child process
max_pool = 32

# If idle for this many seconds, child exits.  0 means no timeout.
child_life_time = 300

# If idle for this many seconds, connection to PostgreSQL closes.
# 0 means no timeout.
connection_life_time = 0

# If child_max_connections connections were received, child exits.
# 0 means no exit.
child_max_connections = 0

# If client_idle_limit is n (n > 0), the client is forced to be
# disconnected whenever after n seconds idle (even inside an explicit
# transactions!)
# 0 means no disconnect.
client_idle_limit = 0

# Maximum time in seconds to complete client authentication.
# 0 means no timeout.
authentication_timeout = 60

# Logging directory
logdir = '/tmp'

# Replication mode
replication_mode = false

# Load balancing mode, i.e., all SELECTs are load balanced.
# This is ignored if replication_mode is false..
load_balance_mode = false

# if there's a data mismatch between master and secondary
# start degeneration to stop replication mode
replication_stop_on_mismatch = false

# If true, replicate SELECT statement when load balancing is disabled.
# If false, it is only sent to the master node.
replicate_select = false

# Semicolon separated list of queries to be issued at the end of a session
reset_query_list = 'ABORT; RESET ALL; SET SESSION AUTHORIZATION DEFAULT'

# If true print timestamp on each log line.
print_timestamp = true

# If true, operate in master/slave mode.
master_slave_mode = false

# If true, cache connection pool.
connection_cache = true

# Health check timeout.  0 means no timeout.
health_check_timeout = 20

# Health check period.  0 means no health check.
health_check_period = 0

# Health check user
health_check_user = 'nobody'

# Execute command by failover.
# special values:  %d = node id
#                  %h = host name
#                  %p = port number
#                  %D = database cluster path
#                  %m = new master node id
#                  %M = old master node id
#                  %% = '%' character
#
failover_command = ''

# Execute command by failback.
# special values:  %d = node id
#                  %h = host name
#                  %p = port number
#                  %D = database cluster path
#                  %m = new master node id
#                  %M = old master node id
#                  %% = '%' character
#
failback_command = ''

# If true, automatically lock table with INSERT statements to keep SERIAL
# data consistency.  An /*INSERT LOCK*/ comment has the same effect.  A
# /NO INSERT LOCK*/ comment disables the effect.
insert_lock = false

# If true, ignore leading white spaces of each query while pgpool judges
# whether the query is a SELECT so that it can be load balanced.  This
# is useful for certain APIs such as DBI/DBD which is known to adding an
# extra leading white space.
ignore_leading_white_space = true

# If true, print all statements to the log.  Like the log_statement option
# to PostgreSQL, this allows for observing queries without engaging in full
# debugging.
log_statement = false

# If true, incoming connections will be printed to the log.
log_connections = false

# If true, hostname will be shown in ps status. Also shown in
# connection log if log_connections = true.
# Be warned that this feature will add overhead to look up hostname.
log_hostname = false

# if non 0, run in parallel query mode
parallel_mode = false

# if non 0, use query cache
enable_query_cache = false

#set pgpool2 hostname 
pgpool2_hostname = ''

# system DB info
system_db_hostname = '127.0.0.1'
system_db_port = 5432
system_db_dbname = 'pgpool'   
system_db_schema = 'pgpool_catalog'
system_db_user = 'pgpool'        
system_db_password = ''   

# backend_hostname, backend_port, backend_weight
# here are examples
#backend_hostname0 = 'host1'
#backend_port0 = 5432
#backend_weight0 = 1
#backend_data_directory0 = '/data'
#backend_hostname1 = 'host2'
#backend_port1 = 5433
#backend_weight1 = 1
#backend_data_directory1 = '/data1'


# backend_hostname, backend_port, backend_weight
# here are examples                
backend_hostname0 = '127.0.0.1'              
backend_port0 = 5432
backend_weight0 = 1
backend_data_directory0 = '/db/pgsql/data'


# - HBA -

# If true, use pool_hba.conf for client authentication. In pgpool-II
# 1.1, the default value is false. The default value will be true in
# 1.2.
enable_pool_hba = false

# - online recovery -
# online recovery user
recovery_user = 'nobody'

# online recovery password
recovery_password = ''

# execute a command in first stage.
recovery_1st_stage_command = ''

# execute a command in second stage.
recovery_2nd_stage_command = ''

# maximum time in seconds to wait for remote start-up. 0 means no wait
recovery_timeout = 90


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pgfoundry.org/pipermail/pgpool-general/attachments/20090604/1a4c8f4f/attachment-0001.html>


More information about the Pgpool-general mailing list