Re: [Pgpool-general] Confusing... pgpool starts on both nodes, but don't replicate.

» Ruben Alves Mon, 06 Jul 2009 04:20:29 -0700

Hello Tatsuo,
I've just stop both of the postgresql services (docsys and docsys2), made a tar.gz of the data main directory send it (gziped) via scp to docssy2, start both services and pgtool.
Still not working... I really don't know why...

docsys:/opt/pgpool2/bin# ./pgpool -d -c -n
2009-07-06 11:15:02 DEBUG: pid 4714: key: listen_addresses
2009-07-06 11:15:02 DEBUG: pid 4714: value: '*' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: port
2009-07-06 11:15:02 DEBUG: pid 4714: value: 9999 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: pcp_port
2009-07-06 11:15:02 DEBUG: pid 4714: value: 9898 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: socket_dir
2009-07-06 11:15:02 DEBUG: pid 4714: value: '/tmp' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: pcp_socket_dir
2009-07-06 11:15:02 DEBUG: pid 4714: value: '/tmp' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: backend_socket_dir
2009-07-06 11:15:02 DEBUG: pid 4714: value: '/tmp' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: pcp_timeout
2009-07-06 11:15:02 DEBUG: pid 4714: value: 10 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: num_init_children
2009-07-06 11:15:02 DEBUG: pid 4714: value: 32 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: max_pool
2009-07-06 11:15:02 DEBUG: pid 4714: value: 4 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: child_life_time
2009-07-06 11:15:02 DEBUG: pid 4714: value: 300 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: connection_life_time
2009-07-06 11:15:02 DEBUG: pid 4714: value: 0 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: child_max_connections
2009-07-06 11:15:02 DEBUG: pid 4714: value: 0 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: client_idle_limit
2009-07-06 11:15:02 DEBUG: pid 4714: value: 0 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: authentication_timeout
2009-07-06 11:15:02 DEBUG: pid 4714: value: 60 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: logdir
2009-07-06 11:15:02 DEBUG: pid 4714: value: '/tmp' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: pid_file_name
2009-07-06 11:15:02 DEBUG: pid 4714: value: '/var/run/pgpool/pgpool.pid' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: replication_mode
2009-07-06 11:15:02 DEBUG: pid 4714: value: true kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: load_balance_mode
2009-07-06 11:15:02 DEBUG: pid 4714: value: true kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: replication_stop_on_mismatch
2009-07-06 11:15:02 DEBUG: pid 4714: value: false kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: replication_stop_on_mismatch: 0
2009-07-06 11:15:02 DEBUG: pid 4714: key: replicate_select
2009-07-06 11:15:02 DEBUG: pid 4714: value: true kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: replicate_select: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: reset_query_list
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'ABORT; DISCARD ALL' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: extract_string_tokens: token: ABORT
2009-07-06 11:15:02 DEBUG: pid 4714: extract_string_tokens: token: DISCARD ALL
2009-07-06 11:15:02 DEBUG: pid 4714: key: print_timestamp
2009-07-06 11:15:02 DEBUG: pid 4714: value: true kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: master_slave_mode
2009-07-06 11:15:02 DEBUG: pid 4714: value: false kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: connection_cache
2009-07-06 11:15:02 DEBUG: pid 4714: value: true kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: health_check_timeout
2009-07-06 11:15:02 DEBUG: pid 4714: value: 20 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: health_check_period
2009-07-06 11:15:02 DEBUG: pid 4714: value: 0 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: health_check_user
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'nobody' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: failover_command
2009-07-06 11:15:02 DEBUG: pid 4714: value: '' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: failback_command
2009-07-06 11:15:02 DEBUG: pid 4714: value: '' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: insert_lock
2009-07-06 11:15:02 DEBUG: pid 4714: value: true kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: ignore_leading_white_space
2009-07-06 11:15:02 DEBUG: pid 4714: value: true kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: log_statement
2009-07-06 11:15:02 DEBUG: pid 4714: value: true kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: log_connections
2009-07-06 11:15:02 DEBUG: pid 4714: value: true kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: log_hostname
2009-07-06 11:15:02 DEBUG: pid 4714: value: true kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: parallel_mode
2009-07-06 11:15:02 DEBUG: pid 4714: value: false kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: enable_query_cache
2009-07-06 11:15:02 DEBUG: pid 4714: value: false kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: pgpool2_hostname
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'docsys' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: system_db_hostname
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'docsys' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: system_db_port
2009-07-06 11:15:02 DEBUG: pid 4714: value: 5432 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: system_db_dbname
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'imm_dbv12' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: system_db_schema
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'public' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: system_db_user
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'postgres' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: system_db_password
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'password kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: enable_pool_hba
2009-07-06 11:15:02 DEBUG: pid 4714: value: false kind: 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: recovery_user
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'pgpool_001' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: recovery_password
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'password' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: recovery_1st_stage_command
2009-07-06 11:15:02 DEBUG: pid 4714: value: '' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: recovery_2nd_stage_command
2009-07-06 11:15:02 DEBUG: pid 4714: value: '' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: recovery_timeout
2009-07-06 11:15:02 DEBUG: pid 4714: value: 90 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: client_idle_limit_in_recovery
2009-07-06 11:15:02 DEBUG: pid 4714: value: 0 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: replication_timeout
2009-07-06 11:15:02 DEBUG: pid 4714: value: 5000 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: key: backend_hostname0
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'docsysfm' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: backend_port0
2009-07-06 11:15:02 DEBUG: pid 4714: value: 5432 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: pool_config: port slot number 0
2009-07-06 11:15:02 DEBUG: pid 4714: key: backend_weight0
2009-07-06 11:15:02 DEBUG: pid 4714: value: 1 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: pool_config: weight slot number 0 weight: 1.000000
2009-07-06 11:15:02 DEBUG: pid 4714: key: backend_data_directory0
2009-07-06 11:15:02 DEBUG: pid 4714: value: '/backup/postgres/data_001/' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: backend_hostname1
2009-07-06 11:15:02 DEBUG: pid 4714: value: 'docsys2' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: key: backend_port1
2009-07-06 11:15:02 DEBUG: pid 4714: value: 5432 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: pool_config: port slot number 1
2009-07-06 11:15:02 DEBUG: pid 4714: key: backend_weight1
2009-07-06 11:15:02 DEBUG: pid 4714: value: 1 kind: 2
2009-07-06 11:15:02 DEBUG: pid 4714: pool_config: weight slot number 1 weight: 1.000000
2009-07-06 11:15:02 DEBUG: pid 4714: key: backend_data_directory1
2009-07-06 11:15:02 DEBUG: pid 4714: value: '/backup/postgres/data_002/' kind: 4
2009-07-06 11:15:02 DEBUG: pid 4714: num_backends: 2 num_backends: 2 total_weight: 2.000000
2009-07-06 11:15:02 DEBUG: pid 4714: backend 0 weight: 1073741823.500000
2009-07-06 11:15:02 DEBUG: pid 4714: backend 1 weight: 1073741823.500000
2009-07-06 11:15:02 DEBUG: pid 4715: I am 4715
2009-07-06 11:15:02 DEBUG: pid 4716: I am 4716
2009-07-06 11:15:02 DEBUG: pid 4717: I am 4717
2009-07-06 11:15:02 DEBUG: pid 4718: I am 4718
2009-07-06 11:15:02 DEBUG: pid 4719: I am 4719
2009-07-06 11:15:02 DEBUG: pid 4720: I am 4720
2009-07-06 11:15:02 DEBUG: pid 4721: I am 4721
2009-07-06 11:15:02 DEBUG: pid 4722: I am 4722
2009-07-06 11:15:02 DEBUG: pid 4723: I am 4723
2009-07-06 11:15:02 DEBUG: pid 4724: I am 4724
2009-07-06 11:15:02 DEBUG: pid 4725: I am 4725
2009-07-06 11:15:02 DEBUG: pid 4726: I am 4726
2009-07-06 11:15:02 DEBUG: pid 4727: I am 4727
2009-07-06 11:15:02 DEBUG: pid 4728: I am 4728
2009-07-06 11:15:02 DEBUG: pid 4729: I am 4729
2009-07-06 11:15:02 DEBUG: pid 4730: I am 4730
2009-07-06 11:15:02 DEBUG: pid 4731: I am 4731
2009-07-06 11:15:02 DEBUG: pid 4732: I am 4732
2009-07-06 11:15:02 DEBUG: pid 4733: I am 4733
2009-07-06 11:15:02 DEBUG: pid 4734: I am 4734
2009-07-06 11:15:02 DEBUG: pid 4735: I am 4735
2009-07-06 11:15:02 DEBUG: pid 4736: I am 4736
2009-07-06 11:15:02 DEBUG: pid 4737: I am 4737
2009-07-06 11:15:02 DEBUG: pid 4738: I am 4738
2009-07-06 11:15:02 DEBUG: pid 4739: I am 4739
2009-07-06 11:15:02 DEBUG: pid 4740: I am 4740
2009-07-06 11:15:02 DEBUG: pid 4741: I am 4741
2009-07-06 11:15:02 DEBUG: pid 4742: I am 4742
2009-07-06 11:15:02 DEBUG: pid 4743: I am 4743
2009-07-06 11:15:02 DEBUG: pid 4744: I am 4744
2009-07-06 11:15:02 DEBUG: pid 4745: I am 4745
2009-07-06 11:15:02 DEBUG: pid 4746: I am 4746
2009-07-06 11:15:02 LOG:   pid 4714: pgpool successfully started
2009-07-06 11:15:02 DEBUG: pid 4747: I am PCP 4747

