<para>
ๆดใซใ้ๅฎณใใผใใจใฏ้ใใ<productname>Pgpool-II</productname>ใฏ้้ขใใใใใผใใซๅฏพใใฆใฏใใซในใใงใใฏใๅฎ่กใ็ถใใพใใ
้้ขใใใใใผใใๅฐ้ๅฏ่ฝใซใชใๆฌก็ฌฌใใใฎใใผใใฏ่ชๅ็ใซๅๅบฆใขใฟใใใใใพใใ
+ ใใใฏ<productname>Pgpool-II </productname><emphasis>V4.1</emphasis>ไปฅ้ใซใฎใฟ้ฉ็จใใใใใจใซๆณจๆใใฆใใ ใใใ
+ ใใไปฅๅใฎใใผใธใงใณใใไฝฟใใฎๅ ดๅใฏใ้้ขใใใใใผใใซๅฏพใใๆฅ็ถๆงใฎๅ้กใ่งฃๆฑบใใใใใ<xref linkend="pcp-attach-node">ใไฝฟใฃใฆใใฎใใผใใๅพฉๅธฐใใใใชใใใฐใชใใพใใใ
</para>
<para>
any usable master backend node.
</para>
<para>
- Moreover, unlike for the failed
- nodes, <productname>Pgpool-II</productname> keeps the
- health-check running on the quarantined nodes and as soon as
- the quarantined node becomes reachable again it gets
- automatically re-attached.
+ Moreover, unlike for the failed nodes,
+ <productname>Pgpool-II</productname> keeps the health-check
+ running on the quarantined nodes and as soon as the quarantined
+ node becomes reachable again it gets automatically
+ re-attached. Note that this is only applied to
+ <productname>Pgpool-II </productname><emphasis>V4.1</emphasis>
+ or greater. If you are using previous versions you need to
+ re-attach the quarantined node by using <xref
+ linkend="pcp-attach-node"> when the connectivity issue is
+ solved.
</para>
<para>
From <productname>Pgpool-II </productname><emphasis>V4.1</emphasis> onwards, if the watchdog-master node