Close() should not allowed since hold cursor + update may cause data inconsistency.
master/slave mode. If it's inside transaction, enable master_slave_dml, which means execute parse on master only. This will prevent unwanted parase executed on slave, which holds at least AccessShareLock on tables until transaction commits. It seems unamed statement does not release the lock until execute. Please note that, even with this fix, bind state will remain on slave if JDBC issues parse with autocommit off. This is because BEGIN parsed, bind on both master and slave but execute only on master. However, this is not harmfull since parse/bind does not hold any locks on tables.
…hout linking to libcrypt by some reasons which I don't know.
abnormaly, some global state variables are not reset. For this purpose, new function reset_variables() added. Remove unnecessary argument of end_load_balance().
This is almost same algorithm as PostgreSQL. I hope pgpool-II does not consume so much system resource any more...
rather than unhelpfull "server closed the connection unexpectedly" message. Patch provided by Glyn Astill with minor tweak by Tatsuo Ishii.
to frontend. Also add info to the message if it was backend or frontend to avoid confusion.
Refactor need_insert_lock to use pool_search_relcache and friends. Add LocalSessionId to child.c which manage per session counter of relcache. Allow to use temp tables with master/slave mode. Parse() failed. since Parse() was always sent to master and slave and slave does not have the temp table. To fix this, is_temp_table() added to pool_proto_modules.c which inquire particular table is a temporary one or not when INSERT/UPDATE/DELETE. If it's a temporary table, parse message is sent to only master. Note that /*NO LOAD BALANCE*/ directive can be used to control this. SELECT still needs /*NO LOAD BALANCE*/. It's hard to find all tables in a SELECT statement.
Teach do_command() that S (parameter status) should be ignored until receiving command complete.
block. See [pgpool-general-jp: 623] for more details.
http://lists.pgfoundry.org/pipermail/pgpool-general/2009-October/002188.html - Re-apply a fix for Red Hat Bugzilla #442372 - Add 2 new docs, per Tatsuo.