When I want to verify if the replication is working I've got that error message:

docsys:/var/lib/postgresql/8.3/main# /usr/lib/postgresql/8.3/bin/pgbench -i -h docsys -p 9999 imm_dbv12 -U postgres
ERROR: kind mismatch among backends. Possible last query was: "SET search_path = public" kind details are: 0[C] 1[N]
HINT: check data consistency among db nodes
server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.
docsys:/var/lib/postgresql/8.3/main#

pgpool on this site give me that error:

2009-07-06 11:17:54 DEBUG: pid 4715: I am 4715 accept fd 5
2009-07-06 11:17:54 LOG:   pid 4715: connection received: host=docsys port=48071
2009-07-06 11:17:54 DEBUG: pid 4715: Protocol Major: 1234 Minor: 5679 database: user:
2009-07-06 11:17:54 DEBUG: pid 4715: SSLRequest: sent N; retry startup
2009-07-06 11:17:54 DEBUG: pid 4715: Protocol Major: 3 Minor: 0 database: imm_dbv12 user: postgres
2009-07-06 11:17:54 DEBUG: pid 4715: new_connection: connecting 0 backend
2009-07-06 11:17:54 DEBUG: pid 4715: new_connection: connecting 1 backend
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length: slot: 0 length: 8
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length: slot: 1 length: 8
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 0 length: 25
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 1 length: 25
2009-07-06 11:17:54 DEBUG: pid 4715: 0 th backend: name: client_encoding value: UTF8
2009-07-06 11:17:54 DEBUG: pid 4715: 1 th backend: name: client_encoding value: UTF8
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 0 length: 23
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 1 length: 23
2009-07-06 11:17:54 DEBUG: pid 4715: 0 th backend: name: DateStyle value: ISO, MDY
2009-07-06 11:17:54 DEBUG: pid 4715: 1 th backend: name: DateStyle value: ISO, MDY
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 0 length: 25
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 1 length: 25
2009-07-06 11:17:54 DEBUG: pid 4715: 0 th backend: name: integer_datetimes value: on
2009-07-06 11:17:54 DEBUG: pid 4715: 1 th backend: name: integer_datetimes value: on
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 0 length: 20
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 1 length: 20
2009-07-06 11:17:54 DEBUG: pid 4715: 0 th backend: name: is_superuser value: on
2009-07-06 11:17:54 DEBUG: pid 4715: 1 th backend: name: is_superuser value: on
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 0 length: 25
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 1 length: 25
2009-07-06 11:17:54 DEBUG: pid 4715: 0 th backend: name: server_encoding value: UTF8
2009-07-06 11:17:54 DEBUG: pid 4715: 1 th backend: name: server_encoding value: UTF8
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 0 length: 25
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 1 length: 25
2009-07-06 11:17:54 DEBUG: pid 4715: 0 th backend: name: server_version value: 8.3.7
2009-07-06 11:17:54 DEBUG: pid 4715: 1 th backend: name: server_version value: 8.3.7
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 0 length: 35
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 1 length: 35
2009-07-06 11:17:54 DEBUG: pid 4715: 0 th backend: name: session_authorization value: postgres
2009-07-06 11:17:54 DEBUG: pid 4715: 1 th backend: name: session_authorization value: postgres
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 0 length: 36
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 1 length: 36
2009-07-06 11:17:54 DEBUG: pid 4715: 0 th backend: name: standard_conforming_strings value: off
2009-07-06 11:17:54 DEBUG: pid 4715: 1 th backend: name: standard_conforming_strings value: off
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 0 length: 22
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length2: master slot: 1 length: 22
2009-07-06 11:17:54 DEBUG: pid 4715: 0 th backend: name: TimeZone value: Portugal
2009-07-06 11:17:54 DEBUG: pid 4715: 1 th backend: name: TimeZone value: Portugal
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length: slot: 0 length: 12
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length: slot: 1 length: 12
2009-07-06 11:17:54 DEBUG: pid 4715: pool_send_auth_ok: send pid 29846 to frontend
2009-07-06 11:17:54 DEBUG: pid 4715: select_load_balancing_node: selected backend id is 0
2009-07-06 11:17:54 DEBUG: pid 4715: read_kind_from_backend: read kind from 0 th backend Z NUM_BACKENDS: 2
2009-07-06 11:17:54 DEBUG: pid 4715: read_kind_from_backend: read kind from 1 th backend Z NUM_BACKENDS: 2
2009-07-06 11:17:54 DEBUG: pid 4715: pool_process_query: kind from backend: Z
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length: slot: 0 length: 5
2009-07-06 11:17:54 DEBUG: pid 4715: pool_read_message_length: slot: 1 length: 5
2009-07-06 11:17:54 DEBUG: pid 4715: ReadyForQuery: message length: 5
2009-07-06 11:17:54 DEBUG: pid 4715: ReadyForQuery: transaction state: I
2009-07-06 11:17:54 DEBUG: pid 4715: read kind from frontend Q(51)
2009-07-06 11:17:54 LOG:   pid 4715: statement: SET search_path = public
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: Query: BEGIN
2009-07-06 11:17:54 DEBUG: pid 4715: detect_error: kind: C
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: kind: C
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: kind: N
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: kind: Z
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: transaction state: T
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: Query: BEGIN
2009-07-06 11:17:54 DEBUG: pid 4715: detect_error: kind: N
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: kind: N
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: kind: N
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: kind: C
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: kind: N
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: kind: Z
2009-07-06 11:17:54 DEBUG: pid 4715: do_command: transaction state: T
2009-07-06 11:17:54 DEBUG: pid 4715: waiting for backend 0 completing the query
2009-07-06 11:17:54 DEBUG: pid 4715: detect_error: kind: C
2009-07-06 11:17:54 DEBUG: pid 4715: detect_error: kind: C
2009-07-06 11:17:54 DEBUG: pid 4715: detect_error: kind: C
2009-07-06 11:17:54 DEBUG: pid 4715: waiting for backend 1 completing the query
2009-07-06 11:17:54 DEBUG: pid 4715: read_kind_from_backend: read kind from 0 th backend C NUM_BACKENDS: 2
2009-07-06 11:17:54 DEBUG: pid 4715: read_kind_from_backend: read kind from 1 th backend N NUM_BACKENDS: 2
2009-07-06 11:17:54 ERROR: pid 4715: read_kind_from_backend: 1 th kind N does not match with master or majority connection kind C

