[Pgpool-hackers] make_persistent_db_connection: s_do_auth failed
Tatsuo Ishii
ishii at sraoss.co.jp
Sun Aug 7 09:56:41 UTC 2011
Done.
I have added sr_check_period, sr_check_user and sr_check_password. I
have not nadded sr_check_database though. We currently do not have
health_check_database. If we add sr_check_database, we need to add
health_check_database. So I leave it as it is.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
> I will do it this week end. My idea is:
>
> 1) Add new directive for replication delay checking and
> primary/standby detection in streaming replication.
>
> 2) Thy are:
> sr_check_user
> sr_check_password
> sr_check_database
>
> Currently, sr_check_user == health_check_user, sr_check_password = '',
> sr_check_database = 'postgres'.
>
> So the new directives allow you to specify those parameters. I'm
> not sure if we need sr_check_database, though.
>
> Comments, suggestions, objections?
>
>> And I also have a question about this. Is it necessary to per-node
>> setting for this?
>
> What do you mean by per-node? Do you want to have different
> user/password combo per node?
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese: http://www.sraoss.co.jp
> _______________________________________________
> Pgpool-hackers mailing list
> Pgpool-hackers at pgfoundry.org
> http://pgfoundry.org/mailman/listinfo/pgpool-hackers
More information about the Pgpool-hackers
mailing list