Аnton Тeihrib | 24 Oct 13:00 2011
Picon

What is recomended strategy for avoiding pgpool SPOF

Hi all!
Thanks a lot for pgpool, it's really nice tool.
But I'm a bit confusing about how can I avoid SPOF of pgpool?
In presentations I saw the solution of making 2 pgpool servers,
but how clients will determine to which server they should connect?
Also I think, that making 2 pgpool servers will bring the problem that:
one pgpool will think that master node is one data node, and another pgpool may
think about another data node as master. Is it possible? And what should we do in such case?
Best regards!

_______________________________________________
Pgpool-general mailing list
Pgpool-general@...
http://pgfoundry.org/mailman/listinfo/pgpool-general
Tatsuo Ishii | 21 Oct 10:10 2011
Picon

Re: "BEGIN; LOCK TABLE" sends to slave in Master/Slave mode

> Thank you for your reply!
> 
> But I have no way to change the request because the client proprietary.
> Is it possible in pgpool or modify the query or not to send to slave?
> Help white_function_list or black_function_list?

No.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> В Птн, 21/10/2011 в 15:23 +0900, Tatsuo Ishii пишет:
>> From: Успенский Игорь <admin <at> bestly.ru>
>> Subject: [Pgpool-general] "BEGIN; LOCK TABLE" sends to slave in Master/Slave mode
>> Date: Fri, 21 Oct 2011 09:48:48 +0400
>> Message-ID: <1319176128.17769.42.camel <at> admin.bestly.ru>
>> 
>> > Hello!
>> > 
>> > I using pgpool2 v3.1 and two PostgreSQL 9.0.4 (Master/Slave with stream
>> > replication)
>> > 
>> > Client send query "BEGIN;LOCK TABLE _1SCONNECT IN EXCLUSIVE MODE;" and
>> > pgpool sends this query master and slave, after slave print to log
>> > "cannot execute LOCK TABLE during recovery". Why pgpool sends this query
>> > to slave? How to change this behavior?
>> 
>> It's a know limitation of pgpool-II.
>> 
>> From:
>> http://pgpool.projects.postgresql.org/pgpool-II/doc/pgpool-en.html#restriction
>> 
>> > pgpool-II cannot process multi-statement queries. 
>> 
>> BEGIN;LOCK TABLE _1SCONNECT IN EXCLUSIVE MODE; is recognized as
>> "BEGIN;" statement by pgpool-II and it thinks that it needed to sent
>> to both master and slave.
>> 
>> The solution is to avoid multi-statement queries like BEGIN;LOCK TABLE_1SCONNECT IN EXCLUSIVE MODE;
>> 
>> Instead:
>> 
>> BEGIN;
>> LOCK TABLE _1SCONNECT IN EXCLUSIVE MODE;
>> --
>> Tatsuo Ishii
>> SRA OSS, Inc. Japan
>> English: http://www.sraoss.co.jp/index_en.php
>> Japanese: http://www.sraoss.co.jp
> 
_______________________________________________
Pgpool-general mailing list
Pgpool-general <at> pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general
Picon

"BEGIN; LOCK TABLE" sends to slave in Master/Slave mode

Hello!

I using pgpool2 v3.1 and two PostgreSQL 9.0.4 (Master/Slave with stream
replication)

Client send query "BEGIN;LOCK TABLE _1SCONNECT IN EXCLUSIVE MODE;" and
pgpool sends this query master and slave, after slave print to log
"cannot execute LOCK TABLE during recovery". Why pgpool sends this query
to slave? How to change this behavior?

My config:

-----------
listen_addresses = '*'
port = 5432
pcp_port = 9898
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
debug_level = 0
pid_file_name = '/var/run/pgpool/pgpool.pid'
replication_mode = false
load_balance_mode = true
replication_stop_on_mismatch = false
replicate_select = true
reset_query_list = 'ABORT; DISCARD ALL'
print_timestamp = false
master_slave_mode = true
master_slave_sub_mode = 'stream'
delay_threshold = 0
sr_check_period = 0
sr_check_user = postgres
sr_check_password = postgres
log_standby_delay = none
connection_cache = true
health_check_timeout = 20
health_check_period = 5
health_check_user = 'postgres'
health_check_password = 'postgres'
failover_command = '/usr/local/bin/failover_stream.sh %d %
H /var/lib/pgsql/data/trigger'
failback_command = ''
fail_over_on_backend_error = true
insert_lock = false
ignore_leading_white_space = true
log_statement = false
log_per_node_statement = false
log_connections = false
log_hostname = false
parallel_mode = false
enable_query_cache = false
pgpool2_hostname = 'T1'

