[pgpool-committers: 4385] pgpool: Fix returning transaction state when "ready for query" message

Tatsuo Ishii ishii at postgresql.org
Sun Dec 10 21:21:05 JST 2017


Fix returning transaction state when "ready for query" message received.

We return primary or master node state of ready for query message to
frontend. In most cases this is good. However if other than primary
node or master node returns an error state (this could happen if load
balance node is other than primary or master node and the query is an
errornous SELECT), this should be returned to frontend, because the
frontend already received an error.

How much this affects to applications is not clear. However this
behavior has been there for long time, probably applications do not
care the state returned by ready for query message.

Branch
------
V3_3_STABLE

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=3f1d420542569bfb4f55037e06bfe22ce3ae2f7b

Modified Files
--------------
pool_proto_modules.c | 10 ++++++++++
1 file changed, 10 insertions(+)



More information about the pgpool-committers mailing list