| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(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:57:31 |
| Message-ID: | 092a1674-0415-f5b4-0d04-b2a18d03778b@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On 6/19/20 7:52 AM, David G. Johnston wrote:
> On Fri, Jun 19, 2020 at 6:58 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto: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.
Actually that is not entirely true, see my follow up post.
>
> You need to decide on one of the actual ways of supplying a password, or
> choose an alternative authentication method like peer.
>
> David J.
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pepe TD Vo | 2020-06-19 15:07:35 | Re: create batch script to import into postgres tables |
| Previous Message | David G. Johnston | 2020-06-19 14:57:03 | Re: create batch script to import into postgres tables |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pepe TD Vo | 2020-06-19 15:07:35 | Re: create batch script to import into postgres tables |
| Previous Message | David G. Johnston | 2020-06-19 14:57:03 | Re: create batch script to import into postgres tables |