backend_hostname2 = 'T2'
backend_port2 = 5432
backend_weight2 = 1
backend_data_directory2 = '/var/lib/pgsql/data'

backend_hostname3 = 'T3'
backend_port3 = 5432
backend_weight3 = 1
backend_data_directory3 = '/var/lib/pgsql/data'

enable_pool_hba = false
recovery_user = 'postgres'
recovery_password = ''
recovery_1st_stage_command = 'basebackup.sh'
recovery_2nd_stage_command = ''
recovery_timeout = 90
client_idle_limit_in_recovery = 0
lobj_lock_table = ''
-----------

Help with pgpool

Hi everyone, i wanted to test pgpool, so i setup postgresql to accept up to 2 conections, then i used pgbench to send 10 request from 10 clients and its failing, shouldn pgpool puts the 8 remaining conections in queue? Ideas???
 
Connection to database "test" failed:
FATAL:  sorry, too many clients already
Client 1 aborted in establishing connection.
Connection to database "test" failed:
FATAL:  sorry, too many clients already
Client 2 aborted in establishing connection.
Connection to database "test" failed:
FATAL:  sorry, too many clients already
Client 3 aborted in establishing connection.
Connection to database "test" failed:
FATAL:  sorry, too many clients already
Client 4 aborted in establishing connection.
Connection to database "test" failed:
FATAL:  sorry, too many clients already
Client 5 aborted in establishing connection.
Connection to database "test" failed:
FATAL:  sorry, too many clients already
Client 6 aborted in establishing connection.
Connection to database "test" failed:
FATAL:  sorry, too many clients already
Client 7 aborted in establishing connection.
Connection to database "test" failed:
FATAL:  sorry, too many clients already
Client 8 aborted in establishing connection.
Connection to database "test" failed:
_______________________________________________
Pgpool-general mailing list
Pgpool-general@...
http://pgfoundry.org/mailman/listinfo/pgpool-general
Picon

Problem when installing Pgpool-II

Hello everyone in the list, I try to install Pgpool-II version 3.1. The PostgreSQL server is installed under /opt/pgsql directory.

 

I install pgpool with this parameters:

./configure  --prefix=/opt/pgpool  --with-pgsql=/opt/pgsql/

 

and all is good, the problem is when I try to install pgpool-regclass or pgpool-recovey functions, because this error is shown:

 

make: pg_config: Command not found

make: *** No targets.  Stop.

 

I was searching  in google but I can not obtain a solution for this problem.

 

Can anybody help me to solve this problem??

 

 

Thank you very much for your time.

Regards.

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

Problem when installing Pgpool-II

Hello everyone in the list, I try to install Pgpool-II version 3.1. The PostgreSQL server is installed under /opt/pgsql directory.

 

I install pgpool with this parameters:

./configure  --prefix=/opt/pgpool  --with-pgsql=/opt/pgsql/

 

The problem is when I try to install pgpool-regclass or pgpool-recovey functions, because this error is shown:

 

make: pg_config: Command not found

make: *** No targets.  Stop.

 

Can anybody help me to solve this problem??

 

Thank you very much for your time.

Regards.

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

Problem when installing Pgpool-II

Hello everyone in the list, I try to install Pgpool-II version 3.1. The PostgreSQL server is installed under /opt/pgsql directory.

 

I install pgpool with this parameters:

./configure  --prefix=/opt/pgpool  --with-pgsql=/opt/pgsql/

 

The problem is when I try to install pgpool-regclass, because this error is shown:

 

make: pg_config: Command not found

make: *** No targets.  Stop.

 

Can anybody help me to solve this problem??

 

Thank you very much for your time.

Regards.

_______________________________________________
Pgpool-general mailing list
Pgpool-general@...
http://pgfoundry.org/mailman/listinfo/pgpool-general
Bryan Varner | 17 Oct 17:44 2011

Trouble with the JDBC drivers...

Greetings all, I'm new to the list.

I've been experimenting with pgpool since the 3.0.1 release.
We have never implemented this in production -- largely because of the errors we've found during testing.


We have intermittent failures with pgpool-II when using the JDBC driver.

