[pgpool-committers: 1100] pgpool: Fix segmentation fault of child that occurs when startup packet

Yugo Nagata nagata at sraoss.co.jp
Tue Jul 2 12:01:39 JST 2013


Fix segmentation fault of child that occurs when startup packet has
no PostgreSQL user information.

When a startup packet has no PostgreSQL user specified, pgpool-II
terminated abnormally. You can reproduce it by

 $ psql -p 9999 -U ''

If enable_pool_hba is on, a child process terminates by segmentation
fault. Otherwise if enable_pool_hba is off, the error message is

 ERROR: pool_discard_cp: cannot get connection pool for user (null) database (null)

In both cases, psql terminates with no message on frontend.

To resolve it, if PostgreSQL user is not specified in startup packet,
the message as following is output to both log and frontend. This is
the same behavior as PostgreSQL.

 FATAL: no PostgreSQL user name specified in startup packet

Branch
------
V3_0_STABLE

Details
-------
http://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=e732c9b7683343ef8561900c9cb3df56828cb2a9

Modified Files
--------------
child.c |   28 +++++++++++++++++++++++++---
1 file changed, 25 insertions(+), 3 deletions(-)



More information about the pgpool-committers mailing list