In my current configuration all queries are sent to the master, i want write queries to be sent to master, and reads to slave. I have 1 pgpool setuped with 2 postgres servers in master/slave replication with slony1 Can this be done with 1 pgpool or i must use 2 pgpools for writes and reads.
here is the pgconfig # # pgpool-II configuration file sample # $Header: /cvsroot/pgpool/pgpool-II/pgpool.conf.sample,v 1.32 2010/01/31 02:22:24 t-ishii Exp $ # 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 = 32 # Number of connection pools allowed for a child process max_pool = 4 # 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' # pid file name pid_file_name = '/var/run/pgpool/pgpool.pid' # 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; DISCARD ALL' # for 8.2 or older this should be as follows. #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 = true # 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 = 10 # Health check user health_check_user = 'postgres' # 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 = 'echo host:%h, new master id:%m, old master id:%M port number:%p > /tmp/failover.log' # 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 = 'echo host:%h, new master id:%m, old master id:%M port number:%p > /tmp/failback.log' # If true, trigger fail over when writing to the backend communication # socket fails. This is the same behavior of pgpool-II 2.2.x or # earlier. If set to false, pgpool will report an error and disconnect # the session. fail_over_on_backend_error = true # If true, automatically locks a table with INSERT statements to keep # SERIAL data consistency. If the data does not have SERIAL data # type, no lock will be issued. An /*INSERT LOCK*/ comment has the # same effect. A /NO INSERT LOCK*/ comment disables the effect. insert_lock = true # 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, print all statements to the log. Similar to log_statement except # that prints DB node id and backend process id info. log_per_node_statement = true # 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 = 'localhost' # system DB info #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_hostname, backend_port, backend_weight # here are examples backend_hostname0 = 'localhost' backend_port0 = 5432 backend_weight0 = 1 backend_data_directory0 = '/usr/local/postgres-8.4/data/' backend_hostname1 = 'localhost' backend_port1 = 5434 backend_weight1 = 1 backend_data_directory1 = '/usr/local/postgres-8.4/data_replication/' # - 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 the recovering node's postmaster # start-up. 0 means no wait. # this is also used as a timer waiting for clients disconnected before # starting 2nd stage recovery_timeout = 90 # If client_idle_limit_in_recovery 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. This parameter only # takes effect in recovery 2nd stage. client_idle_limit_in_recovery = 0 # Specify table name to lock. This is used when rewriting lo_creat # command in replication mode. The table must exist and has writable # permission to public. If the table name is '', no rewriting occurs. lobj_lock_table = '' # If true, enable SSL support for both frontend and backend connections. # note that you must also set ssl_key and ssl_cert for SSL to work in # the frontend connections. ssl = false # path to the SSL private key file #ssl_key = './server.key' # path to the SSL public certificate file #ssl_cert = './server.cert' # If either ssl_ca_cert or ssl_ca_cert_dir is set, then certificate # verification will be performed to establish the authenticity of the # certificate. If neither is set to a nonempty string then no such # verification takes place. ssl_ca_cert should be a path to a single # PEM format file containing CA root certificate(s), whereas ssl_ca_cert_dir # should be a directory containing such files. These are analagous to the # -CAfile and -CApath options to openssl verify(1), respectively. #ssl_ca_cert = '' #ssl_ca_cert_dir = '' ----------------------------------------------------------------- Зрелищни снимки от ЮАР 2010. Вижте най-интересните моменти! http://sportni.bg/worldcup2010/?tid=20&oid=1002