I'm currently using:
   A brand-new build of pgpool-II version 3.1.
   postgresql 9.0-801-jdbc4 version of the JDBC drivers.

My testing server backends are:
   Postgres 9.0.4, UTF8, on 32bit Ubuntu 10.04.
   They are configured for streaming replication (which is working very well).

My java application is making use of the standard JDBC non-pooling data source (with autoCommit = true) to create connections on multiple threads.

Our production configuration currently looks like this:
  Application -> C3P0 (Connection Pool) -> JDBC Driver -> master database

I have tested the following configurations in my test environment:
  Application -> C3P0 -> JDBC Driver -> pgpool-II -> database(s)
  Application -> JDBC Driver -> pgpool-II -> database(s)

In both setups, I continue to have issues with prepared statements and 'portals' (I think) which the JDBC driver reports as non-existent.

I have set prepareThreshold=0 on the JDBC driver, to disable statement caching, and still get these errors.

Occasionally, during testing, we see messages that look like this:
Caused by: org.postgresql.util.PSQLException: ERROR: prepared statement "S_18" does not exist     at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2102)     at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1835)     at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)     at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:500)     at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:388)     at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:273)
This causes our application to (obviously) have issues.

Is there a known good configuration for the JDBC driver & data sources that should make this work reliably?

Attached is my pgpool configuration.

Thank you for any help / suggestions!

Regards,
 -Bryan
# ----------------------------
# pgPool-II configuration file
# ----------------------------
#
# This file consists of lines of the form:
#
#   name = value
#
# Whitespace may be used.  Comments are introduced with "#" anywhere on a line.
# The complete list of parameter names and allowed values can be found in the
# pgPool-II documentation.
#
# This file is read on server startup and when the server receives a SIGHUP
# signal.  If you edit the file on a running system, you have to SIGHUP the
# server for the changes to take effect, or use "pgpool reload".  Some
# parameters, which are marked below, require a server shutdown and restart to
# take effect.
#

#------------------------------------------------------------------------------
# CONNECTIONS
#------------------------------------------------------------------------------

# - pgpool Connection Settings -

listen_addresses = '*'
                                   # Host name or IP address to listen on:
                                   # '*' for all, '' for no TCP/IP connections
                                   # (change requires restart)
port = 5432
                                   # Port number
                                   # (change requires restart)
socket_dir = '/var/run/postgresql'
                                   # Unix domain socket path
                                   # The Debian package defaults to
                                   # /var/run/postgresql
                                   # (change requires restart)

# - pgpool Communication Manager Connection Settings -

pcp_port = 9898
                                   # Port number for pcp
                                   # (change requires restart)
pcp_socket_dir = '/var/run/postgresql'
                                   # Unix domain socket path for pcp
                                   # The Debian package defaults to
                                   # /var/run/postgresql
                                   # (change requires restart)

# - Backend Connection Settings -

backend_hostname0 = 'plindytestdb-0'
                                   # Host name or IP address to connect to for backend 0
backend_port0 = 5432
                                   # Port number for backend 0
backend_weight0 = 1
                                   # Weight for backend 0 (only in load balancing mode)
backend_data_directory0 = '/postgres/data/9.0/main'
                                   # Data directory for backend 0
backend_flag0 = 'DISALLOW_TO_FAILOVER'
                                   # Controls various backend behavior
                                   # ALLOW_TO_FAILOVER or DISALLOW_TO_FAILOVER

backend_hostname1 = 'plindytestdb-1'
backend_port1 = 5432
backend_weight1 = 2
backend_data_directory1 = '/postgres/data/9.0/main'
backend_flag1 = 'DISALLOW_TO_FAILOVER'

# - Authentication -

enable_pool_hba = on
                                   # Use pool_hba.conf for client authentication
authentication_timeout = 60
                                   # Delay in seconds to complete client authentication
                                   # 0 means no timeout.

# - SSL Connections -

ssl = off
                                   # Enable SSL support
                                   # (change requires restart)
#ssl_key = './server.key'
                                   # Path to the SSL private key file
                                   # (change requires restart)
#ssl_cert = './server.cert'
                                   # Path to the SSL public certificate file
                                   # (change requires restart)
#ssl_ca_cert = ''
                                   # Path to a single PEM format file
                                   # containing CA root certificate(s)
                                   # (change requires restart)
