<!ENTITY release SYSTEM "release.sgml">
<!ENTITY release-3.6 SYSTEM "release-3.6.sgml">
+<!ENTITY release-3.5 SYSTEM "release-3.5.sgml">
+<!ENTITY release-3.4 SYSTEM "release-3.4.sgml">
+<!ENTITY release-3.3 SYSTEM "release-3.3.sgml">
+<!ENTITY release-3.2 SYSTEM "release-3.2.sgml">
+<!ENTITY release-3.1 SYSTEM "release-3.1.sgml">
<!ENTITY release-old SYSTEM "release-old.sgml">
<!ENTITY acronyms SYSTEM "acronyms.sgml">
--- /dev/null
+<!-- doc/src/sgml/release-3.1.sgml -->
+<!-- See header comment in release.sgml about typical markup -->
+
+<sect1 id="release-3-1-21">
+<!--
+ <title>Release 3.1.21</title>
+ -->
+ <title>リリース 3.1.21</title>
+
+ <note>
+ <!--
+ <title>Release Date</title>
+ -->
+ <title>リリース日</title>
+ <simpara>2016-12-26</simpara>
+ </note>
+
+ <sect2>
+ <!--
+ <title>Bug fixes</title>
+ -->
+ <title>不具合修正</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <!--
+ 2016-10-27 [f37c592]
+ -->
+ <para>
+ <!--
+ Do not cancel a query when the query resulted in an error other than in native replication mode. (Tatsuo Ishii)
+ -->
+ネイティブレプリケーションモード以外の場合、エラーが発生した場合は、クエリをキャンセルしないように修正しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ It was intended to keep the consistency, but there's no point in other
+ than native replication mode.
+ -->
+本来は一貫性を維持するためにキャセルされるようになっていましたが、ネイティブレプリケーションモード以外の場合ではキャセルする必要がないので、修正しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-09 [8231f65]
+ -->
+ <para>
+ <!--
+ Do not use random() while generating MD5 salt. (Tatsuo Ishii)
+ -->
+MD5 salt を生成するときに、<function>random()</function> を使用しないように修正しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ random() should not be used in security related applications. To
+ replace random(), import PostmasterRandom() from PostgreSQL. Also
+ store current time at the start up of Pgpool-II main process for later
+ use.
+ -->
+<function>random()</function>関数はセキュリティ関連のアプリケーションに使用しないべきです。
+<function>random()</function>の代わりに<productname>PostgreSQL</productname>の<function>PostmasterRandom()</function> 使用するように変更しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-06 [891ce0f]
+ -->
+ <para>
+ <!--
+ Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)
+ -->
+クエリキャッシュが有効な場合、sync メッセージが廃棄されないよう修正しました。(Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+
+</sect1>
--- /dev/null
+<!-- doc/src/sgml/release-3.2.sgml -->
+<!-- See header comment in release.sgml about typical markup -->
+
+<sect1 id="release-3-2-18">
+<!--
+ <title>Release 3.2.18</title>
+ -->
+ <title>リリース 3.2.18</title>
+
+ <note>
+ <!--
+ <title>Release Date</title>
+ -->
+ <title>リリース日</title>
+ <simpara>2016-12-26</simpara>
+ </note>
+
+ <sect2>
+ <!--
+ <title>Bug fixes</title>
+ -->
+ <title>不具合修正</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <!--
+ 2016-12-20 [888ac16]
+ -->
+ <para>
+ <!--
+ Fix occasional segfault when query cache is enabled. (Tatsuo Ishii)
+ -->
+クエリキャッシュが有効になっている場合に、時々発生しうるセグメンテーション違反を修正しました。(bug 263) (Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-10-27 [f37c592]
+ -->
+ <para>
+ <!--
+ Do not cancel a query when the query resulted in an error other than in native replication mode. (Tatsuo Ishii)
+ -->
+ネイティブレプリケーションモード以外の場合、エラーが発生した場合は、クエリをキャンセルしないように修正しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ It was intended to keep the consistency, but there's no point in other
+ than native replication mode.
+ -->
+本来は一貫性を維持するためにキャセルされるようになっていましたが、ネイティブレプリケーションモード以外の場合ではキャセルする必要がないので、修正しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-09 [d7a9a98]
+ -->
+ <para>
+ <!--
+ Do not use random() while generating MD5 salt. (Tatsuo Ishii)
+ -->
+MD5 salt を生成するときに、<function>random()</function> を使用しないように修正しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ random() should not be used in security related applications. To
+ replace random(), import PostmasterRandom() from PostgreSQL. Also
+ store current time at the start up of Pgpool-II main process for later
+ use.
+ -->
+<function>random()</function>関数はセキュリティ関連のアプリケーションに使用しないべきです。
+<function>random()</function>の代わりに<productname>PostgreSQL</productname>の<function>PostmasterRandom()</function> 使用するように変更しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-06 [891ce0f]
+ -->
+ <para>
+ <!--
+ Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)
+ -->
+クエリキャッシュが有効な場合、sync メッセージが廃棄されないよう修正しました。(Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+
+</sect1>
--- /dev/null
+<!-- doc/src/sgml/release-3.3.sgml -->
+<!-- See header comment in release.sgml about typical markup -->
+
+<sect1 id="release-3-3-13">
+<!--
+ <title>Release 3.3.13</title>
+ -->
+ <title>リリース 3.3.13</title>
+
+ <note>
+ <!--
+ <title>Release Date</title>
+ -->
+ <title>リリース日</title>
+ <simpara>2016-12-26</simpara>
+ </note>
+
+ <sect2>
+ <!--
+ <title>Bug fixes</title>
+ -->
+ <title>不具合修正</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <!--
+ 2016-12-23 [a7e222d]
+ -->
+ <para>
+ <!--
+ Tightening up the watchdog security. (Muhammad Usama)
+ -->
+watchdog のセキュリティを強化しました。(Muhammad Usama)
+ </para>
+
+ <para>
+ <!--
+ Now wd_authkey uses the HMAC SHA-256 hashing.
+ -->
+wd_authkeyは、HMAC SHA-256ハッシングを使用するようになりました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-22 [1b293c4]
+ -->
+ <para>
+ <!--
+ Add pgpool_adm extension. (Bo Peng)
+ -->
+<productname>Pgpool-II</productname>のRPM にpgpool_adm extension が含まれるように修正しました。(Bo Peng)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-20 [6099e25]
+ -->
+ <para>
+ <!--
+ Fix occasional segfault when query cache is enabled. (Tatsuo Ishii)
+ -->
+クエリキャッシュが有効になっている場合に、時々発生しうるセグメンテーション違反を修正しました。(bug 263) (Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-10-27 [f37c592]
+ -->
+ <para>
+ <!--
+ Do not cancel a query when the query resulted in an error other than in native replication mode. (Tatsuo Ishii)
+ -->
+ネイティブレプリケーションモード以外の場合、エラーが発生した場合は、クエリをキャンセルしないように修正しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ It was intended to keep the consistency, but there's no point in other
+ than native replication mode.
+ -->
+本来は一貫性を維持するためにキャセルされるようになっていましたが、ネイティブレプリケーションモード以外の場合ではキャセルする必要がないので、修正しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-24 [8aa7586]
+ -->
+ <para>
+ <!--
+ Change the default value of search_primary_node_timeout from 10 to 300. (Tatsuo Ishii)
+ -->
+<xref linkend="guc-search-primary-node-timeout">のデフォルト値を10から300に変更しました。(Tatstuo Ishii)
+ </para>
+ <para>
+ <!--
+ Prior default value 10 seconds is sometimes too short for a standby to
+ be promoted.
+ -->
+これまでのデフォルト値10秒は、スタンバイを昇格する際には小さすぎでした。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-21 [b306e04]
+ -->
+ <para>
+ <!--
+ Fix the case when all backends are down then 1 node attached. (Tatsuo Ishii)
+ -->
+すべてのバックエンドがダウンした後に、1つのノードを復帰させる時の不具合が修正されました。(bug 248) (Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ When all backends are down, no connection is accepted. Then 1
+ PostgreSQL becomes up, and attach the node using pcp_attach_node. It
+ successfully finishes. However, when a new connection arrives, still
+ the connection is refused because pgpool child process looks into the
+ cached status, in which the recovered node is still in down status if
+ mode is streaming replication mode (native replication and other modes
+ are fine). Solution is, if all nodes are down, force to restart all
+ pgpool child.
+ -->
+すべてのノードがダウンすると、すべてのコネクションを受け付けなくなります。
+その状態で1つの<productname>PostgreSQL</productname>が起動し、<command>pcp_attach_node</command>コマンドでそのノードを復帰させます。
+そしてこのコマンドは成功しました。
+しかし、新しい接続が拒否されました。
+これは<productname>Pgpool-II</productname> の子プロセスがキャッシュされた古い情報を参照したのが原因でした。
+ストリーミングレプリケーションモードでは、このキャッシュされた情報において、復帰させたノードの状態がdownのままでした。
+（ネィティブレプリケーションモード、およびそれ以外のモードでは問題ありません）
+解決法として、全ノードがダウンした場合、強制的に全 <productname>Pgpool-II</productname>子プロセスを再起動するようにしました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-09 [8231f65]
+ -->
+ <para>
+ <!--
+ Do not use random() while generating MD5 salt. (Tatsuo Ishii)
+ -->
+MD5 salt を生成するときに、<function>random()</function> を使用しないように修正しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ random() should not be used in security related applications. To
+ replace random(), import PostmasterRandom() from PostgreSQL. Also
+ store current time at the start up of Pgpool-II main process for later
+ use.
+ -->
+<function>random()</function>関数はセキュリティ関連のアプリケーションに使用しないべきです。
+<function>random()</function>の代わりに<productname>PostgreSQL</productname>の<function>PostmasterRandom()</function> 使用するように変更しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-06 [891ce0f]
+ -->
+ <para>
+ <!--
+ Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)
+ -->
+クエリキャッシュが有効な場合、sync メッセージが廃棄されないよう修正しました。(Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+
+</sect1>
--- /dev/null
+<!-- doc/src/sgml/release-3.4.sgml -->
+<!-- See header comment in release.sgml about typical markup -->
+
+<sect1 id="release-3-4-9">
+<!--
+ <title>Release 3.4.9</title>
+ -->
+ <title>リリース 3.4.9</title>
+
+ <note>
+ <!--
+ <title>Release Date</title>
+ -->
+ <title>リリース日</title>
+ <simpara>2016-12-26</simpara>
+ </note>
+
+ <sect2>
+ <!--
+ <title>Bug fixes</title>
+ -->
+ <title>不具合修正</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <!--
+ 2016-12-23 [f5e9a2a]
+ -->
+ <para>
+ <!--
+ Tightening up the watchdog security. (Muhammad Usama)
+ -->
+watchdog のセキュリティを強化しました。(Muhammad Usama)
+ </para>
+
+ <para>
+ <!--
+ Now wd_authkey uses the HMAC SHA-256 hashing.
+ -->
+wd_authkeyは、HMAC SHA-256ハッシングを使用するようになりました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-22 [79f1ba8]
+ -->
+ <para>
+ <!--
+ Add pgpool_adm extension. (Bo Peng)
+ -->
+<productname>Pgpool-II</productname>のRPM にpgpool_adm extension が含まれるように修正しました。(Bo Peng)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-20 [888ac16]
+ -->
+ <para>
+ <!--
+ Fix occasional segfault when query cache is enabled. (Tatsuo Ishii)
+ -->
+クエリキャッシュが有効になっている場合に、時々発生しうるセグメンテーション違反を修正しました。(bug 263) (Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-06 [336e932]
+ -->
+ <para>
+ <!--
+ Fix a race condition in a signal handler per bug 265. (Tatsuo Ishii)
+ -->
+シグナルハンドラでの競合状態を修正しました。(bug 265) (Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ In child.c there's signal handler which calls elog. Since the signal
+ handler is not blocked against other signals while processing, deadlock
+ could occur in the system calls in the pgpool shutdown sequence. To
+ fix the problem, now the signal handler is blocked by using
+ POOL_SETMASK.
+ -->
+child.cには、elogを呼び出すシグナルハンドラがあります。 シグナルハンドラは処理中に他のシグナルに対してブロックされないため、pgpoolのシャットダウンシーケンスでシステムコールにデッドロックが発生する可能性がありました。 この問題を解決するために、シグナルハンドラはPOOL_SETMASKを使用してブロックされるように修正しました。
+ </para>
+ <para>
+ <!--
+ Ideally we should avoid calling elog in signal handlers though.
+ -->
+理想的にはシグナルハンドラでelogを呼び出すことを避けるべきです。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-10-27 [1fe3ab1]
+ -->
+ <para>
+ <!--
+ Do not cancel a query when the query resulted in an error other than in native replication mode. (Tatsuo Ishii)
+ -->
+ネイティブレプリケーションモード以外の場合、エラーが発生した場合は、クエリをキャンセルしないように修正しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ It was intended to keep the consistency, but there's no point in other
+ than native replication mode.
+ -->
+本来は一貫性を維持するためにキャセルされるようになっていましたが、ネイティブレプリケーションモード以外の場合ではキャセルする必要がないので、修正しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-10-27 [46579d6]
+ -->
+ <para>
+ <!--
+ Remove obsoleted option "-c" in pgpool command. (Tatsuo Ishii)
+ -->
+pgpool コマンドで廃止されたオプション"-c"を削除しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ Also fix typo in the help message.
+ -->
+また、helpメッセージのタイポを修正しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-24 [e0d0bc2]
+ -->
+ <para>
+ <!--
+ Change the default value of search_primary_node_timeout from 10 to 300. (Tatsuo Ishii)
+ -->
+<xref linkend="guc-search-primary-node-timeout">のデフォルト値を10から300に変更しました。(Tatstuo Ishii)
+ </para>
+ <para>
+ <!--
+ Prior default value 10 seconds is sometimes too short for a standby to
+ be promoted.
+ -->
+これまでのデフォルト値10秒は、スタンバイを昇格する際には小さすぎでした。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-21 [0409030]
+ -->
+ <para>
+ <!--
+ Fix the case when all backends are down then 1 node attached. (Tatsuo Ishii)
+ -->
+すべてのバックエンドがダウンした後に、1つのノードを復帰させる時の不具合が修正されました。(bug 248) (Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ When all backends are down, no connection is accepted. Then 1
+ PostgreSQL becomes up, and attach the node using pcp_attach_node. It
+ successfully finishes. However, when a new connection arrives, still
+ the connection is refused because pgpool child process looks into the
+ cached status, in which the recovered node is still in down status if
+ mode is streaming replication mode (native replication and other modes
+ are fine). Solution is, if all nodes are down, force to restart all
+ pgpool child.
+ -->
+すべてのノードがダウンすると、すべてのコネクションを受け付けなくなります。
+その状態で1つの<productname>PostgreSQL</productname>が起動し、<command>pcp_attach_node</command>コマンドでそのノードを復帰させます。
+そしてこのコマンドは成功しました。
+しかし、新しい接続が拒否されました。
+これは<productname>Pgpool-II</productname> の子プロセスがキャッシュされた古い情報を参照したのが原因でした。
+ストリーミングレプリケーションモードでは、このキャッシュされた情報において、復帰させたノードの状態がdownのままでした。
+（ネィティブレプリケーションモード、およびそれ以外のモードでは問題ありません）
+解決法として、全ノードがダウンした場合、強制的に全 <productname>Pgpool-II</productname>子プロセスを再起動するようにしました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-09 [85c813c]
+ -->
+ <para>
+ <!--
+ Do not use random() while generating MD5 salt. (Tatsuo Ishii)
+ -->
+MD5 salt を生成するときに、<function>random()</function> を使用しないように修正しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ <function>random()</function> should not be used in security related applications. To
+ replace <function>random()</function>, import <function>PostmasterRandom()</function> from PostgreSQL.
+ -->
+<function>random()</function>関数はセキュリティ関連のアプリケーションに使用しないべきです。
+<function>random()</function>の代わりに<productname>PostgreSQL</productname>の<function>PostmasterRandom()</function> 使用するように変更しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-06 [f9f098f]
+ -->
+ <para>
+ <!--
+ Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)
+ -->
+クエリキャッシュが有効な場合、sync メッセージが廃棄されないよう修正しました。(Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+
+</sect1>
--- /dev/null
+<!-- doc/src/sgml/release-3.5.sgml -->
+<!-- See header comment in release.sgml about typical markup -->
+
+<sect1 id="release-3-5-5">
+<!--
+ <title>Release 3.5.5</title>
+ -->
+ <title>リリース 3.5.5</title>
+
+ <note>
+ <!--
+ <title>Release Date</title>
+ -->
+ <title>リリース日</title>
+ <simpara>2016-12-26</simpara>
+ </note>
+
+ <sect2>
+ <!--
+ <title>Bug fixes</title>
+ -->
+ <title>不具合修正</title>
+
+ <itemizedlist>
+ <listitem>
+ <!--
+ 2016-12-23 [4124e5e]
+ -->
+ <para>
+ <!--
+ Tightening up the watchdog security. (Muhammad Usama)
+ -->
+watchdog のセキュリティを強化しました。(Muhammad Usama)
+ </para>
+
+ <para>
+ <!--
+ Now wd_authkey uses the HMAC SHA-256 hashing.
+ -->
+wd_authkeyは、HMAC SHA-256ハッシングを使用するようになりました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-22 [f8a157a]
+ -->
+ <para>
+ <!--
+ Add pgpool_adm extension. (Bo Peng)
+ -->
+<productname>Pgpool-II</productname>のRPM にpgpool_adm extension が含まれるように修正しました。(Bo Peng)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-20 [888ac16]
+ -->
+ <para>
+ <!--
+ Fix occasional segfault when query cache is enabled. (Tatsuo Ishii)
+ -->
+クエリキャッシュが有効になっている場合に、時々発生しうるセグメンテーション違反を修正しました。(bug 263) (Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-20 [9274f82]
+ -->
+ <para>
+ <!--
+ Fix packet kind does not match error in extended protocol per bug 231. (Tatsuo Ishii)
+ -->
+拡張プロトコルにおいて発生しうるkind mismatchエラーを修正しました。(bug 231) (Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ According to the bug231, the bug seem to bite you if all of
+ following conditions are met:
+ -->
+bug 231による、以下の条件がすべて満たされていると、このバグが発生する可能性がありました。
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <!--
+ Streaming replication mode
+ -->
+ストリーミングレプリケーションモード
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Load balance node is not node 0
+ -->
+ ロードバランスノードがnode 0ではない
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Extended protocol is used
+ -->
+拡張プロトコルを使用している
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ SELECT is executed, the statement is closed, then a
+ transaction command is executed
+ -->
+SELECTが実行され、ステートメントがクローズされた後、トランザクションコマンドが実行されている
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ <!--
+ The sequence of how the problem bites is:
+ -->
+問題の発生順序:
+ <orderedlist>
+ <listitem>
+ <para>
+ <!--
+ SELECT executes on statement S1 on the load balance node 1
+ -->
+ロードバランスノード1でステートメントS1のSELECTが実行されます。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Frontend send Close statement
+ -->
+フロントエンドがクローズステートメントを送ります。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Pgool-II forward it to backend 1
+ -->
+Pgpool-IIはそれをバックエンド1に転送します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Frontend sends Parse, Bind, Execute of COMMIT
+ -->
+フロントエンドは、Parse、Bind、COMMIT の Execute を送信します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Pgool-II forward it to backend 0 & 1
+ -->
+Pgpool-IIはそれをバックエンド0と1に転送します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Frontend sends sync message
+ -->
+フロントエンドが同期メッセージを送信します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Pgool-II forward it to backend 0 & 1
+ -->
+Pgpool-IIはそれをバックエンド0と1に転送します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Backend 0 replies back Parse complete ("1"), while
+ backend 1 replies back close complete ("3") because of
+ #3.
+ -->
+バックエンド0はParse complete（ "1"）を返しますが、バックエンド1は＃3によりcloes complete（ "3"）を返します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Kind mismatch occurs
+ -->
+Kind mismatch が発生します。
+ </para>
+ </listitem>
+ </orderedlist>
+
+ </para>
+ <para>
+ <!--
+ The solution is, in #3, let Pgpool-II wait for response from backend
+ 1, but do not read the response message. Later on Pgpool-II's state
+ machine will read the response from it before the sync message is sent
+ in #6. With this, backend 1 will reply back "1" in #8, and the kind
+ mismatch error does not occur.
+ -->
+解決策は、＃3では、Pgpool-IIがバックエンド1からの応答を待つようにしますが、応答メッセージは読み取らないようにします。 その後、Pgpool-IIの状態マシンは、＃6で同期メッセージが送信される前に、その応答を読み込みます。 これによりバックエンド1は＃8で "1"を返信し、kind mismatchエラーは発生しなくなります。
+ </para>
+ <para>
+ <!--
+ Also, fix not calling pool_set_doing_extended_query_message() when
+ receives Close message. (I don't know why it was missed).
+ -->
+また、Closeメッセージを受け取ったときにpool_set_doing_extended_query_message（）が呼び出されない不具合を修正しました。
+ </para>
+ <para>
+ <!--
+ New regression test "067.bug231" was added.
+ -->
+新しいリグレッションテスト "067.bug231"が追加されました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-06 [336e932]
+ -->
+ <para>
+ <!--
+ Fix a race condition in a signal handler per bug 265. (Tatsuo Ishii)
+ -->
+シグナルハンドラでの競合状態を修正しました。(bug 265) (Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ In child.c there's signal handler which calls elog. Since the signal
+ handler is not blocked against other signals while processing, deadlock
+ could occur in the system calls in the pgpool shutdown sequence. To
+ fix the problem, now the signal handler is blocked by using
+ POOL_SETMASK.
+ -->
+child.cには、elogを呼び出すシグナルハンドラがあります。 シグナルハンドラは処理中に他のシグナルに対してブロックされないため、pgpoolのシャットダウンシーケンスでシステムコールにデッドロックが発生する可能性がありました。 この問題を解決するために、シグナルハンドラはPOOL_SETMASKを使用してブロックされるように修正されました。
+ </para>
+ <para>
+ <!--
+ Ideally we should avoid calling elog in signal handlers though.
+ -->
+理想的にはシグナルハンドラでelogを呼び出すことを避けるべきです。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-11-26 [045a59f]
+ -->
+ <para>
+ <!--
+ Back porting the improved failover command propagation mechanism from Pgpool-II 3.6 (Muhammad Usama)
+ -->
+<productname>Pgpool-II</productname> 3.6 でのフェイルオーバーコマンドの転送処理の改善がバックポートされました。(Muhammad Usama)
+ </para>
+ <para>
+ <!--
+ Overhauling the design of how failover, failback and promote node commands are
+ propagated to the watchdog nodes. Previously the watchdog on pgpool-II node that
+ needs to perform the node command (failover, failback or promote node) used to
+ broadcast the failover command to all attached pgpool-II nodes. And this
+ sometimes makes the synchronization issues, especially when the watchdog cluster
+ contains a large number of nodes and consequently the failover command sometimes
+ gets executed by more than one pgpool-II.
+ -->
+これまでは、Pgpool-II ノードの watchdogがすべての接続されたノードにフェイルオーバーコマンド(failover、 failback 及び promote node)を転送していました。多数のノードが含まれているwatchdogクラスタでは、フェールオーバーコマンドが複数のPgpool-IIによって実行されることによって、データの同期問題を引き起こす可能性がありました。このコミットでは、すべてのフェイルオーバーコマンド(failover、 failback 及び promote node)が master/coordinator watchdog に転送され、master/coordinator watchdogはすべてのスタンバイノードに転送するようになりました。
+ </para>
+ <para>
+ <!--
+ Now with this commit all the node commands are forwarded to the
+ master/coordinator watchdog, which in turn propagates to all standby nodes.
+ Apart from above the commit also changes the failover command interlocking
+ mechanism and now only the master/coordinator node can become the lock holder
+ so the failover commands will only get executed on the master/coordinator node.
+ -->
+また、今回の修正では、インターロック機能も変更されました。master/coordinatorノードのみがロックホルダになり、フェイルオーバコマンドはmaster/coordinatorノードでのみ実行されます。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-10-27 [f37c592]
+ -->
+ <para>
+ <!--
+ Do not cancel a query when the query resulted in an error other than in native replication mode. (Tatsuo Ishii)
+ -->
+ネイティブレプリケーションモード以外の場合、エラーが発生した場合は、クエリをキャンセルしないように修正しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ It was intended to keep the consistency, but there's no point in other
+ than native replication mode.
+ -->
+本来は一貫性を維持するためにキャセルされるようになっていましたが、ネイティブレプリケーションモード以外の場合ではキャセルする必要がないので、修正しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-10-27 [c9e203d]
+ -->
+ <para>
+ <!--
+ Remove obsoleted option "-c" in pgpool command. (Tatsuo Ishii)
+ -->
+pgpool コマンドで廃止されたオプション"-c"を削除しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ Also fix typo in the help message.
+ -->
+また、helpメッセージのタイポを修正しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-10-18 [8da0e7f]
+ -->
+ <para>
+ <!--
+ Fix for 0000252: authentication failed error when PCP command is cancelled... (Muhammad Usama)
+ -->
+ PCPコマンドがキャンセルされたときの認証失敗エラーが修正されました。(bug 252) (Muhammad Usama)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-24 [8aa7586]
+ -->
+ <para>
+ <!--
+ Change the default value of search_primary_node_timeout from 10 to 300. (Tatsuo Ishii)
+ -->
+<xref linkend="guc-search-primary-node-timeout">のデフォルト値を10から300に変更しました。(Tatstuo Ishii)
+ </para>
+ <para>
+ <!--
+ Prior default value 10 seconds is sometimes too short for a standby to
+ be promoted.
+ -->
+これまでのデフォルト値10秒は、スタンバイを昇格する際には小さすぎでした。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-21 [b306e04]
+ -->
+ <para>
+ <!--
+ Fix the case when all backends are down then 1 node attached. (Tatsuo Ishii)
+ -->
+すべてのバックエンドがダウンした後に、1つのノードを復帰させる時の不具合が修正されました。(bug 248) (Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ When all backends are down, no connection is accepted. Then 1
+ PostgreSQL becomes up, and attach the node using pcp_attach_node. It
+ successfully finishes. However, when a new connection arrives, still
+ the connection is refused because pgpool child process looks into the
+ cached status, in which the recovered node is still in down status if
+ mode is streaming replication mode (native replication and other modes
+ are fine). Solution is, if all nodes are down, force to restart all
+ pgpool child.
+ -->
+すべてのノードがダウンすると、すべてのコネクションを受け付けなくなります。
+その状態で1つの<productname>PostgreSQL</productname>が起動し、<command>pcp_attach_node</command>コマンドでそのノードを復帰させます。
+そしてこのコマンドは成功しました。
+しかし、新しい接続が拒否されました。
+これは<productname>Pgpool-II</productname> の子プロセスがキャッシュされた古い情報を参照したのが原因でした。
+ストリーミングレプリケーションモードでは、このキャッシュされた情報において、復帰させたノードの状態がdownのままでした。
+（ネィティブレプリケーションモード、およびそれ以外のモードでは問題ありません）
+解決法として、全ノードがダウンした場合、強制的に全 <productname>Pgpool-II</productname>子プロセスを再起動するようにしました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-20 [a38fa09]
+ -->
+ <para>
+ <!--
+ Fix for: [pgpool-general: 4997] Avoiding downtime when pgpool changes require a restart (Muhammad Usama)
+ -->
+再起動が必要なパラメータの設定を変更した際の<productname>Pgpool-II</productname>停止が起こらないようにしました。(Muhammad Usama)
+ </para>
+ <para>
+ <!--
+ To fix this, The verification mechanism of configuration parameter values is
+ reversed, previously the standby nodes used to verify their parameter values
+ against the respective values on the master pgpool-II node and when the
+ inconsistency was found the FATAL error was thrown, now with this commit the
+ verification responsibility is delegated to the master pgpool-II node.
+ Now the master node will verify the configuration parameter values of each
+ joining standby node against its local values and will produce
+ a WARNING message instead of an error in case of a difference.
+ This way the nodes having the different configurations will also be allowed to
+ join the watchdog cluster and the user has to manually look out for the
+ configuration inconsistency warnings in the master pgpool-II log to avoid the
+ surprises at the time of pgpool-II master switch over.
+ -->
+この修正のために、設定パラメータの検証機構の順序を逆にしました。
+以前はスタンバイノードが<productname>Pgpool-II</productname>マスターノードに対して設定パラメータの値を検証し、不整合が見つかった場合にはFATALエラーが出力されていました。
+この修正で、<productname>Pgpool-II</productname>マスターノードに検証の役割が移譲されました。
+マスターノードは参加している個々のスタンバイノードの設定値をローカルの設定値と比較し、違っている場合にはエラーではなくてWARNINGメッセージを出力します。
+この方法では、watchdogクラスタとユーザは、手動でマスター<productname>Pgpool-II</productname>ログの中から不整合ワーニングを見つけて、<productname>Pgpool-II</productname>マスターのスイッチオーバが見つかった時に驚くようなことが起こらないようにしなければなりません。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-13 [1c99580]
+ -->
+ <para>
+ <!--
+ Add compiler flag "-fno-strict-aliasing" in <filename>configure.ac</filename> to fix compiler error. (Tatsuo Ishii)
+ -->
+ コンパイルエラーを修正するために、<filename>configure.ac</filename>
+ ファイルにコンパイルフラグ "-fno-strict-aliasing" が追加されました。(Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-09 [8231f65]
+ -->
+ <para>
+ <!--
+ Do not use random() while generating MD5 salt. (Tatsuo Ishii)
+ -->
+MD5 salt を生成するときに、<function>random()</function> を使用しないように修正しました。(Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ <function>random()</function> should not be used in security related applications. To
+ replace <function>random()</function>, import <function>PostmasterRandom()</function> from PostgreSQL.
+ -->
+<function>random()</function>関数はセキュリティ関連のアプリケーションに使用しないべきです。
+<function>random()</function>の代わりに<productname>PostgreSQL</productname>の<function>PostmasterRandom()</function> 使用するように変更しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-09-06 [891ce0f]
+ -->
+ <para>
+ <!--
+ Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)
+ -->
+クエリキャッシュが有効な場合、sync メッセージが廃棄されないよう修正しました。(Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+
+</sect1>
</sect2>
</sect1>
+
+<sect1 id="release-3-6-1">
+<!--
+ <title>release 3.6.1</title>
+ -->
+ <title>リリース 3.6.1</title>
+
+ <note>
+ <title>リリース日</title>
+ <simpara>2016-12-26</simpara>
+ </note>
+
+ <sect2>
+ <!--
+ <title>Bug fixes</title>
+ -->
+ <title>不具合修正</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <!--
+ 2016-12-23 [4124e5e]
+ -->
+ <para>
+ <!--
+ Tightening up the watchdog security. (Muhammad Usama)
+ -->
+watchdog のセキュリティを強化しました。(Muhammad Usama)
+ </para>
+
+ <para>
+ <!--
+ Now wd_authkey uses the HMAC SHA-256 hashing.
+ -->
+wd_authkeyは、HMAC SHA-256ハッシングを使用するようになりました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-22 [f8a157a]
+ -->
+ <para>
+ <!--
+ Add pgpool_adm extension. (Bo Peng)
+ -->
+<productname>Pgpool-II</productname>のRPM にpgpool_adm extension が含まれるように修正しました。(Bo Peng)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-20 [888ac16]
+ -->
+ <para>
+ <!--
+ Fix occasional segfault when query cache is enabled. (Tatsuo Ishii)
+ -->
+クエリキャッシュが有効になっている場合に、時々発生しうるセグメンテーション違反を修正しました。(bug 263) (Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-20 [9274f82]
+ -->
+ <para>
+ <!--
+ Fix packet kind does not match error in extended protocol per bug 231. (Tatsuo Ishii)
+ -->
+拡張プロトコルにおいて発生しうるkind mismatchエラーを修正しました。(bug 231) (Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ According to the bug231, the bug seem to bite you if all of
+ following conditions are met:
+ -->
+bug 231による、以下の条件がすべて満たされていると、このバグが発生する可能性がありました。
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <!--
+ Streaming replication mode
+ -->
+ストリーミングレプリケーションモード
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Load balance node is not node 0
+ -->
+ ロードバランスノードがnode 0ではない
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Extended protocol is used
+ -->
+拡張プロトコルを使用している
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ SELECT is executed, the statement is closed, then a
+ transaction command is executed
+ -->
+SELECTが実行され、ステートメントがクローズされた後、トランザクションコマンドが実行されている
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ <!--
+ The sequence of how the problem bites is:
+ -->
+問題の発生順序:
+ <orderedlist>
+ <listitem>
+ <para>
+ <!--
+ SELECT executes on statement S1 on the load balance node 1
+ -->
+ロードバランスノード1でステートメントS1のSELECTが実行されます。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Frontend send Close statement
+ -->
+フロントエンドがクローズステートメントを送ります。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Pgool-II forward it to backend 1
+ -->
+Pgpool-IIはそれをバックエンド1に転送します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Frontend sends Parse, Bind, Execute of COMMIT
+ -->
+フロントエンドは、Parse、Bind、COMMIT の Execute を送信します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Pgool-II forward it to backend 0 & 1
+ -->
+Pgpool-IIはそれをバックエンド0と1に転送します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Frontend sends sync message
+ -->
+フロントエンドが同期メッセージを送信します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Pgool-II forward it to backend 0 & 1
+ -->
+Pgpool-IIはそれをバックエンド0と1に転送します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Backend 0 replies back Parse complete ("1"), while
+ backend 1 replies back close complete ("3") because of
+ #3.
+ -->
+バックエンド0はParse complete（ "1"）を返しますが、バックエンド1は＃3によりcloes complete（ "3"）を返します。
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--
+ Kind mismatch occurs
+ -->
+Kind mismatch が発生します。
+ </para>
+ </listitem>
+ </orderedlist>
+
+ </para>
+ <para>
+ <!--
+ The solution is, in #3, let Pgpool-II wait for response from backend
+ 1, but do not read the response message. Later on Pgpool-II's state
+ machine will read the response from it before the sync message is sent
+ in #6. With this, backend 1 will reply back "1" in #8, and the kind
+ mismatch error does not occur.
+ -->
+解決策は、＃3では、Pgpool-IIがバックエンド1からの応答を待つようにしますが、応答メッセージは読み取らないようにします。 その後、Pgpool-IIの状態マシンは、＃6で同期メッセージが送信される前に、その応答を読み込みます。 これによりバックエンド1は＃8で "1"を返信し、kind mismatchエラーは発生しなくなります。
+ </para>
+ <para>
+ <!--
+ Also, fix not calling pool_set_doing_extended_query_message() when
+ receives Close message. (I don't know why it was missed).
+ -->
+また、Closeメッセージを受け取ったときにpool_set_doing_extended_query_message（）が呼び出されない不具合を修正しました。
+ </para>
+ <para>
+ <!--
+ New regression test "067.bug231" was added.
+ -->
+新しいリグレッションテスト "067.bug231"を追加しました。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-06 [336e932]
+ -->
+ <para>
+ <!--
+ Fix a race condition in a signal handler per bug 265. (Tatsuo Ishii)
+ -->
+シグナルハンドラでの競合状態を修正しました。(bug 265) (Tatsuo Ishii)
+ </para>
+ <para>
+ <!--
+ In child.c there's signal handler which calls elog. Since the signal
+ handler is not blocked against other signals while processing, deadlock
+ could occur in the system calls in the pgpool shutdown sequence. To
+ fix the problem, now the signal handler is blocked by using
+ POOL_SETMASK.
+ -->
+child.cには、elogを呼び出すシグナルハンドラがあります。 シグナルハンドラは処理中に他のシグナルに対してブロックされないため、pgpoolのシャットダウンシーケンスでシステムコールにデッドロックが発生する可能性がありました。 この問題を解決するために、シグナルハンドラはPOOL_SETMASKを使用してブロックされるように修正されました。
+ </para>
+ <para>
+ <!--
+ Ideally we should avoid calling elog in signal handlers though.
+ -->
+理想的にはシグナルハンドラでelogを呼び出すことを避けるべきです。
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-11-24 [cc452ad]
+ -->
+ <para>
+ <!--
+ Fix wrong minimum configuration value for client_idle_limit_in_recovery. (Tatsuo Ishii)
+ -->
+誤ったclient_idle_limit_in_recoveryの最小設定値を修正しました。(bug 264) (Tatsuo Ishii)
+ </para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-11-22 [94d9378]
+ -->
+ <para>
+ <!--
+ Allow to execute "make xslthtml" under doc.ja. (Tatsuo Ishii)
+ -->
+doc.jaの下で "make xslthtml"を実行できるように修正しました。(Tatsuo Ishii)
+ </para>
+ <para>
+
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+
+</sect1>
subsets can easily be copied into back branches.
-->
-&release-3.6;
<!--
&release-3.7;
-->
+&release-3.6;
+&release-3.5;
+&release-3.4;
+&release-3.3;
+&release-3.2;
+&release-3.1;
</appendix>
-<!ENTITY version "3.6.0">
+<!ENTITY version "3.7devel">
<!-- doc/src/sgml/release-3.1.sgml -->
<!-- See header comment in release.sgml about typical markup -->
-<sect1 id="release-3-1-18">
- <title>Release 3.1.18</title>
+<sect1 id="release-3-1-21">
+ <title>Release 3.1.21</title>
<note>
<title>Release Date</title>
<simpara>2016-12-26</simpara>
</note>
- <sect2>
- <title>Changes</title>
-
- <itemizedlist>
-
- <listitem>
- <!--
- 2016-12-20 [3b2e955]
- -->
- <para>
- Add 3.5.5 release note. (Tatsuo Ishii)
- </para>
- </listitem>
- </itemizedlist>
- </sect2>
-
<sect2>
<title>Bug fixes</title>
<itemizedlist>
- <listitem>
- <!--
- 2016-12-20 [888ac16]
- -->
- <para>
- Fix occasional segfault when query cache is enabled. (Tatsuo Ishii)
- </para>
- <para>
- Per bug 263.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-12-20 [9274f82]
- -->
- <para>
- Fix packet kind does not match error in extended protocol per bug 231. (Tatsuo Ishii)
- </para>
- <para>
- According to the bug231, the bug seem to bite you if all of
- following conditions are met:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Streaming replication mode
- </para>
- </listitem>
- <listitem>
- <para>
- Load balance node is not node 0
- </para>
- </listitem>
- <listitem>
- <para>
- Extended protocol is used
- </para>
- </listitem>
- <listitem>
- <para>
- SELECT is executed, the statement is closed, then a
- transaction command is executed
- </para>
- </listitem>
- </itemizedlist>
- <para>
- The sequence of how the problem bites is:
- <orderedlist>
- <listitem>
- <para>
- SELECT executes on statement S1 on the load balance node 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend send Close statement
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend sends Parse, Bind, Execute of COMMIT
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 0 & 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend sends sync message
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 0 & 1
- </para>
- </listitem>
- <listitem>
- <para>
- Backend 0 replies back Parse complete ("1"), while
- backend 1 replies back close complete ("3") because of
- #3.
- </para>
- </listitem>
- <listitem>
- <para>
- Kind mismatch occurs
- </para>
- </listitem>
- </orderedlist>
-
- </para>
- <para>
- The solution is, in #3, let Pgpool-II wait for response from backend
- 1, but do not read the response message. Later on Pgpool-II's state
- machine will read the response from it before the sync message is sent
- in #6. With this, backend 1 will reply back "1" in #8, and the kind
- mismatch error does not occur.
- </para>
- <para>
- Also, fix not calling pool_set_doing_extended_query_message() when
- receives Close message. (I don't know why it was missed).
- </para>
- <para>
- New regression test "067.bug231" was added.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-12-06 [336e932]
- -->
- <para>
- Fix a race condition in a signal handler per bug 265. (Tatsuo Ishii)
- </para>
- <para>
- In child.c there's signal handler which calls elog. Since the signal
- handler is not blocked against other signals while processing, deadlock
- could occur in the system calls in the pgpool shutdown sequence. To
- fix the problem, now the signal handler is blocked by using
- POOL_SETMASK.
- </para>
- <para>
- Ideally we should avoid calling elog in signal handlers though.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-11-26 [045a59f]
- -->
- <para>
- Back porting the improved failover command propagation mechanism from Pgpool-II 3.6 (Muhammad Usama)
- </para>
- <para>
- Overhauling the design of how failover, failback and promote node commands are
- propagated to the watchdog nodes. Previously the watchdog on pgpool-II node that
- needs to perform the node command (failover, failback or promote node) used to
- broadcast the failover command to all attached pgpool-II nodes. And this
- sometimes makes the synchronization issues, especially when the watchdog cluster
- contains a large number of nodes and consequently the failover command sometimes
- gets executed by more than one pgpool-II.
- </para>
- <para>
- Now with this commit all the node commands are forwarded to the
- master/coordinator watchdog, which in turn propagates to all standby nodes.
- Apart from above the commit also changes the failover command interlocking
- mechanism and now only the master/coordinator node can become the lock holder
- so the failover commands will only get executed on the master/coordinator node.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-10-27 [e07a6d3]
- -->
- <para>
- Adopt the incompatibility with psql of PostgreSQL 9.6. (Tatsuo Ishii)
- </para>
- <para>
- Since -c option does not imply -X anymore in 9.6, regression fails if
- <filename>.psqlrc</filename> is set, for example "\pset
- pager" is set.
- </para>
- </listitem>
-
<listitem>
<!--
2016-10-27 [f37c592]
</para>
</listitem>
- <listitem>
- <!--
- 2016-10-27 [c9e203d]
- -->
- <para>
- Remove obsoleted option "-c" in pgpool command. (Tatsuo Ishii)
- </para>
- <para>
- Also fix typo in the help message.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-10-18 [8da0e7f]
- -->
- <para>
- Fix for 0000252: authentication failed error when PCP command is cancelled... (Muhammad Usama)
- </para>
- <para>
- Fixed by adding the volatile modifier to authenticated flag, to make sure we
- always get the updated value after the long jump.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-24 [8aa7586]
- -->
- <para>
- Change the default value of search_primary_node_timeout from 10 to 300. (Tatsuo Ishii)
- </para>
- <para>
- Prior default value 10 seconds is sometimes too short for a standby to
- be promoted.
- </para>
- <para>
- Per [pgpool-general: 5026].
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-21 [b306e04]
- -->
- <para>
- Fix the case when all backends are down then 1 node attached. (Tatsuo Ishii)
- </para>
- <para>
- When all backends are down, no connection is accepted. Then 1
- PostgreSQL becomes up, and attach the node using pcp_attach_node. It
- successfully finishes. However, when a new connection arrives, still
- the connection is refused because pgpool child process looks into the
- cached status, in which the recovered node is still in down status if
- mode is streaming replication mode (native replication and other modes
- are fine). Solution is, if all nodes are down, force to restart all
- pgpool child.
- </para>
- <para>
- Per bug 248.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-20 [a38fa09]
- -->
- <para>
- Fix for: [pgpool-general: 4997] Avoiding downtime when pgpool changes require a restart (Muhammad Usama)
- </para>
- <para>
- To fix this, The verification mechanism of configuration parameter values is
- reversed, previously the standby nodes used to verify their parameter values
- against the respective values on the master pgpool-II node and when the
- inconsistency was found the FATAL error was thrown, now with this commit the
- verification responsibility is delegated to the master pgpool-II node.
- Now the master node will verify the configuration parameter values of each
- joining standby node against its local values and will produce
- a WARNING message instead of an error in case of a difference.
- This way the nodes having the different configurations will also be allowed to
- join the watchdog cluster and the user has to manually look out for the
- configuration inconsistency warnings in the master pgpool-II log to avoid the
- surprises at the time of pgpool-II master switch over.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-13 [1c99580]
- -->
- <para>
- Disable strict aliasing optimization. (Tatsuo Ishii)
- </para>
- <para>
- flatten_set_variable_args() was imported from PostgreSQL in Pgpool-II
- 3.5. To make the code work, a compiler flag "-fno-strict-aliasing" is
- necessary (PostgreSQL does so). Unfortunately when the function was
- imported, the compiler flag was not added. To fix this, configure.ac
- was modified.
- </para>
- <para>
- Per [pgpool-general: 4975].
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-09 [1ac4c8a]
- -->
- <para>
- Fixing an obvious logic mistake. (Muhammad Usama)
- </para>
- <para>
- per Coverity CID 1362580 and CID 1362581
-
- </para>
- </listitem>
-
<listitem>
<!--
2016-09-09 [8231f65]
store current time at the start up of Pgpool-II main process for later
use.
</para>
- <para>
- Per Coverity CID 1362583.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-09 [12812a1]
- -->
- <para>
- Remove useless assignment. (Tatsuo Ishii)
- </para>
- <para>
- Per coverity CID 1362589.
- </para>
</listitem>
<listitem>
<para>
Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)
</para>
- <para>
- While returning cached query result, sync message sent from frontend
- is discarded. This is harmless because "ready for query" messages is
- sent to frontend afterward. Problem is, AccessShareLock held by
- previous parse message processing is not released until sync message
- is received by the backend. Fix is, forwarding the sync message to
- backend and discarding "ready for query" message returned from
- backend.
- </para>
- <para>
- Per [pgpool-hackers: 1787].
- </para>
</listitem>
</itemizedlist>
<simpara>2016-12-26</simpara>
</note>
- <sect2>
- <title>Changes</title>
-
- <itemizedlist>
-
- <listitem>
- <!--
- 2016-12-20 [3b2e955]
- -->
- <para>
- Add 3.2.18 release note. (Tatsuo Ishii)
- </para>
- </listitem>
- </itemizedlist>
- </sect2>
-
<sect2>
<title>Bug fixes</title>
</para>
</listitem>
- <listitem>
- <!--
- 2016-12-20 [9274f82]
- -->
- <para>
- Fix packet kind does not match error in extended protocol per bug 231. (Tatsuo Ishii)
- </para>
- <para>
- According to the bug231, the bug seem to bite you if all of
- following conditions are met:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Streaming replication mode
- </para>
- </listitem>
- <listitem>
- <para>
- Load balance node is not node 0
- </para>
- </listitem>
- <listitem>
- <para>
- Extended protocol is used
- </para>
- </listitem>
- <listitem>
- <para>
- SELECT is executed, the statement is closed, then a
- transaction command is executed
- </para>
- </listitem>
- </itemizedlist>
- <para>
- The sequence of how the problem bites is:
- <orderedlist>
- <listitem>
- <para>
- SELECT executes on statement S1 on the load balance node 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend send Close statement
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend sends Parse, Bind, Execute of COMMIT
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 0 & 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend sends sync message
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 0 & 1
- </para>
- </listitem>
- <listitem>
- <para>
- Backend 0 replies back Parse complete ("1"), while
- backend 1 replies back close complete ("3") because of
- #3.
- </para>
- </listitem>
- <listitem>
- <para>
- Kind mismatch occurs
- </para>
- </listitem>
- </orderedlist>
-
- </para>
- <para>
- The solution is, in #3, let Pgpool-II wait for response from backend
- 1, but do not read the response message. Later on Pgpool-II's state
- machine will read the response from it before the sync message is sent
- in #6. With this, backend 1 will reply back "1" in #8, and the kind
- mismatch error does not occur.
- </para>
- <para>
- Also, fix not calling pool_set_doing_extended_query_message() when
- receives Close message. (I don't know why it was missed).
- </para>
- <para>
- New regression test "067.bug231" was added.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-12-06 [336e932]
- -->
- <para>
- Fix a race condition in a signal handler per bug 265. (Tatsuo Ishii)
- </para>
- <para>
- In child.c there's signal handler which calls elog. Since the signal
- handler is not blocked against other signals while processing, deadlock
- could occur in the system calls in the pgpool shutdown sequence. To
- fix the problem, now the signal handler is blocked by using
- POOL_SETMASK.
- </para>
- <para>
- Ideally we should avoid calling elog in signal handlers though.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-11-26 [045a59f]
- -->
- <para>
- Back porting the improved failover command propagation mechanism from Pgpool-II 3.6 (Muhammad Usama)
- </para>
- <para>
- Overhauling the design of how failover, failback and promote node commands are
- propagated to the watchdog nodes. Previously the watchdog on pgpool-II node that
- needs to perform the node command (failover, failback or promote node) used to
- broadcast the failover command to all attached pgpool-II nodes. And this
- sometimes makes the synchronization issues, especially when the watchdog cluster
- contains a large number of nodes and consequently the failover command sometimes
- gets executed by more than one pgpool-II.
- </para>
- <para>
- Now with this commit all the node commands are forwarded to the
- master/coordinator watchdog, which in turn propagates to all standby nodes.
- Apart from above the commit also changes the failover command interlocking
- mechanism and now only the master/coordinator node can become the lock holder
- so the failover commands will only get executed on the master/coordinator node.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-10-27 [e07a6d3]
- -->
- <para>
- Adopt the incompatibility with psql of PostgreSQL 9.6. (Tatsuo Ishii)
- </para>
- <para>
- Since -c option does not imply -X anymore in 9.6, regression fails if
- <filename>.psqlrc</filename> is set, for example "\pset
- pager" is set.
- </para>
- </listitem>
-
<listitem>
<!--
2016-10-27 [f37c592]
</para>
</listitem>
- <listitem>
- <!--
- 2016-10-27 [c9e203d]
- -->
- <para>
- Remove obsoleted option "-c" in pgpool command. (Tatsuo Ishii)
- </para>
- <para>
- Also fix typo in the help message.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-10-18 [8da0e7f]
- -->
- <para>
- Fix for 0000252: authentication failed error when PCP command is cancelled... (Muhammad Usama)
- </para>
- <para>
- Fixed by adding the volatile modifier to authenticated flag, to make sure we
- always get the updated value after the long jump.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-24 [8aa7586]
- -->
- <para>
- Change the default value of search_primary_node_timeout from 10 to 300. (Tatsuo Ishii)
- </para>
- <para>
- Prior default value 10 seconds is sometimes too short for a standby to
- be promoted.
- </para>
- <para>
- Per [pgpool-general: 5026].
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-21 [b306e04]
- -->
- <para>
- Fix the case when all backends are down then 1 node attached. (Tatsuo Ishii)
- </para>
- <para>
- When all backends are down, no connection is accepted. Then 1
- PostgreSQL becomes up, and attach the node using pcp_attach_node. It
- successfully finishes. However, when a new connection arrives, still
- the connection is refused because pgpool child process looks into the
- cached status, in which the recovered node is still in down status if
- mode is streaming replication mode (native replication and other modes
- are fine). Solution is, if all nodes are down, force to restart all
- pgpool child.
- </para>
- <para>
- Per bug 248.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-20 [a38fa09]
- -->
- <para>
- Fix for: [pgpool-general: 4997] Avoiding downtime when pgpool changes require a restart (Muhammad Usama)
- </para>
- <para>
- To fix this, The verification mechanism of configuration parameter values is
- reversed, previously the standby nodes used to verify their parameter values
- against the respective values on the master pgpool-II node and when the
- inconsistency was found the FATAL error was thrown, now with this commit the
- verification responsibility is delegated to the master pgpool-II node.
- Now the master node will verify the configuration parameter values of each
- joining standby node against its local values and will produce
- a WARNING message instead of an error in case of a difference.
- This way the nodes having the different configurations will also be allowed to
- join the watchdog cluster and the user has to manually look out for the
- configuration inconsistency warnings in the master pgpool-II log to avoid the
- surprises at the time of pgpool-II master switch over.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-13 [1c99580]
- -->
- <para>
- Disable strict aliasing optimization. (Tatsuo Ishii)
- </para>
- <para>
- flatten_set_variable_args() was imported from PostgreSQL in Pgpool-II
- 3.5. To make the code work, a compiler flag "-fno-strict-aliasing" is
- necessary (PostgreSQL does so). Unfortunately when the function was
- imported, the compiler flag was not added. To fix this, configure.ac
- was modified.
- </para>
- <para>
- Per [pgpool-general: 4975].
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-09 [1ac4c8a]
- -->
- <para>
- Fixing an obvious logic mistake. (Muhammad Usama)
- </para>
- <para>
- per Coverity CID 1362580 and CID 1362581
-
- </para>
- </listitem>
-
<listitem>
<!--
2016-09-09 [8231f65]
-->
<para>
- Do not use random() while generating MD5 salt. (Tatsuo Ishii)
+ Do not use <function>random()</function> while generating MD5 salt. (Tatsuo Ishii)
</para>
<para>
- random() should not be used in security related applications. To
- replace random(), import PostmasterRandom() from PostgreSQL. Also
- store current time at the start up of Pgpool-II main process for later
+ <function>random()</function> should not be used in security related applications. To
+ replace <function>random()</function>, import <function>PostmasterRandom()</function> from PostgreSQL. Also
+ store current time at the start up of <productname>Pgpool-II</productname> main process for later
use.
</para>
- <para>
- Per Coverity CID 1362583.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-09 [12812a1]
- -->
- <para>
- Remove useless assignment. (Tatsuo Ishii)
- </para>
- <para>
- Per coverity CID 1362589.
- </para>
</listitem>
<listitem>
<para>
Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)
</para>
- <para>
- While returning cached query result, sync message sent from frontend
- is discarded. This is harmless because "ready for query" messages is
- sent to frontend afterward. Problem is, AccessShareLock held by
- previous parse message processing is not released until sync message
- is received by the backend. Fix is, forwarding the sync message to
- backend and discarding "ready for query" message returned from
- backend.
- </para>
- <para>
- Per [pgpool-hackers: 1787].
- </para>
</listitem>
</itemizedlist>
<simpara>2016-12-26</simpara>
</note>
- <sect2>
- <title>Changes</title>
-
- <itemizedlist>
-
- <listitem>
- <!--
- 2016-12-20 [3b2e955]
- -->
- <para>
- Add 3.3.13 release note. (Tatsuo Ishii)
- </para>
- </listitem>
- </itemizedlist>
- </sect2>
-
<sect2>
<title>Bug fixes</title>
<listitem>
<!--
- 2016-12-20 [888ac16]
+ 2016-12-23 [a7e222d]
-->
<para>
- Fix occasional segfault when query cache is enabled. (Tatsuo Ishii)
- </para>
- <para>
- Per bug 263.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-12-20 [9274f82]
- -->
- <para>
- Fix packet kind does not match error in extended protocol per bug 231. (Tatsuo Ishii)
- </para>
- <para>
- According to the bug231, the bug seem to bite you if all of
- following conditions are met:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Streaming replication mode
- </para>
- </listitem>
- <listitem>
- <para>
- Load balance node is not node 0
- </para>
- </listitem>
- <listitem>
- <para>
- Extended protocol is used
- </para>
- </listitem>
- <listitem>
- <para>
- SELECT is executed, the statement is closed, then a
- transaction command is executed
- </para>
- </listitem>
- </itemizedlist>
- <para>
- The sequence of how the problem bites is:
- <orderedlist>
- <listitem>
- <para>
- SELECT executes on statement S1 on the load balance node 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend send Close statement
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend sends Parse, Bind, Execute of COMMIT
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 0 & 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend sends sync message
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 0 & 1
- </para>
- </listitem>
- <listitem>
- <para>
- Backend 0 replies back Parse complete ("1"), while
- backend 1 replies back close complete ("3") because of
- #3.
- </para>
- </listitem>
- <listitem>
- <para>
- Kind mismatch occurs
- </para>
- </listitem>
- </orderedlist>
-
- </para>
- <para>
- The solution is, in #3, let Pgpool-II wait for response from backend
- 1, but do not read the response message. Later on Pgpool-II's state
- machine will read the response from it before the sync message is sent
- in #6. With this, backend 1 will reply back "1" in #8, and the kind
- mismatch error does not occur.
- </para>
- <para>
- Also, fix not calling pool_set_doing_extended_query_message() when
- receives Close message. (I don't know why it was missed).
- </para>
- <para>
- New regression test "067.bug231" was added.
- </para>
- </listitem>
+ Tightening up the watchdog security. (Muhammad Usama)
+ </para>
- <listitem>
- <!--
- 2016-12-06 [336e932]
- -->
- <para>
- Fix a race condition in a signal handler per bug 265. (Tatsuo Ishii)
- </para>
- <para>
- In child.c there's signal handler which calls elog. Since the signal
- handler is not blocked against other signals while processing, deadlock
- could occur in the system calls in the pgpool shutdown sequence. To
- fix the problem, now the signal handler is blocked by using
- POOL_SETMASK.
- </para>
- <para>
- Ideally we should avoid calling elog in signal handlers though.
+ <para>
+ Now wd_authkey uses the HMAC SHA-256 hashing.
</para>
</listitem>
<listitem>
<!--
- 2016-11-26 [045a59f]
+ 2016-12-22 [1b293c4]
-->
<para>
- Back porting the improved failover command propagation mechanism from Pgpool-II 3.6 (Muhammad Usama)
- </para>
- <para>
- Overhauling the design of how failover, failback and promote node commands are
- propagated to the watchdog nodes. Previously the watchdog on pgpool-II node that
- needs to perform the node command (failover, failback or promote node) used to
- broadcast the failover command to all attached pgpool-II nodes. And this
- sometimes makes the synchronization issues, especially when the watchdog cluster
- contains a large number of nodes and consequently the failover command sometimes
- gets executed by more than one pgpool-II.
- </para>
- <para>
- Now with this commit all the node commands are forwarded to the
- master/coordinator watchdog, which in turn propagates to all standby nodes.
- Apart from above the commit also changes the failover command interlocking
- mechanism and now only the master/coordinator node can become the lock holder
- so the failover commands will only get executed on the master/coordinator node.
+ Add pgpool_adm extension in <productname>Pgpool-II</productname> RPM. (Bo Peng)
</para>
</listitem>
<listitem>
<!--
- 2016-10-27 [e07a6d3]
+ 2016-12-20 [888ac16]
-->
<para>
- Adopt the incompatibility with psql of PostgreSQL 9.6. (Tatsuo Ishii)
- </para>
- <para>
- Since -c option does not imply -X anymore in 9.6, regression fails if
- <filename>.psqlrc</filename> is set, for example "\pset
- pager" is set.
+ Fix occasional segfault when query cache is enabled. (bug 263) (Tatsuo Ishii)
</para>
</listitem>
</para>
</listitem>
- <listitem>
- <!--
- 2016-10-27 [c9e203d]
- -->
- <para>
- Remove obsoleted option "-c" in pgpool command. (Tatsuo Ishii)
- </para>
- <para>
- Also fix typo in the help message.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-10-18 [8da0e7f]
- -->
- <para>
- Fix for 0000252: authentication failed error when PCP command is cancelled... (Muhammad Usama)
- </para>
- <para>
- Fixed by adding the volatile modifier to authenticated flag, to make sure we
- always get the updated value after the long jump.
- </para>
- </listitem>
-
<listitem>
<!--
2016-09-24 [8aa7586]
2016-09-21 [b306e04]
-->
<para>
- Fix the case when all backends are down then 1 node attached. (Tatsuo Ishii)
+ Fix the case when all backends are down then 1 node attached. (bug 248) (Tatsuo Ishii)
</para>
<para>
When all backends are down, no connection is accepted. Then 1
are fine). Solution is, if all nodes are down, force to restart all
pgpool child.
</para>
- <para>
- Per bug 248.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-20 [a38fa09]
- -->
- <para>
- Fix for: [pgpool-general: 4997] Avoiding downtime when pgpool changes require a restart (Muhammad Usama)
- </para>
- <para>
- To fix this, The verification mechanism of configuration parameter values is
- reversed, previously the standby nodes used to verify their parameter values
- against the respective values on the master pgpool-II node and when the
- inconsistency was found the FATAL error was thrown, now with this commit the
- verification responsibility is delegated to the master pgpool-II node.
- Now the master node will verify the configuration parameter values of each
- joining standby node against its local values and will produce
- a WARNING message instead of an error in case of a difference.
- This way the nodes having the different configurations will also be allowed to
- join the watchdog cluster and the user has to manually look out for the
- configuration inconsistency warnings in the master pgpool-II log to avoid the
- surprises at the time of pgpool-II master switch over.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-13 [1c99580]
- -->
- <para>
- Disable strict aliasing optimization. (Tatsuo Ishii)
- </para>
- <para>
- flatten_set_variable_args() was imported from PostgreSQL in Pgpool-II
- 3.5. To make the code work, a compiler flag "-fno-strict-aliasing" is
- necessary (PostgreSQL does so). Unfortunately when the function was
- imported, the compiler flag was not added. To fix this, configure.ac
- was modified.
- </para>
- <para>
- Per [pgpool-general: 4975].
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-09 [1ac4c8a]
- -->
- <para>
- Fixing an obvious logic mistake. (Muhammad Usama)
- </para>
- <para>
- per Coverity CID 1362580 and CID 1362581
-
- </para>
</listitem>
<listitem>
store current time at the start up of Pgpool-II main process for later
use.
</para>
- <para>
- Per Coverity CID 1362583.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-09 [12812a1]
- -->
- <para>
- Remove useless assignment. (Tatsuo Ishii)
- </para>
- <para>
- Per coverity CID 1362589.
- </para>
</listitem>
<listitem>
<para>
Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)
</para>
- <para>
- While returning cached query result, sync message sent from frontend
- is discarded. This is harmless because "ready for query" messages is
- sent to frontend afterward. Problem is, AccessShareLock held by
- previous parse message processing is not released until sync message
- is received by the backend. Fix is, forwarding the sync message to
- backend and discarding "ready for query" message returned from
- backend.
- </para>
- <para>
- Per [pgpool-hackers: 1787].
- </para>
</listitem>
</itemizedlist>
<simpara>2016-12-26</simpara>
</note>
- <sect2>
- <title>Changes</title>
-
- <itemizedlist>
-
- <listitem>
- <!--
- 2016-12-20 [3b2e955]
- -->
- <para>
- Add 3.4.9 release note. (Tatsuo Ishii)
- </para>
- </listitem>
- </itemizedlist>
- </sect2>
-
<sect2>
<title>Bug fixes</title>
<listitem>
<!--
- 2016-12-20 [888ac16]
+ 2016-12-23 [f5e9a2a]
-->
<para>
- Fix occasional segfault when query cache is enabled. (Tatsuo Ishii)
- </para>
- <para>
- Per bug 263.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-12-20 [9274f82]
- -->
- <para>
- Fix packet kind does not match error in extended protocol per bug 231. (Tatsuo Ishii)
- </para>
- <para>
- According to the bug231, the bug seem to bite you if all of
- following conditions are met:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Streaming replication mode
- </para>
- </listitem>
- <listitem>
- <para>
- Load balance node is not node 0
- </para>
- </listitem>
- <listitem>
- <para>
- Extended protocol is used
- </para>
- </listitem>
- <listitem>
- <para>
- SELECT is executed, the statement is closed, then a
- transaction command is executed
- </para>
- </listitem>
- </itemizedlist>
- <para>
- The sequence of how the problem bites is:
- <orderedlist>
- <listitem>
- <para>
- SELECT executes on statement S1 on the load balance node 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend send Close statement
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend sends Parse, Bind, Execute of COMMIT
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 0 & 1
- </para>
- </listitem>
- <listitem>
- <para>
- Frontend sends sync message
- </para>
- </listitem>
- <listitem>
- <para>
- Pgool-II forward it to backend 0 & 1
- </para>
- </listitem>
- <listitem>
- <para>
- Backend 0 replies back Parse complete ("1"), while
- backend 1 replies back close complete ("3") because of
- #3.
- </para>
- </listitem>
- <listitem>
- <para>
- Kind mismatch occurs
- </para>
- </listitem>
- </orderedlist>
+ Tightening up the watchdog security. (Muhammad Usama)
+ </para>
- </para>
- <para>
- The solution is, in #3, let Pgpool-II wait for response from backend
- 1, but do not read the response message. Later on Pgpool-II's state
- machine will read the response from it before the sync message is sent
- in #6. With this, backend 1 will reply back "1" in #8, and the kind
- mismatch error does not occur.
- </para>
- <para>
- Also, fix not calling pool_set_doing_extended_query_message() when
- receives Close message. (I don't know why it was missed).
- </para>
- <para>
- New regression test "067.bug231" was added.
+ <para>
+ Now wd_authkey uses the HMAC SHA-256 hashing.
</para>
</listitem>
<listitem>
<!--
- 2016-12-06 [336e932]
+ 2016-12-22 [79f1ba8]
-->
<para>
- Fix a race condition in a signal handler per bug 265. (Tatsuo Ishii)
- </para>
- <para>
- In child.c there's signal handler which calls elog. Since the signal
- handler is not blocked against other signals while processing, deadlock
- could occur in the system calls in the pgpool shutdown sequence. To
- fix the problem, now the signal handler is blocked by using
- POOL_SETMASK.
- </para>
- <para>
- Ideally we should avoid calling elog in signal handlers though.
+ Add pgpool_adm extension in <productname>Pgpool-II</productname>RPM. (Bo Peng)
</para>
</listitem>
<listitem>
<!--
- 2016-11-26 [045a59f]
- -->
- <para>
- Back porting the improved failover command propagation mechanism from Pgpool-II 3.6 (Muhammad Usama)
- </para>
- <para>
- Overhauling the design of how failover, failback and promote node commands are
- propagated to the watchdog nodes. Previously the watchdog on pgpool-II node that
- needs to perform the node command (failover, failback or promote node) used to
- broadcast the failover command to all attached pgpool-II nodes. And this
- sometimes makes the synchronization issues, especially when the watchdog cluster
- contains a large number of nodes and consequently the failover command sometimes
- gets executed by more than one pgpool-II.
- </para>
- <para>
- Now with this commit all the node commands are forwarded to the
- master/coordinator watchdog, which in turn propagates to all standby nodes.
- Apart from above the commit also changes the failover command interlocking
- mechanism and now only the master/coordinator node can become the lock holder
- so the failover commands will only get executed on the master/coordinator node.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-10-27 [e07a6d3]
+ 2016-12-20 [888ac16]
-->
<para>
- Adopt the incompatibility with psql of PostgreSQL 9.6. (Tatsuo Ishii)
- </para>
- <para>
- Since -c option does not imply -X anymore in 9.6, regression fails if
- <filename>.psqlrc</filename> is set, for example "\pset
- pager" is set.
+ Fix occasional segfault when query cache is enabled. (bug 263) (Tatsuo Ishii)
</para>
</listitem>
</para>
</listitem>
- <listitem>
- <!--
- 2016-10-18 [8da0e7f]
- -->
- <para>
- Fix for 0000252: authentication failed error when PCP command is cancelled... (Muhammad Usama)
- </para>
- <para>
- Fixed by adding the volatile modifier to authenticated flag, to make sure we
- always get the updated value after the long jump.
- </para>
- </listitem>
-
<listitem>
<!--
2016-09-24 [8aa7586]
2016-09-21 [b306e04]
-->
<para>
- Fix the case when all backends are down then 1 node attached. (Tatsuo Ishii)
+ Fix the case when all backends are down then 1 node attached. (bug 248) (Tatsuo Ishii)
</para>
<para>
When all backends are down, no connection is accepted. Then 1
are fine). Solution is, if all nodes are down, force to restart all
pgpool child.
</para>
- <para>
- Per bug 248.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-20 [a38fa09]
- -->
- <para>
- Fix for: [pgpool-general: 4997] Avoiding downtime when pgpool changes require a restart (Muhammad Usama)
- </para>
- <para>
- To fix this, The verification mechanism of configuration parameter values is
- reversed, previously the standby nodes used to verify their parameter values
- against the respective values on the master pgpool-II node and when the
- inconsistency was found the FATAL error was thrown, now with this commit the
- verification responsibility is delegated to the master pgpool-II node.
- Now the master node will verify the configuration parameter values of each
- joining standby node against its local values and will produce
- a WARNING message instead of an error in case of a difference.
- This way the nodes having the different configurations will also be allowed to
- join the watchdog cluster and the user has to manually look out for the
- configuration inconsistency warnings in the master pgpool-II log to avoid the
- surprises at the time of pgpool-II master switch over.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-13 [1c99580]
- -->
- <para>
- Disable strict aliasing optimization. (Tatsuo Ishii)
- </para>
- <para>
- flatten_set_variable_args() was imported from PostgreSQL in Pgpool-II
- 3.5. To make the code work, a compiler flag "-fno-strict-aliasing" is
- necessary (PostgreSQL does so). Unfortunately when the function was
- imported, the compiler flag was not added. To fix this, configure.ac
- was modified.
- </para>
- <para>
- Per [pgpool-general: 4975].
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-09 [1ac4c8a]
- -->
- <para>
- Fixing an obvious logic mistake. (Muhammad Usama)
- </para>
- <para>
- per Coverity CID 1362580 and CID 1362581
-
- </para>
</listitem>
<listitem>
store current time at the start up of Pgpool-II main process for later
use.
</para>
- <para>
- Per Coverity CID 1362583.
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-09 [12812a1]
- -->
- <para>
- Remove useless assignment. (Tatsuo Ishii)
- </para>
- <para>
- Per coverity CID 1362589.
- </para>
</listitem>
<listitem>
<para>
Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)
</para>
- <para>
- While returning cached query result, sync message sent from frontend
- is discarded. This is harmless because "ready for query" messages is
- sent to frontend afterward. Problem is, AccessShareLock held by
- previous parse message processing is not released until sync message
- is received by the backend. Fix is, forwarding the sync message to
- backend and discarding "ready for query" message returned from
- backend.
- </para>
- <para>
- Per [pgpool-hackers: 1787].
- </para>
</listitem>
</itemizedlist>
</note>
<sect2>
- <title>Changes</title>
+ <title>Bug fixes</title>
<itemizedlist>
<listitem>
<!--
- 2016-12-20 [3b2e955]
+ 2016-12-23 [4124e5e]
-->
<para>
- Add 3.5.5 release note. (Tatsuo Ishii)
+ Tightening up the watchdog security. (Muhammad Usama)
+ </para>
+
+ <para>
+ Now wd_authkey uses the HMAC SHA-256 hashing.
</para>
</listitem>
- </itemizedlist>
- </sect2>
-
- <sect2>
- <title>Bug fixes</title>
-
- <itemizedlist>
<listitem>
<!--
- 2016-12-20 [888ac16]
+ 2016-12-22 [f8a157a]
-->
<para>
- Fix occasional segfault when query cache is enabled. (Tatsuo Ishii)
+ Add pgpool_adm extension in <productname>Pgpool-II</productname> RPM. (Bo Peng)
</para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-20 [888ac16]
+ -->
<para>
- Per bug 263.
+ Fix occasional segfault when query cache is enabled. (bug 263) (Tatsuo Ishii)
</para>
</listitem>
2016-12-20 [9274f82]
-->
<para>
- Fix packet kind does not match error in extended protocol per bug 231. (Tatsuo Ishii)
+ Fix packet kind does not match error in extended protocol. (bug 231) (Tatsuo Ishii)
</para>
<para>
According to the bug231, the bug seem to bite you if all of
</para>
</listitem>
- <listitem>
- <!--
- 2016-10-27 [e07a6d3]
- -->
- <para>
- Adopt the incompatibility with psql of PostgreSQL 9.6. (Tatsuo Ishii)
- </para>
- <para>
- Since -c option does not imply -X anymore in 9.6, regression fails if
- <filename>.psqlrc</filename> is set, for example "\pset
- pager" is set.
- </para>
- </listitem>
-
<listitem>
<!--
2016-10-27 [f37c592]
<para>
Fix for 0000252: authentication failed error when PCP command is cancelled... (Muhammad Usama)
</para>
- <para>
- Fixed by adding the volatile modifier to authenticated flag, to make sure we
- always get the updated value after the long jump.
- </para>
</listitem>
<listitem>
2016-09-13 [1c99580]
-->
<para>
- Disable strict aliasing optimization. (Tatsuo Ishii)
- </para>
- <para>
- flatten_set_variable_args() was imported from PostgreSQL in Pgpool-II
- 3.5. To make the code work, a compiler flag "-fno-strict-aliasing" is
- necessary (PostgreSQL does so). Unfortunately when the function was
- imported, the compiler flag was not added. To fix this, configure.ac
- was modified.
- </para>
- <para>
- Per [pgpool-general: 4975].
- </para>
- </listitem>
-
- <listitem>
- <!--
- 2016-09-09 [1ac4c8a]
- -->
- <para>
- Fixing an obvious logic mistake. (Muhammad Usama)
- </para>
- <para>
- per Coverity CID 1362580 and CID 1362581
-
+ Add compiler flag "-fno-strict-aliasing" in configure.ac to fix compiler error. (Tatsuo Ishii)
</para>
</listitem>
Do not use random() while generating MD5 salt. (Tatsuo Ishii)
</para>
<para>
- random() should not be used in security related applications. To
- replace random(), import PostmasterRandom() from PostgreSQL. Also
- store current time at the start up of Pgpool-II main process for later
- use.
+ <function>random()</function> should not be used in security related applications. To
+ replace <function>random()</function>, import <function>PostmasterRandom()</function> from PostgreSQL. Also
+ store current time at the start up of <productname>Pgpool-II</productname> main process for later
+ use.
</para>
- <para>
- Per Coverity CID 1362583.
- </para>
- </listitem>
- <listitem>
- <!--
- 2016-09-09 [12812a1]
- -->
- <para>
- Remove useless assignment. (Tatsuo Ishii)
- </para>
- <para>
- Per coverity CID 1362589.
- </para>
</listitem>
<listitem>
<para>
Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)
</para>
- <para>
- While returning cached query result, sync message sent from frontend
- is discarded. This is harmless because "ready for query" messages is
- sent to frontend afterward. Problem is, AccessShareLock held by
- previous parse message processing is not released until sync message
- is received by the backend. Fix is, forwarding the sync message to
- backend and discarding "ready for query" message returned from
- backend.
- </para>
- <para>
- Per [pgpool-hackers: 1787].
- </para>
</listitem>
</itemizedlist>
</note>
<sect2>
- <title>Changes</title>
+ <title>Bug fixes</title>
<itemizedlist>
<listitem>
<!--
- 2016-12-20 [3b2e955]
+ 2016-12-23 [4124e5e]
-->
<para>
- Add 3.6.1, 3.5.5 release note. (Tatsuo Ishii)
+ Tightening up the watchdog security. (Muhammad Usama)
+ </para>
+
+ <para>
+ Now wd_authkey uses the HMAC SHA-256 hashing.
</para>
</listitem>
- </itemizedlist>
- </sect2>
-
- <sect2>
- <title>Bug fixes</title>
-
- <itemizedlist>
<listitem>
<!--
- 2016-12-20 [888ac16]
+ 2016-12-22 [f8a157a]
-->
<para>
- Fix occasional segfault when query cache is enabled. (Tatsuo Ishii)
+ Add pgpool_adm extension in <productname>Pgpool-II</productname> RPM. (Bo Peng)
</para>
+ </listitem>
+
+ <listitem>
+ <!--
+ 2016-12-20 [888ac16]
+ -->
<para>
- Per bug 263.
+ Fix occasional segfault when query cache is enabled. (bug 263) (Tatsuo Ishii)
</para>
</listitem>
2016-12-20 [9274f82]
-->
<para>
- Fix packet kind does not match error in extended protocol per bug 231. (Tatsuo Ishii)
+ Fix packet kind does not match error in extended protocol. (bug 231) (Tatsuo Ishii)
</para>
<para>
According to the bug231, the bug seem to bite you if all of
2016-12-06 [336e932]
-->
<para>
- Fix a race condition in a signal handler per bug 265. (Tatsuo Ishii)
+ Fix a race condition in a signal handler. (bug 265) (Tatsuo Ishii)
</para>
<para>
In child.c there's signal handler which calls elog. Since the signal
2016-11-24 [cc452ad]
-->
<para>
- Fix wrong minimum configuration value for client_idle_limit_in_recovery. (Tatsuo Ishii)
- </para>
- <para>
- Per bug #264.
+ Fix wrong minimum configuration value for client_idle_limit_in_recovery. (bug 264) (Tatsuo Ishii)
</para>
</listitem>
</para>
</listitem>
- <listitem>
- <!--
- 2016-11-22 [99cf426]
- -->
- <para>
- Fix pgpool.spec to install sgml docs and man. (pengbo)
- </para>
- <para>
- In 3.6.0, SGML docs and man pages wre not installed in RPM.
- </para>
- </listitem>
-
</itemizedlist>
</sect2>
projects / pgpool2.git / commitdiff