On Thu, 2011-10-06 at 10:59 -0500, Matias Israel Malpica Escobar wrote:
> Hi everyone i´ve been trying to understand and configure pgpool for a pool of 
> connections (not sure if that is the term), i already follow a manual and 
> confiigure it like this:
> 
> listen_addresses = '*'
> port = 9999
> pcp_port = 9898
> socket_dir = '/var/run/postgresql'
> pcp_socket_dir = '/var/run/postgresql'
> backend_socket_dir = '/var/run/postgresql'
> pcp_timeout = 10
> num_init_children = 32
> max_pool = 4
> child_life_time = 300
> connection_life_time = 0
> child_max_connections = 0
> client_idle_limit = 0
> authentication_timeout = 60
> logdir = '/var/run/postgresql'
> replication_mode = false
> load_balance_mode = false
> replication_stop_on_mismatch = false
> replicate_select = false
> reset_query_list = 'ABORT; RESET ALL; SET SESSION AUTHORIZATION DEFAULT'
> print_timestamp = true
> master_slave_mode = false
> connection_cache = true
> health_check_timeout = 20
> health_check_period = 60
> health_check_user = 'pgpool2'
> failover_command = ''
> failback_command = ''
> insert_lock = false
> ignore_leading_white_space = true
> log_statement = false
> log_connections = false
> log_hostname = false
> parallel_mode = false
> enable_query_cache = false
> pgpool2_hostname = 'pgsql1'
> system_db_hostname = 'localhost'
> system_db_port = 5432
> system_db_dbname = 'pgpool'
> system_db_schema = 'pgpool_catalog'
> system_db_user = 'pgpool'
> system_db_password = ''
> backend_hostname0 = '192.168.0.3'
> backend_port0 = 5432
> backend_weight0 = 1
> backend_hostname1 = '192.168.0.4'
> backend_port1 = 5432
> backend_weight1 = 1
> enable_pool_hba = false
> recovery_user = 'pgpool2'
> recovery_password = ''
> recovery_1st_stage_command = ''
> recovery_2nd_stage_command = ''
> recovery_timeout = 90
> After this i startes pgpool and everything seems to be working, how do i 
> actually test it?
> 
> Now i have a couple of questions.
> 
> With this i understand that i am creating 4 pools for 32 connections each, so 
> it would be 128 connections?
> 

Yes, but only 32 active at one time.

> The purpose of this is, first allow pgpool to handle connections instead of 
> postygres so the end user do not receive an error, adn second use the same 
> connection to dispach several request that are alike...
> 

Obviously, if your user tries to connect to a database that doesn't
exist, he'll get an error message. If he tries to execute a badly
written query, he'll also get an error message.

pgpool will be able to reuse a connection if the user wants to connect
to the same database with the same user.


-- 
Guillaume
  http://blog.guillaume.lelarge.info
  http://www.dalibo.com

_______________________________________________
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general

Reply via email to