<div dir="ltr"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><span><div>Hi, </div><div>I have recently upgraded to using pgpool 3.7.0 on Alpine 3.7 and I noticed that the pool_hba.conf is not acting the way it did when I was using pgpool 3.5.3. Previously, in 3.5.3 the hba conf files between pgpool and postgres were required to match on the authentication type e.g. both in trust or both in md5 mode but not mixed.</div><div><br></div><div>This seems to have changed in v3.7.0. I'm now able to have the pool_hba.conf set to trust and not maintaining the pool_passwd file while still forcing authentication at the database level with its pg_hba.conf using md5. Is this the expected behavior now? I personally prefer this setup but would like to make sure I don't have a bad build or something is wrong. </div><div><br></div><div>Thanks,</div><div>Peter </div></span></div></div></div></div></div></div>
</div>
<br>
<p style="margin:0px 0in;font-size:12pt;font-family:"Times New Roman",serif;color:rgb(34,34,34);background-color:rgb(255,255,255)"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(102,102,102)">The information contained in this email message is PRIVATE and intended only for the personal and confidential use of the recipient named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by email, and delete the original message.</span></p>