#ssl_ca_cert_dir = ''
                                   # Directory containing CA root certificate(s)
                                   # (change requires restart)

#------------------------------------------------------------------------------
# POOLS
#------------------------------------------------------------------------------

# - Pool size -

num_init_children = 30
                                   # Number of pools
                                   # (change requires restart)
max_pool = 1
                                   # Number of connections per pool
                                   # (change requires restart)

# - Life time -

child_life_time = 300
                                   # Pool exits after being idle for this many seconds
child_max_connections = 0
                                   # Pool exits after receiving that many connections
                                   # 0 means no exit
connection_life_time = 0
                                   # Connection to backend closes after being idle for this many seconds
                                   # 0 means no close
client_idle_limit = 0
                                   # Client is disconnected after being idle for that many seconds
                                   # (even inside an explicit transactions!)
                                   # 0 means no disconnection

#------------------------------------------------------------------------------
# LOGS
#------------------------------------------------------------------------------

# - Where to log -

log_destination = 'stderr'
                                   # Where to log
                                   # Valid values are combinations of stderr,
                                   # and syslog. Default to stderr.

# - What to log -

print_timestamp = on
                                   # Print timestamp on each line
                                   # (change requires restart)

log_connections = on
                                   # Log connections
log_hostname = on
                                   # Hostname will be shown in ps status
                                   # and in logs if connections are logged
log_statement = off
                                   # Log all statements
log_per_node_statement = off
                                   # Log all statements
                                   # with node and backend informations
log_standby_delay = 'if_over_threshold'
                                   # Log standby delay
                                   # Valid values are combinations of always,
                                   # if_over_threshold, none

# - Syslog specific -

syslog_facility = 'LOCAL0'
                                   # Syslog local facility. Default to LOCAL0
syslog_ident = 'pgpool'
                                   # Syslog program identification string
                                   # Default to 'pgpool'

# - Debug -

debug_level = 0
                                   # Debug message verbosity level
                                   # 0 means no message, 1 or more mean verbose

#------------------------------------------------------------------------------
# FILE LOCATIONS
#------------------------------------------------------------------------------

pid_file_name = '/var/run/postgresql/pgpool.pid'
                                   # PID file name
                                   # (change requires restart)
logdir = '/tmp'
                                   # Directory of pgPool status file
                                   # (change requires restart)

#------------------------------------------------------------------------------
# CONNECTION POOLING
#------------------------------------------------------------------------------

connection_cache = on
                                   # Activate connection pools
                                   # (change requires restart)

                                   # Semicolon separated list of queries
                                   # to be issued at the end of a session
                                   # The default is for 8.3 and later
reset_query_list = 'ABORT; DISCARD ALL'
                                   # The following one is for 8.2 and before
#reset_query_list = 'ABORT; RESET ALL; SET SESSION AUTHORIZATION DEFAULT'

#------------------------------------------------------------------------------
# REPLICATION MODE
#------------------------------------------------------------------------------

replication_mode = off
                                   # Activate replication mode
                                   # (change requires restart)
replicate_select = off
                                   # Replicate SELECT statements
                                   # when in replication or parallel mode
                                   # replicate_select is higher priority than
                                   # load_balance_mode.

insert_lock = off
                                   # Automatically locks a dummy row or a table
                                   # with INSERT statements to keep SERIAL data
                                   # consistency
                                   # Without SERIAL, no lock will be issued
lobj_lock_table = ''
                                   # When rewriting lo_creat command in
                                   # replication mode, specify table name to
                                   # lock

# - Degenerate handling -

replication_stop_on_mismatch = off
                                   # On disagreement with the packet kind
                                   # sent from backend, degenerate the node
                                   # which is most likely "minority"
                                   # If off, just force to exit this session

failover_if_affected_tuples_mismatch = off
                                   # On disagreement with the number of affected
                                   # tuples in UPDATE/DELETE queries, then
                                   # degenerate the node which is most likely
                                   # "minority".
                                   # If off, just abort the transaction to
                                   # keep the consistency

#------------------------------------------------------------------------------
# LOAD BALANCING MODE
#------------------------------------------------------------------------------

load_balance_mode = on
                                   # Activate load balancing mode
                                   # (change requires restart)
ignore_leading_white_space = on
                                   # Ignore leading white spaces of each query
white_function_list = ''
                                   # Comma separated list of function names
                                   # that don't write to database
                                   # Regexp are accepted
