Log message:
Update pgpool2 to 3.4.2. Add SMF support.

3.4.2

* Bugfixes

3.4.1

* Bugfixes

3.4.0

New major version up from 3.3.

* Incompatible changes

    - Parallel query mode is obsoleted and is removed from
      pgpool.conf. This is due to the very few users using the mode
      (and the relatively high cost to maintain it).  Actual codes for
      the mode are still there and users can use the mode if they
      specify necessary parameters in pgpool.conf. Note, however, the
      next version of pgpool-II (will be 3.5.0) will actually remove
      the code.

    - "print_timestamp" parameter is removed. Instead new
      "log_line_prefix" should be used.

    - Recovery script now accepts 4 parameters, rather than 3 (the 4th
      parameter is the port number of master PostgreSQL). Existing
      3-parameter-style recovery scripts can be used if you don't care
      about information provided by the 4th parameter.

* New features

    - Allow fine control of load balancing by using application name
      or database name. For example, if a client has particular
      application name, read queries can be redirect to master node,
      rather than to one of slave nodes (Tatsuo Ishii)

    - Allow to print pgpool-II process names in the log output. New
      parameter "log_line_prefix", which is the printf-style string
      that is output at the beginning of each log line (Muhammad Usama)

    - Allow to control log verbosity like PostgreSQL. For this purpose
      new parameters "log_error_verbosity", \ 
"client_min_messages",
      "log_min_messages" are added (Muhammad Usama)

    - Allow to use SQL comments without disturbing load balancing if
      new parameter "allow_sql_comments" is on. If it's off, previous
      behavior is kept (Tatsuo Ishii)

    - Allow to skip unlogged tables checking by using new parameter
      "check_unlogged_table". This reduces the number of pgpool-II's
      internal catalog look up queries and enhances performance
      (Tatsuo Ishii)

    - Prevent listen backlog overflow by using new parameter
      "listen_backlog_multiplier" for very busy systems (Tatsuo Ishii)

    - Prevent connection timeout to backend by using new parameter
      "connect_timeout". This is useful in unstable networks
      (Tatsuo Ishii)

* Enhancements

    - Builtin SQL parser is now compatible with PostgreSQL 9.4 (Muhammad Usama)

    - Import PostgreSQL's memory manager and exception manager (Muhammad Usama)

    - Reorganize source code tree (Muhammad Usama)

    - The status file "pgpool_status" is now a plain ASCII file. This
      allows to register down PostgreSQL nodes before pgpool-II
      starts for example (Tatsuo Ishii)

    - Allow to use IPv6 address for PostgreSQ (Michael Stapelberg)

    - Allow to use IPv6 bind address for pgpool-II (Michael Stapelberg)

    - Rename all occurrence of "on memory query cache" to "in memory
      query cache" because latter is more correct in English (Tatsuo Ishii)

Log message:
Update pgpool2 to 3.3.3.

Bug fixes:
- installer: Fix bug that install of pgpool-II RPM fails (Yugo Nagata)
- installer: Fix to set up passwordless SSH from apache@localhost to
  postgres@localhost (Yugo Nagata)
- Fix bug that restarted pgpool's watchdog status is regarded as down
  (Yugo Nagata)
- doc: Add mention about "listen queue" and how to increase the \ 
"backlog"
  in the num_init_children section. (Tatsuo Ishii)
- Fix bug that watchdog status goes down even when only one of trusted
  servers get unpingable (Yugo Nagata)
- Fix bad performance of unlogged tables detection code. (Tatsuo Ishii)
- Fix primary node detection logic. (Tatsuo Ishii)
  There's a possibility that primary node is not detected. This happens
  in following situation.  node 0: primary, node 1: standby. Node 0 goes
  down. Health checking detects the fact but local status is not updated
  yet. Primary node finding (find_primary_node) runs. Node 0's status is
  yet healthy. Because find_primary_node fails to connect to node 0, it
  immediately returns -1 and fails to find that fact that node 1 is now
  primary.
  Fix is just continuing to look for primary node when fails to connect
  to a node.
- Add raw mode support to pgpool_setup. (Tatsuo Ishii)
- test: Integrate jdbc test to regression test. (Tatsuo Ishii)
- Fix jdbc DML fails when operated in raw mode and auto commit is off.
  (Tatsuo Ishii)
- Fix to output error message when wd_escalation_command fails with exit
  code other than 0 (Yugo Nagata)
