| From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Requiring pass and database psql shell command |
| Date: | 2018-03-05 14:23:12 |
| Message-ID: | c8afb0cf-c65b-beef-cff8-28a42a23f548@cox.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
The password file is also a solution.
https://www.postgresql.org/docs/current/static/libpq-pgpass.html
On 03/05/2018 07:33 AM, James Keener wrote:
> Well, it's not a problem, it's the way it's designed and it's a sensible
> design. Check https://www.postgresql.org/docs/9.3/static/libpq-envars.html
> for more info on doing what you want.
>
> On March 5, 2018 7:55:46 AM EST, "Łukasz Jarych" <jaryszek(at)gmail(dot)com> wrote:
>
> Hi Guys,
>
> do you have also problem that every time you have to log into your
> database using shell and psql?
>
> I have to write over and over localhost, username, password...how to
> force shell to remember this?
>
> Best,
> Jacek
>
>
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roger Sunny | 2018-03-05 14:23:30 | 回复: pg_upgrade fails to restore function |
| Previous Message | Pavel Luzanov | 2018-03-05 14:22:02 | Re: psql variables in the DO command |