From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | mbork(at)mbork(dot)pl |
Cc: | Dominique Devienne <ddevienne(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: What are best practices wrt passwords? |
Date: | 2024-10-16 16:33:01 |
Message-ID: | Zw_qvUHTC98XcGa6@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Oct 16, 2024 at 06:16:57PM +0200, mbork(at)mbork(dot)pl wrote:
> On 2024-10-16, at 14:41, Dominique Devienne <ddevienne(at)gmail(dot)com> wrote:
>
> > On Wed, Oct 16, 2024 at 2:25 PM <mbork(at)mbork(dot)pl> wrote:
> >> I'd like to be able to use psql without typing passwords again and
> >> again. I know about `.pgpass` and PGPASSFILE, but I specifically do not
> >> want to use it - I have the password in the `.env` file, and having it
> >> in _two_ places comes with its own set of problems, like how to make
> >> sure they don't get out of sync.
> >
> > What's wrong with PGPASSWORD?
> > https://www.postgresql.org/docs/current/libpq-envars.html
>
> `ps auxe` shows all processes with their environments, no?
I think that only shows for super-user.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
When a patient asks the doctor, "Am I going to die?", he means
"Am I going to die soon?"
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-10-16 16:40:59 | Re: how to know if the sql will run a seq scan |
Previous Message | mbork | 2024-10-16 16:16:57 | Re: What are best practices wrt passwords? |