RE: [Patch] PQconnectPoll() is blocked if target_session_attrs is read-write

Tsunakawa-san Thank you for your comment. I understand the sense. I don't require an explicit rule. Regards Ryo Matsumura

RE: [Patch] PQconnectPoll() is blocked if target_session_attrs is read-write

From: Matsumura, Ryo [mailto:matsumura@jp.fujitsu.com] > Detail: > If target_session_attrs is set to read-write, PQconnectPoll() calls > PQsendQuery("SHOW transaction_read_only") althogh previous return value > was PGRES_POLLING_READING not WRITING. The current code probably assumes that PQsen

RE: [Patch] PQconnectPoll() is blocked if target_session_attrs is read-write

Kyotaro-san Thank you for your review. > First, this patch looks broken. I took a serious mistake. > You also need to update the corresponding documentation. I attach a new patch that includes updating of document. Regards Ryo Matasumura libpq_state_change_bugfix.ver1.1.patch Description: l

Re: [Patch] PQconnectPoll() is blocked if target_session_attrs is read-write

Hello. At Mon, 22 Jul 2019 02:28:22 +, "Matsumura, Ryo" wrote in <03040DFF97E6E54E88D3BFEE5F5480F74AC15BBD@G01JPEXMBYT04> > Hi > > # I rewrote my previous mail. > > PQconnectPoll() is used as method for asynchronous using externally or > internally. > If a caller confirms a socket ready

[Patch] PQconnectPoll() is blocked if target_session_attrs is read-write

Hi # I rewrote my previous mail. PQconnectPoll() is used as method for asynchronous using externally or internally. If a caller confirms a socket ready for writing or reading that is requested by return value of previous PQconnectPoll(), next PQconnectPoll() must not be blocked. But if the calle