<div dir="ltr">Thanks. We are willing to help test, so please keep us updated.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 18, 2015 at 8:32 AM, Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@postgresql.org" target="_blank">ishii@postgresql.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">> Hello,<br>
><br>
> I am working on running pgpool on heroku. Has anyone tried this before?<br>
><br>
> What I am finding out is that I need to be able to configure the username,<br>
> password, and database name per backend.<br>
><br>
> The following features are requested<br>
><br>
> 1) Ability to configure the database name that the health check connection<br>
> connects to. Currently it can be toggled between "template1" and<br>
> "postgres". Though in enviornments where we don't have control (e.g.,<br>
> heroku) we need to be able to configure the database name.<br>
><br>
> 2) Ability to configure username, password, and database name per backend<br>
> for the health check. In enviornments where we don't have control (e.g.,<br>
> heroku) we need to be able to configure the database name.<br>
<br>
</div></div>These are definitely interesting requests. I'm looking forward to add<br>
a knob to control them in pgpool-II 3.5 which is supposed to be<br>
released this fall.<br>
<br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" rel="noreferrer" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" rel="noreferrer" target="_blank">http://www.sraoss.co.jp</a><br>
</blockquote></div><br></div>