On Sun, 4 Sep 2016, Adrian Klaver wrote:
> Well first, if you are going to use trust as your auth method then specifying
> a password is moot exercise.
I tried adding an explicit password to ~/.pgpass with md5 as the auth
method, but that didn't work so I went back to trust. That's served well for
19 years. :-)
> Second, not sure where you are in the process, but any time you change the
> pg_hba.conf file you will need to give Postgres a reload signal to get it
> to recognize the changes. Again not sure how you are signalling Postgres
> but if you are using pg_ctl
> https://www.postgresql.org/docs/9.5/static/app-pg-ctl.html
> then something like:
>
> pg_ctl reload -D path_to_your_datadir
>
> as OS user postgres.
Good to know. I use pg_ctl stop and start with the path on both command
lines.
> Third, .pgpass should hold information that already exists in the database
> system tables. It is not a mechanism for entering that information into
> the database. So yes, you will need to use ALTER ROLE to create the
> password inside Postgres.
OK. I'll try that for the learning experience.
So much to learn and so little time ...
Thanks,
Rich