I can't really understand that... And the worst thing at the moment is thinking about online recovery if one the server goes down...

Tatsuo Ishii wrote:

Thanks to all. Now I understand better how pgpool works.
Now I've been able to made some successful test. Replication Mode is 
working perfectly.
The problem now is a little bit diferrent... I've just made a backup 
from the postgres production database, and freshly imported in two new 
databases in docsys and docsys2.
The problem is when I try any kind of connection to pgpool (in 9999 
port) I have the "kind mismatch error".


ex:
docsys:/home/rubenalves# /usr/lib/postgresql/8.3/bin/pgbench -i -h 
docsys -p 9999 imm_dbv12 -U postgres
ERROR:  kind mismatch among backends. Possible last query was: "SET 
search_path = public" kind details are: 0[C] 1[N]
HINT:  check data consistency among db nodes
server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.
docsys:/home/rubenalves#

I really can't understand because the both databases are IDENTICAL, how 
pgpool may find some differences?

Someone got an idea about this error?


You need to show us the log output with pgpool-II debug option
"-d".

Besides this, to make two databases "identical" by using
pg_dump/pg_restore is not enough for pgpool-II. pgpool-II requires two
database nodes "phyically identical". For this purpose you should use
tar/rsync or whatever tools to make a identical copy of database. In
your case probably you restore first database node by using pg_restore
then copy to second one by using tar or rsync.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

-- 
Ruben Alves 

System Analyst 
USI @ Instituto de Medicina Molecular

_______________________________________________
Pgpool-general mailing list
[email protected]
http://pgfoundry.org/mailman/listinfo/pgpool-general

Re: [Pgpool-general] Confusing... pgpool starts on both nodes, but don't replicate.

Reply via email to