- test: Add new regression test for query cache. (Tatsuo Ishii)
- Fix query cache bug with extended protocol. (Tatsuo Ishii)
  SELECT retrieves outdated cache even DML was executed in an expilicit
  transaction. The bug had been there since in memory query cache was
  born. Per [pgpool-general-jp: 1252].
- Add missing entries "relcache_size" and "check_temp_table" \ 
to show
  pool_status (Tatsuo Ishii)
- Fix to output error message when if_up_cmd fails. (Yugo Nagata)
- Avoid to send queries to unrelated nodes in streaming replication mode.
  (Tatsuo Ishii)
  Pgpool-II sends certain queries, such as BEGIN, END and SET commands to
  all of DB nodes. However in streaming replication mode, only primary
  node and at most one standby node are only concerned (if primacy node
  is selected as the load balance node, only 1 node is concerned).
- Fix possible buffer overrun problem and memory leak. (Tatsuo Ishii)
- Fix possible buffer overrun. (Tatsuo Ishii)
  Replace strcpy() with strlcpy(). Per Coverity report 1111478, 1111480,
  1111481.
- Add dubug messages for analyzing errors in if_up_cmd (Yugo Nagata)
- Fix freeing NULL. (Tatsuo Ishii)
- Do not enable query cache on materialized views. (Tatsuo Ishii)
- Fix memory leak. (Tatsuo Ishii)
- Fix a segmentation fault in parallel mode with system_db_hostname is
  empty (Yugo Nagata)
- Fix to output debug messages in processing pgpool.conf with -d option
  (Yugo Nagata)
  Previously, some debug messages in pool_get_config() ware not output
  even when -d option was used.
- Fix JDBC exception of prepared statement including now() in
  replication mode (Yugo Nagata)
  With JDBC, when a prepared statement is executed more than
  PrepareThreshold times, the statement is named and Describe message
  is sent after Parse. With named statement, pgpool rewrite now() to
  parameter in replication mode. Hence, rewritten query has additonal
  parameter than original. In this case, ParameterDescription message
  sent to frontend (response of Describe) should include OIDs of the
  same number os original query's parameters. Otherwize, JDBC throws
  ArrayIndexoutOfBoundsException.
- Fix backend error of prepared statement about table which has column whoes
  default value is now() in replication mode (Yugo Nagata)
  When pgpool parses a named prepared statement with default now(),
  timestamps are replaced to additional parameters. So, Bind message also
  should inclued additional parameter format codes. However, when the
  number of original parameter was one, pgpool didn't handle this. This
  caused a error like "incorrect binary data format in bind parameter 2".
- test: Fix a bug of regression test of JDBC that shows OK even when
  this fails (Yugo Nagata)
- test: Add a new regression test for JDBC's PrepareThreshold (Yugo Nagata)
- doc: Add description about parallel mode doesn't support PREPARE (Yugo Nagata)

Log message:
Update pgpool2 to 3.3.2

Notable changes in 3.3.0:
- Default monitoring method was changed from query mode to heartbeat mode.
- Failover/failback commands are executed in only one pgpool-II.
- In default, all the query caches on shared memory are cleared when
  standby pgpool-II escalates to active.
- Database name, user name, and password used for monitring other
  pgpool-II by query are specified by dedicated parameters.
- Import PostgreSQL 9.2 raw parser.
- Add a tool called pgpool_setup to set up pgpool-II and PostgreSQL
  temporary installation in current directory for *testing* purpose.
- Support installation method using CREATE EXTENSION for pgpool-recovery
  and pgpool-regclass.
- Add a function "pgpool_pgctl()" which enebles to execute
  pg_ctl stop/restart/reload (except for start) by SQL.
- Add new parameter "search_primary_node_timeout".

Full changelog:

http://www.pgpool.net/docs/pgpool-II-3.3.2/NEWS.txt

Log message:
Add dependency on postgresql*-server.
Add support for non-default recovery, regclass and walrecrunning libs.

Log message:
Fix MASTER_SITES

Log message:
Import postgresql91-pgpool2-3.2.4 as wip/pgpool2.

pgpool-II is a middleware that works between PostgreSQL
servers and a PostgreSQL database client. It talks
PostgreSQL's backend and frontend protocol, and relays
a connection between them. Therefore, a database application
(frontend) thinks that pgpool-II is the actual PostgreSQL
server, and the server (backend) sees pgpool-II as one
of its clients.