MIME-Version: 1.0
References: 
 <CAEy4EGV7+UEkDmn4CmO3hcTXnbZYXqkk5tXqDYORs8oPAyqFGw@mail.gmail.com>
 <TYWP286MB26336ABAF0DDD2A7DE072652F26BA@TYWP286MB2633.JPNP286.PROD.OUTLOOK.COM>
In-Reply-To: 
 <TYWP286MB26336ABAF0DDD2A7DE072652F26BA@TYWP286MB2633.JPNP286.PROD.OUTLOOK.COM>
From: zam bak <zam6ak@gmail.com>
Date: Fri, 20 Feb 2026 19:23:32 -0500
Message-ID: 
 <CAEy4EGWaBY-baKq3GBL+NFt7rVG_eFr9rZP00v5JG3ox6AfFtg@mail.gmail.com>
Subject: Re: pg_enc --input-file ability to read from stdin
To: Bo Peng <pengbo@sraoss.co.jp>
Cc: "pgpool-general@lists.postgresql.org"
 <pgpool-general@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAEy4EGWaBY-baKq3GBL%2BNFt7rVG_eFr9rZP00v5JG3ox6AfFtg%40mail.gmail.com>
Precedence: bulk

On Wed, Feb 18, 2026 at 9:21=E2=80=AFPM Bo Peng <pengbo@sraoss.co.jp> wrote=
:
>
> hi,
>
> > P.S.
> > Documentation also does not mention if colon ':' needs to be escaped
> > (and how) when password contains colon??
>
> As far as I understand, a colon ':' in the password does not need to be e=
scaped.
> Could you clarify what kind of case you are referring to?

For the case where credentials are being read in from the file,
documentation states that the format should be

    username1:secretpassword1
    username2:secretpassword2


So I was wondering if the colon - if it is a part of the password has
to be escaped (because its also a separator between the username and
the password)
I did try this, for example:

    username1:secret:password1
    username2:secret:password2

...and it seems to work fine - is this expected? no escaping is needed?


>
> ________________________________________
> =E5=B7=AE=E5=87=BA=E4=BA=BA: zam bak <zam6ak@gmail.com>
> =E9=80=81=E4=BF=A1: 2026 =E5=B9=B4 2 =E6=9C=88 18 =E6=97=A5 (=E6=B0=B4=E6=
=9B=9C=E6=97=A5) 1:36
> =E5=AE=9B=E5=85=88: pgpool-general@lists.postgresql.org <pgpool-general@l=
ists.postgresql.org>
> =E4=BB=B6=E5=90=8D: pg_enc --input-file ability to read from stdin
>
>
> Hello
>
> Is it possible to pipe stdin output to pg_end --input-file option by
> using dash '-' as a placeholder for stdin?
> https://www.pgpool.net/docs/latest/en/html/pg-enc.html
>
> I tried both "echo" and "cat" and am not able to do it.
>
> Example 1:
> cat <<'EOF' | pg_enc --update-pass --key-file
> /etc/pgpool-II/.pgpoolkey --config-file /etc/pgpool-II/pgpool.conf
> --input-file -
> username1:secretpassword1
> username2:secretpassword2
> EOF
> trying to read key from file /etc/pgpool-II/.pgpoolkey
> trying to read username:password pairs from file -
> failed to open input_file "-" (No such file or directory)
>
> Example 2:
> echo '
> username1:secretpassword1
> username2:secretpassword2
> ' | pg_enc --update-pass --key-file /etc/pgpool-II/.pgpoolkey
> --config-file /etc/pgpool-II/pgpool.conf --input-file -
> trying to read key from file /etc/pgpool-II/.pgpoolkey
> trying to read username:password pairs from file -
> failed to open input_file "-" (No such file or directory)
>
>
> The reason for asking about this is:
> *  to be able to use pg_enc in scripting setups
> * to be able to provide list of usernames/passwords without having to
> actually create a file
> * to be able to reduce escaping when autogenerated passwords contain
> special characters (by echoing literals)
>
>
> P.S.
> Documentation also does not mention if colon ':' needs to be escaped
> (and how) when password contains colon??
>
>
>
> Thanks
> Z...
>
>
>
>