black_function_list = 'nextval,setval,allocate_barcode_block,ctrl_.*_materialization,matview_.*'
                                   # Comma separated list of function names
                                   # that write to database
                                   # Regexp are accepted

#------------------------------------------------------------------------------
# MASTER/SLAVE MODE
#------------------------------------------------------------------------------

master_slave_mode = on
                                   # Activate master/slave mode
                                   # (change requires restart)
master_slave_sub_mode = 'stream'
                                   # Master/slave sub mode
                                   # Valid values are combinations slony or
                                   # stream. Default is slony.
                                   # (change requires restart)

# - Streaming -

sr_check_period = 0
                                   # Streaming replication check period
                                   # Disabled (0) by default
sr_check_user = 'nobody'
                                   # Streaming replication check user
                                   # This is necessary even if you disable
                                   # streaming replication delay check with
                                   # sr_check_period = 0
sr_check_password = ''
                                   # Password for streaming replication check user
delay_threshold = 6144
                                   # Threshold before not dispatching query to standby node
                                   # Unit is in bytes
                                   # Disabled (0) by default

# - Special commands -

follow_master_command = ''
                                   # Executes this command after master failover
                                   # Special values:
                                   #   %d = node id
                                   #   %h = host name
                                   #   %p = port number
                                   #   %D = database cluster path
                                   #   %m = new master node id
                                   #   %H = hostname of the new master node
                                   #   %M = old master node id
                                   #   %P = old primary node id
                                   #   %% = '%' character

#------------------------------------------------------------------------------
# PARALLEL MODE AND QUERY CACHE
#------------------------------------------------------------------------------

parallel_mode = off
                                   # Activates parallel query mode
                                   # (change requires restart)
enable_query_cache = off
                                   # Activates query cache
                                   # (change requires restart)

pgpool2_hostname = ''
                                   # Set pgpool2 hostname 
                                   # (change requires restart)

# - System DB info -

system_db_hostname  = 'localhost'
                                   # (change requires restart)
system_db_port = 5432 
                                   # (change requires restart)
system_db_dbname = 'pgpool'
                                   # (change requires restart)
system_db_schema = 'pgpool_catalog'
                                   # (change requires restart)
system_db_user = 'pgpool'
                                   # (change requires restart)
system_db_password = ''
                                   # (change requires restart)

#------------------------------------------------------------------------------
# HEALTH CHECK
#------------------------------------------------------------------------------

health_check_period = 0
                                   # Health check period
                                   # Disabled (0) by default
health_check_timeout = 20
                                   # Health check timeout
                                   # 0 means no timeout
health_check_user = 'nobody'
                                   # Health check user
health_check_password = ''
                                   # Password for health check user

#------------------------------------------------------------------------------
# FAILOVER AND FAILBACK
#------------------------------------------------------------------------------

failover_command = ''
                                   # Executes this command at failover
                                   # Special values:
                                   #   %d = node id
                                   #   %h = host name
                                   #   %p = port number
                                   #   %D = database cluster path
                                   #   %m = new master node id
                                   #   %H = hostname of the new master node
                                   #   %M = old master node id
                                   #   %P = old primary node id
                                   #   %% = '%' character
failback_command = ''
                                   # Executes this command at failback.
                                   # Special values:
                                   #   %d = node id
                                   #   %h = host name
                                   #   %p = port number
                                   #   %D = database cluster path
                                   #   %m = new master node id
                                   #   %H = hostname of the new master node
                                   #   %M = old master node id
                                   #   %P = old primary node id
                                   #   %% = '%' character

fail_over_on_backend_error = on
                                   # Initiates failover when writing to the
                                   # backend communication socket fails
                                   # This is the same behaviour of pgpool-II
                                   # 2.2.x and previous releases
                                   # If set to off, pgpool will report an
                                   # error and disconnect the session.

#------------------------------------------------------------------------------
# ONLINE RECOVERY
#------------------------------------------------------------------------------

recovery_user = 'nobody'
                                   # Online recovery user
recovery_password = ''
                                   # Online recovery password
recovery_1st_stage_command = ''
                                   # Executes a command in first stage
recovery_2nd_stage_command = ''
                                   # Executes a command in second stage
recovery_timeout = 90
                                   # Timeout in seconds to wait for the
                                   # recovering node's postmaster to start up
                                   # 0 means no wait
