Re: create batch script to import into postgres tables

[Pepe TD Vo <pepevo@xxxxxxxxx>]

appreciate for clarification, all inputs and teaching me more in PostgreSQL

have a good weekend and happy father's day to all who is Father.

v/r, 

Bach-Nga

No one in this world is pure and perfect.  If you avoid people for their mistakes you will be alone. So judge less, love, and forgive more.

To call him a dog hardly seems to do him justice though in as much as he had four legs, a tail, and barked, I admit he was, to all outward appearances. But to those who knew him well, he was a perfect gentleman (Hermione Gingold)

**Live simply **Love generously **Care deeply **Speak kindly.

*** Genuinely rich *** Faithful talent *** Sharing success

On Friday, June 19, 2020, 10:57:59 AM EDT, Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote:

On 6/19/20 7:52 AM, David G. Johnston wrote:
> On Fri, Jun 19, 2020 at 6:58 AM Adrian Klaver <adrian.klaver@xxxxxxxxxxx
> <mailto:adrian.klaver@xxxxxxxxxxx>> 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.klaver@xxxxxxxxxxx