[pgpool-hackers: 4591] Re: If reading password from .pcppass file fails, try to read it from prompt.
Bo Peng
pengbo at sraoss.co.jp
Thu May 8 10:33:41 JST 2025
Ishii-san, thank you for your comment.
I will commit this patch to the master branch.
---
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS K.K.
TEL: 03-5979-2701 FAX: 03-5979-2702
URL: https://www.sraoss.co.jp/
________________________________________
差出人: Tatsuo Ishii <ishii at postgresql.org>
送信日時: 2025年5月8日 10:11
宛先: Bo Peng
CC: pgpool-hackers at pgpool.net
件名: Re: [pgpool-hackers: 4589] If reading password from .pcppass file fails, try to read it from prompt.
> Currently, if password cannot be retrieved from .pcppass file, pcp command fails with the following messages:
>
> FATAL: authentication failed for user "<username>"
> DETAIL: username and/or password does not match
>
> If reading the password from the .pcppass file fails, it should fall back to prompting the user for input, similar to how PostgreSQL handles .pgpass.
>
> Patch is attached.
> This patch also changes the following messages to be displayed without requiring the --debug option:
>
> WARNING: password file \"%s\" is not a plain file
> WARNING: password file \"%s\" has group or world access; permissions should be u=rw (0600) or less
>
> Any comments?
I think it's a good idea. I agree behaving similar to PostgreSQL is
always good, since that brings less confusion to PostgreSQL users.
Patch looks good to me.
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
More information about the pgpool-hackers
mailing list