client_idle_limit_in_recovery = 0
                                   # Client is disconnected after being idle
                                   # for that many seconds in the second stage
                                   # of online recovery
                                   # 0 means no disconnection
                                   # -1 means immediate disconnection

#------------------------------------------------------------------------------
# OTHERS
#------------------------------------------------------------------------------

relcache_expire = 0
                                   # Life time of relation cache in seconds.
                                   # 0 means no cache expiration(the default).
                                   # The relation cache is used for cache the
                                   # query result against PostgreSQL system
                                   # catalog to obtain various information
                                   # including table structures or if it's a
                                   # temporary table or not. The cache is
                                   # maintained in a pgpool child local memory
                                   # and being kept as long as it survives.
                                   # If someone modify the table by using
                                   # ALTER TABLE or some such, the relcache is
                                   # not consistent anymore.
                                   # For this purpose, cache_expiration
                                   # controls the life time of the cache.

_______________________________________________
Pgpool-general mailing list
Pgpool-general@...
http://pgfoundry.org/mailman/listinfo/pgpool-general
Nozomi Anzai | 14 Oct 06:10 2011
Picon

pgpoolAdmin 3.1.0 released

Pgpool Global Development Group is pleased to announce the
availability of pgpoolAdmin 3.1.0, the latest stable version of an
open source management tool for pgpool-II 3.1 series.

-----------------------------------------------------------------------
Changes from pgpoolAdmin 3.1.0:
-----------------------------------------------------------------------

  * Replace functions deprecated in PHP 5.3 (Anzai)

  * Sync pgpool.conf Setting with pgpool-II 3.1 (Anzai)

  * Add new parameters and remove deleted parameters in pgpool-II 3.1
    (Anzai)
    - new:
      follow_master_command, relcache_expire, backend_flag,
      sr_check_period, sr_check_user, sr_check_password, log_destination,
      syslog_facility, syslog_ident

    - deleted:
      pcp_timeout, backend_socket_dir

  * Add promote button in Master/Slave mode with streaming replication
    (Anzai)
    - This button is to execute pcp_promote_node.

  * Other small changes for pgpool-II 3.1 (Anzai)
    - When log_destination is syslog, Log button will be invisible.
    - Allow regex value in black_function_list and white_function_list.

  * Some fix (Anzai)
    - Change to save boolean values in pgpool.conf with on/off format.

-----------------------------------------------------------------------

You can download pgpoolAdmin 3.1.0 from:
http://pgfoundry.org/frs/download.php/2964/pgpoolAdmin-3.1.0.tar.gz

If you find any problem, please post to: pgpool-general@...

--

-- 
Nozomi Anzai
SRA OSS, Inc. Japan
Jean-Paul Argudo | 13 Oct 15:19 2011

Presenting whats new in pgpool 3.1 in Amsterdam

Hi there,

Just to let you know that I'll present pgpool-II 3.1 new features and
enhancements next week at the PostgreSQL Conference Europe 2011.

The talk was approved long time ago, but I just realized I forgot to
tell you :)

Last year's talk about pgpool-II was a great success, so I guess this
new talk was selected on this basis :)

I'll let you know how this new talk was received by the audience next week.

Cheers!

PS:

* Last year's talk:
http://www.postgresql.eu/events/schedule/pgday2010/session/80-why-your-postgresql-90-cluster-needs-pgpool-ii/

* This year talk:
http://www.postgresql.eu/events/schedule/pgconfeu2011/session/210-whats-new-in-pgpool-ii-31/

--

-- 
Jean-Paul Argudo
www.PostgreSQL.(fr|eu)
www.Dalibo.com

PGpool not pooling...

HI i am testing pgpool with pgbench, i am running the following:
 
pgbench Matt -U testuser -p 9999 -c 34 -t 10 -C -d
An i am noticing that when the conection goes up to the 32 client it stops working
 
client 32 executing \setrandom delta -5000 5000
client 32 sending BEGIN;
when i go to ps -aux i can see this in each process
 
postgres: testuser Matt 127.0.0.1(55016) idle in transaction
 
i already checked the pgpool.conf file and the maximun child conections option is set to 32 but from what i understand pgpool should put the remaining 2 conecntions in queue right?
 
connection_cache = true
What am i doing worng???
_______________________________________________
Pgpool-general mailing list
Pgpool-general@...
http://pgfoundry.org/mailman/listinfo/pgpool-general

Gmane