Re: create batch script to import into postgres tables

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Pepe TD Vo <pepevo(at)yahoo(dot)com>, cgerard999(at)gmail(dot)com, Christopher Browne <cbbrowne(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)postgresql(dot)org>, Pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: create batch script to import into postgres tables
Date: 2020-06-19 14:52:54
Message-ID: CAKFQuwbhVtbSi4r5e5KJBOFODJs3UVcaqggx97A7xDxpmwB8xA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

On Fri, Jun 19, 2020 at 6:58 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:

> On 6/19/20 6:53 AM, Pepe TD Vo wrote:
> > Thank you sir and I am sorry for the typo not having "--" on password.
> > I did spelling out with --password=mypassword
>
> Please go back and read my post again.
>

To be clear, there is no way to supply a password as a command line
argument. It is fundamentally a bad idea and we don't even make it an
option.

You need to decide on one of the actual ways of supplying a password, or
choose an alternative authentication method like peer.

David J.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message David G. Johnston 2020-06-19 14:57:03 Re: create batch script to import into postgres tables
Previous Message jim schmidt 2020-06-19 14:37:54 Re: Deleting more efficiently from large partitions

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2020-06-19 14:57:03 Re: create batch script to import into postgres tables
Previous Message Adrian Klaver 2020-06-19 14:33:27 Re: create batch script to import into postgres tables