Thread: Re: create batch script to import into postgres tables

Re: create batch script to import into postgres tables

From

Christopher Browne

Date:

16 June 2020, 15:16:50

On Tue, 16 Jun 2020 at 10:59, Pepe TD Vo <pepevo@yahoo.com> wrote:

I can run \copy in Linux with individual csv file into the table fine and run import using pgadmin into AWS instance. I am trying to run \copy all csv files import into its own table in Linux and in AWS instance. If all csv files into one table is fine but each csv for each table. Should I create one batch job for each imported table? If each batch file import csv to its table would be fine via \copy table_name(col1, col2, ... coln) from '/path/tablename.csv' delimiter ',' csv header; right?

There is no single straightforward answer to that.

Supposing I want a batch to either all be processed, or to all not process, then I might write a sql file like:

begin;

\copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;

\copy table_2 (c1, c2, c3) from '/path/tabledata2.csv' csv header;

\copy table_3 (c1, c2, c3) from '/path/tabledata3.csv' csv header;

commit;

But you may be fine with having a separate SQL script for each table.

There will be conditions where one or the other is more appropriate, and that will be based on the requirements of the process.

Also, the problem is I can't pull/execute psql from window client to pull the psql in aws instance and don't know how to create the batch script for this run. I tried simple \copy pull from c:\tes.csv and psql is unknown.

You cannot run psql without having it installed; there is a Windows installer for PostgreSQL, so you could use that to get it installed.

Hopefully there is an installer that will just install PostgreSQL client software (like psql, pg_dump, and notably *not* the database server software); I don't use WIndows, so I am not too familiar with that.

When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

16 June 2020, 15:42:18

Yes, I do have putty installed but can't connect to the aws postgres instance. Only work for oracle instance. Only connect postgres instance using pgadmin.

follow the url and the login prompt for username and hung there.

thank you.

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 Tuesday, June 16, 2020, 11:17:21 AM EDT, Christopher Browne <cbbrowne@gmail.com> wrote:

On Tue, 16 Jun 2020 at 10:59, Pepe TD Vo <pepevo@yahoo.com> wrote:

I can run \copy in Linux with individual csv file into the table fine and run import using pgadmin into AWS instance. I am trying to run \copy all csv files import into its own table in Linux and in AWS instance. If all csv files into one table is fine but each csv for each table. Should I create one batch job for each imported table? If each batch file import csv to its table would be fine via \copy table_name(col1, col2, ... coln) from '/path/tablename.csv' delimiter ',' csv header; right?

There is no single straightforward answer to that.

Supposing I want a batch to either all be processed, or to all not process, then I might write a sql file like:

begin;

\copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;

\copy table_2 (c1, c2, c3) from '/path/tabledata2.csv' csv header;

\copy table_3 (c1, c2, c3) from '/path/tabledata3.csv' csv header;

commit;

But you may be fine with having a separate SQL script for each table.

There will be conditions where one or the other is more appropriate, and that will be based on the requirements of the process.

Also, the problem is I can't pull/execute psql from window client to pull the psql in aws instance and don't know how to create the batch script for this run. I tried simple \copy pull from c:\tes.csv and psql is unknown.

You cannot run psql without having it installed; there is a Windows installer for PostgreSQL, so you could use that to get it installed.

When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

18 June 2020, 15:20:07

I have a Postgresql client installed and connected. how can i create a batch script running from the client window?

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.

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

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

On Tuesday, June 16, 2020, 11:42:40 AM EDT, Pepe TD Vo <pepevo@yahoo.com> wrote:

Yes, I do have putty installed but can't connect to the aws postgres instance. Only work for oracle instance. Only connect postgres instance using pgadmin.

follow the url and the login prompt for username and hung there.

thank you.

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.

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

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

On Tuesday, June 16, 2020, 11:17:21 AM EDT, Christopher Browne <cbbrowne@gmail.com> wrote:

On Tue, 16 Jun 2020 at 10:59, Pepe TD Vo <pepevo@yahoo.com> wrote:

I can run \copy in Linux with individual csv file into the table fine and run import using pgadmin into AWS instance. I am trying to run \copy all csv files import into its own table in Linux and in AWS instance. If all csv files into one table is fine but each csv for each table. Should I create one batch job for each imported table? If each batch file import csv to its table would be fine via \copy table_name(col1, col2, ... coln) from '/path/tablename.csv' delimiter ',' csv header; right?

There is no single straightforward answer to that.

Supposing I want a batch to either all be processed, or to all not process, then I might write a sql file like:

begin;

\copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;

\copy table_2 (c1, c2, c3) from '/path/tabledata2.csv' csv header;

\copy table_3 (c1, c2, c3) from '/path/tabledata3.csv' csv header;

commit;

But you may be fine with having a separate SQL script for each table.

There will be conditions where one or the other is more appropriate, and that will be based on the requirements of the process.

Also, the problem is I can't pull/execute psql from window client to pull the psql in aws instance and don't know how to create the batch script for this run. I tried simple \copy pull from c:\tes.csv and psql is unknown.

You cannot run psql without having it installed; there is a Windows installer for PostgreSQL, so you could use that to get it installed.

When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

18 June 2020, 15:20:07

I have a Postgresql client installed and connected. how can i create a batch script running from the client window?

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.

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

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

On Tuesday, June 16, 2020, 11:42:40 AM EDT, Pepe TD Vo <pepevo@yahoo.com> wrote:

Yes, I do have putty installed but can't connect to the aws postgres instance. Only work for oracle instance. Only connect postgres instance using pgadmin.

follow the url and the login prompt for username and hung there.

thank you.

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.

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

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

On Tuesday, June 16, 2020, 11:17:21 AM EDT, Christopher Browne <cbbrowne@gmail.com> wrote:

On Tue, 16 Jun 2020 at 10:59, Pepe TD Vo <pepevo@yahoo.com> wrote:

I can run \copy in Linux with individual csv file into the table fine and run import using pgadmin into AWS instance. I am trying to run \copy all csv files import into its own table in Linux and in AWS instance. If all csv files into one table is fine but each csv for each table. Should I create one batch job for each imported table? If each batch file import csv to its table would be fine via \copy table_name(col1, col2, ... coln) from '/path/tablename.csv' delimiter ',' csv header; right?

There is no single straightforward answer to that.

Supposing I want a batch to either all be processed, or to all not process, then I might write a sql file like:

begin;

\copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;

\copy table_2 (c1, c2, c3) from '/path/tabledata2.csv' csv header;

\copy table_3 (c1, c2, c3) from '/path/tabledata3.csv' csv header;

commit;

But you may be fine with having a separate SQL script for each table.

There will be conditions where one or the other is more appropriate, and that will be based on the requirements of the process.

Also, the problem is I can't pull/execute psql from window client to pull the psql in aws instance and don't know how to create the batch script for this run. I tried simple \copy pull from c:\tes.csv and psql is unknown.

You cannot run psql without having it installed; there is a Windows installer for PostgreSQL, so you could use that to get it installed.

When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

18 June 2020, 16:08:23

On 6/18/20 8:20 AM, Pepe TD Vo wrote:

Please don't top post. The preferred style on this list is inline or 
bottom posting(https://en.wikipedia.org/wiki/Posting_style).

> I have a Postgresql client installed and connected.  how can i create a 
> batch script running from the client window?

Create a file with commands in it like the example from Christopher 
Browne that was posted earlier:

"There is no single straightforward answer to that.

Supposing I want a batch to either all be processed, or to all not process,
then I might write a sql file like:

begin;
\copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;
\copy table_2 (c1, c2, c3) from '/path/tabledata2.csv' csv header;
\copy table_3 (c1, c2, c3) from '/path/tabledata3.csv' csv header;
commit;

But you may be fine with having a separate SQL script for each table.

There will be conditions where one or the other is more appropriate, and
that will be based on the requirements of the process."

Then point psql at it:

psql -d some_db -h some_host -U some_user -f the_file

Be aware that \copy is all or nothing. If there is a single failure in 
the copying the whole copy will rollback. Given that the one file per 
table might be preferable.

> 
> **
> *Bach-Nga
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

18 June 2020, 16:08:23

On 6/18/20 8:20 AM, Pepe TD Vo wrote:

Please don't top post. The preferred style on this list is inline or 
bottom posting(https://en.wikipedia.org/wiki/Posting_style).

> I have a Postgresql client installed and connected.  how can i create a 
> batch script running from the client window?

Create a file with commands in it like the example from Christopher 
Browne that was posted earlier:

"There is no single straightforward answer to that.

Supposing I want a batch to either all be processed, or to all not process,
then I might write a sql file like:

begin;
\copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;
\copy table_2 (c1, c2, c3) from '/path/tabledata2.csv' csv header;
\copy table_3 (c1, c2, c3) from '/path/tabledata3.csv' csv header;
commit;

But you may be fine with having a separate SQL script for each table.

There will be conditions where one or the other is more appropriate, and
that will be based on the requirements of the process."

Then point psql at it:

psql -d some_db -h some_host -U some_user -f the_file

Be aware that \copy is all or nothing. If there is a single failure in 
the copying the whole copy will rollback. Given that the one file per 
table might be preferable.

> 
> **
> *Bach-Nga
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

18 June 2020, 16:40:00

I get this part that separates SQL script for import each table,

(import.sql)

begin;
\copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;
commit;

but when open the psql sql shell script it prompts line by line for localhost, port, db, user, and password. If I set up a script and let it run it won't connect to the postgresql instance. I want to know how to execute a batch script connect to the database/instance.

In oracle I created a shell script with all oracle_sid, oracle_home, and read the function/procedure... for psql, especially from window client, I did put psql_home and connect to the instance, it failed

c:\Progra~1\PostgreSQL\11\bin\psql -d PSCIDR -h localhost -p 5432 -U postgres -i import.sql

even I do a simple count

c:\Progra~1\PostgreSQL\11\bin\psql -d PSCIDR -h localhost -p 5432 -U postgres -c "select count(*) from tableA";

none of them is work. Try to learn how to execute its script.

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.

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

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

On Thursday, June 18, 2020, 12:08:44 PM EDT, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

On 6/18/20 8:20 AM, Pepe TD Vo wrote:

Please don't top post. The preferred style on this list is inline or
bottom posting(https://en.wikipedia.org/wiki/Posting_style).

> I have a Postgresql client installed and connected. how can i create a
> batch script running from the client window?

Create a file with commands in it like the example from Christopher
Browne that was posted earlier:

"There is no single straightforward answer to that.

Supposing I want a batch to either all be processed, or to all not process,
then I might write a sql file like:

begin;
\copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;
\copy table_2 (c1, c2, c3) from '/path/tabledata2.csv' csv header;
\copy table_3 (c1, c2, c3) from '/path/tabledata3.csv' csv header;
commit;

But you may be fine with having a separate SQL script for each table.

There will be conditions where one or the other is more appropriate, and
that will be based on the requirements of the process."

Then point psql at it:

psql -d some_db -h some_host -U some_user -f the_file

Be aware that \copy is all or nothing. If there is a single failure in
the copying the whole copy will rollback. Given that the one file per
table might be preferable.

>
> **
> *Bach-Nga

>

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

18 June 2020, 16:40:00

I get this part that separates SQL script for import each table,

(import.sql)

begin;
\copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;
commit;

c:\Progra~1\PostgreSQL\11\bin\psql -d PSCIDR -h localhost -p 5432 -U postgres -i import.sql

even I do a simple count

c:\Progra~1\PostgreSQL\11\bin\psql -d PSCIDR -h localhost -p 5432 -U postgres -c "select count(*) from tableA";

none of them is work. Try to learn how to execute its script.

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.

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

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

On Thursday, June 18, 2020, 12:08:44 PM EDT, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

>
> **
> *Bach-Nga

>

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

18 June 2020, 19:06:18

On 6/18/20 9:40 AM, Pepe TD Vo wrote:
> I get this part that separates SQL script for import each table,
> 
> (import.sql)
> begin;
> \copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;
> commit;
> 
> but when open the psql sql shell script it prompts line by line for 
> localhost, port, db, user, and password.  If I set up a script and let 
> it run it won't connect to the postgresql instance.  I want to know how 
> to execute a batch script connect to the database/instance.
> In oracle I created a shell script with all oracle_sid, oracle_home, and 
> read the function/procedure... for psql, especially from window client, 
> I did put psql_home and connect to the instance, it failed
> 
> c:\Progra~1\PostgreSQL\11\bin\psql -d PSCIDR -h localhost -p 5432 -U 
> postgres -i import.sql

The above should be -f import.sql. AFAIK there is no -i for psql, so 
that should be failing.

> 
> even I do a simple count
> 
> c:\Progra~1\PostgreSQL\11\bin\psql -d PSCIDR -h localhost -p 5432 -U 
> postgres -c "select count(*) from tableA";

psql -d production  -U postgres -c 'select count(*) from cell_per';
Null display is "NULL".
  count
-------
     68
(1 row)

psql -d production  -U postgres -c 'select count(*) from cell_per'
Null display is "NULL".
  count
-------
     68

psql -d production  -U postgres -c 'select count(*) from cell_per;'
Null display is "NULL".
  count
-------
     68


> 
> none of them is work. Try to learn how to execute its script.

What error messages do you get?

> 
> **
> *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.EmojiEmojiEmoji
> 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 Thursday, June 18, 2020, 12:08:44 PM EDT, Adrian Klaver 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> On 6/18/20 8:20 AM, Pepe TD Vo wrote:
> 
> Please don't top post. The preferred style on this list is inline or
> bottom posting(https://en.wikipedia.org/wiki/Posting_style).
> 
>  > I have a Postgresql client installed and connected.  how can i create a
>  > batch script running from the client window?
> 
> Create a file with commands in it like the example from Christopher
> Browne that was posted earlier:
> 
> "There is no single straightforward answer to that.
> 
> 
> Supposing I want a batch to either all be processed, or to all not process,
> then I might write a sql file like:
> 
> 
> begin;
> \copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;
> \copy table_2 (c1, c2, c3) from '/path/tabledata2.csv' csv header;
> \copy table_3 (c1, c2, c3) from '/path/tabledata3.csv' csv header;
> commit;
> 
> 
> But you may be fine with having a separate SQL script for each table.
> 
> 
> There will be conditions where one or the other is more appropriate, and
> that will be based on the requirements of the process."
> 
> Then point psql at it:
> 
> psql -d some_db -h some_host -U some_user -f the_file
> 
> Be aware that \copy is all or nothing. If there is a single failure in
> the copying the whole copy will rollback. Given that the one file per
> table might be preferable.
> 
> 
>  >
>  > **
>  > *Bach-Nga
> 
>  >
> 
> 
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

18 June 2020, 19:06:18

On 6/18/20 9:40 AM, Pepe TD Vo wrote:
> I get this part that separates SQL script for import each table,
> 
> (import.sql)
> begin;
> \copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;
> commit;
> 
> but when open the psql sql shell script it prompts line by line for 
> localhost, port, db, user, and password.  If I set up a script and let 
> it run it won't connect to the postgresql instance.  I want to know how 
> to execute a batch script connect to the database/instance.
> In oracle I created a shell script with all oracle_sid, oracle_home, and 
> read the function/procedure... for psql, especially from window client, 
> I did put psql_home and connect to the instance, it failed
> 
> c:\Progra~1\PostgreSQL\11\bin\psql -d PSCIDR -h localhost -p 5432 -U 
> postgres -i import.sql

The above should be -f import.sql. AFAIK there is no -i for psql, so 
that should be failing.

> 
> even I do a simple count
> 
> c:\Progra~1\PostgreSQL\11\bin\psql -d PSCIDR -h localhost -p 5432 -U 
> postgres -c "select count(*) from tableA";

psql -d production  -U postgres -c 'select count(*) from cell_per';
Null display is "NULL".
  count
-------
     68
(1 row)

psql -d production  -U postgres -c 'select count(*) from cell_per'
Null display is "NULL".
  count
-------
     68

psql -d production  -U postgres -c 'select count(*) from cell_per;'
Null display is "NULL".
  count
-------
     68


> 
> none of them is work. Try to learn how to execute its script.

What error messages do you get?

> 
> **
> *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.EmojiEmojiEmoji
> 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 Thursday, June 18, 2020, 12:08:44 PM EDT, Adrian Klaver 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> On 6/18/20 8:20 AM, Pepe TD Vo wrote:
> 
> Please don't top post. The preferred style on this list is inline or
> bottom posting(https://en.wikipedia.org/wiki/Posting_style).
> 
>  > I have a Postgresql client installed and connected.  how can i create a
>  > batch script running from the client window?
> 
> Create a file with commands in it like the example from Christopher
> Browne that was posted earlier:
> 
> "There is no single straightforward answer to that.
> 
> 
> Supposing I want a batch to either all be processed, or to all not process,
> then I might write a sql file like:
> 
> 
> begin;
> \copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;
> \copy table_2 (c1, c2, c3) from '/path/tabledata2.csv' csv header;
> \copy table_3 (c1, c2, c3) from '/path/tabledata3.csv' csv header;
> commit;
> 
> 
> But you may be fine with having a separate SQL script for each table.
> 
> 
> There will be conditions where one or the other is more appropriate, and
> that will be based on the requirements of the process."
> 
> Then point psql at it:
> 
> psql -d some_db -h some_host -U some_user -f the_file
> 
> Be aware that \copy is all or nothing. If there is a single failure in
> the copying the whole copy will rollback. Given that the one file per
> table might be preferable.
> 
> 
>  >
>  > **
>  > *Bach-Nga
> 
>  >
> 
> 
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

18 June 2020, 19:54:44

>>psql -d production -U postgres -c 'select count(*) from cell_per';
Null display is "NULL".
count
-------
68
(1 row)

you can do this once you are in psql. But if you are running from shell script, it will be an error

>>What error messages do you get?

my shell script is:

@echo off

C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432 -c "select count(*) from tableA;"

pause

the error I have is 'C:\Program' is not recognized as an internal or external command, operable program or batch file.

I even surround the path in quotes because of space.

@echo off

cmd /c ""C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432 -c "select count(*) from tableA;"

pause

error is: 'C:\Program Files\PostgreSQL\11\bin\psql: illegal option -- u

when I put -P Password123 (or fully qualified password=Password123)

it gives me another error "pset: unknow option: Password123

psql: could not set printing parameter "Password123"

I can connect from psql shell fine when it prompt hostname, username (but connect to postgres not to PSmasteruser, PSmasteruser username set up for aws maintenance postgres database, someone did, not me and the password is same on both). Once I'm in psql and I can change to PSCIDR instance fine and run select count(*) from tableA;

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.

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

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

On Thursday, June 18, 2020, 03:06:39 PM EDT, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

On 6/18/20 9:40 AM, Pepe TD Vo wrote:
> I get this part that separates SQL script for import each table,
>
> (import.sql)
> begin;
> \copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;
> commit;
>
> but when open the psql sql shell script it prompts line by line for
> localhost, port, db, user, and password. If I set up a script and let
> it run it won't connect to the postgresql instance. I want to know how
> to execute a batch script connect to the database/instance.
> In oracle I created a shell script with all oracle_sid, oracle_home, and
> read the function/procedure... for psql, especially from window client,
> I did put psql_home and connect to the instance, it failed
>
> c:\Progra~1\PostgreSQL\11\bin\psql -d PSCIDR -h localhost -p 5432 -U
> postgres -i import.sql

The above should be -f import.sql. AFAIK there is no -i for psql, so
that should be failing.

>
> even I do a simple count
>
> c:\Progra~1\PostgreSQL\11\bin\psql -d PSCIDR -h localhost -p 5432 -U
> postgres -c "select count(*) from tableA";

psql -d production -U postgres -c 'select count(*) from cell_per';
Null display is "NULL".
count
-------
68
(1 row)

psql -d production -U postgres -c 'select count(*) from cell_per'
Null display is "NULL".
count
-------
68

psql -d production -U postgres -c 'select count(*) from cell_per;'
Null display is "NULL".
count
-------
68

>
> none of them is work. Try to learn how to execute its script.

What error messages do you get?

>
> **
> *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.EmojiEmojiEmoji
> 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 Thursday, June 18, 2020, 12:08:44 PM EDT, Adrian Klaver
> <adrian.klaver@aklaver.com> wrote:
>
>
> On 6/18/20 8:20 AM, Pepe TD Vo wrote:
>
> Please don't top post. The preferred style on this list is inline or
> bottom posting(https://en.wikipedia.org/wiki/Posting_style).
>
> > I have a Postgresql client installed and connected. how can i create a
> > batch script running from the client window?
>
> Create a file with commands in it like the example from Christopher
> Browne that was posted earlier:
>
> "There is no single straightforward answer to that.
>
>
> Supposing I want a batch to either all be processed, or to all not process,
> then I might write a sql file like:
>
>
> begin;
> \copy table_1 (c1, c2, c3) from '/path/tabledata1.csv' csv header;
> \copy table_2 (c1, c2, c3) from '/path/tabledata2.csv' csv header;
> \copy table_3 (c1, c2, c3) from '/path/tabledata3.csv' csv header;
> commit;
>
>
> But you may be fine with having a separate SQL script for each table.
>
>
> There will be conditions where one or the other is more appropriate, and
> that will be based on the requirements of the process."
>
> Then point psql at it:
>
> psql -d some_db -h some_host -U some_user -f the_file
>
> Be aware that \copy is all or nothing. If there is a single failure in
> the copying the whole copy will rollback. Given that the one file per
> table might be preferable.
>
>
> >
> > **
> > *Bach-Nga
>
> >
>
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>

>
>
>

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

18 June 2020, 19:54:44

>>What error messages do you get?

my shell script is:

@echo off

C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432 -c "select count(*) from tableA;"

pause

the error I have is 'C:\Program' is not recognized as an internal or external command, operable program or batch file.

I even surround the path in quotes because of space.

@echo off

cmd /c ""C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432 -c "select count(*) from tableA;"

pause

error is: 'C:\Program Files\PostgreSQL\11\bin\psql: illegal option -- u

when I put -P Password123 (or fully qualified password=Password123)

it gives me another error "pset: unknow option: Password123

psql: could not set printing parameter "Password123"

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.

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

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

On Thursday, June 18, 2020, 03:06:39 PM EDT, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

>
>
>

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

18 June 2020, 23:00:33

On 6/18/20 12:54 PM, Pepe TD Vo wrote:
>>>psql -d production  -U postgres -c 'select count(*) from cell_per';
> Null display is "NULL".
>    count
> -------
>      68
> (1 row)
> 
> you can do this once you are in psql. But if you are running from shell 
> script, it will be an error
> 
>  >>What error messages do you get?
> 
> my shell script is:
> @echo off
> C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser  -d PSCIDR -h 
> hostname.amazonaws.com -p 5432 -c "select count(*) from tableA;"
> pause
> 
> the error I have is 'C:\Program' is not recognized as an internal or 
> external command, operable program or batch file.
> 
> I even surround the path in quotes because of space.
> @echo off
> cmd /c ""C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d 
> PSCIDR -h hostname.amazonaws.com -p 5432 -c "select count(*) from tableA;"
> pause

Not sure how quoting works in Windows shell scripts, but pretty sure the 
above has unbalanced quotes.


> 
> error is: 'C:\Program Files\PostgreSQL\11\bin\psql: illegal option -- u
> 
> when I put -P Password123 (or fully qualified password=Password123)

I would recommend spending some time here:

https://www.postgresql.org/docs/12/app-psql.html

to see what the options are. Hint: -P is not the option for password.

> 
> it gives me another error "pset: unknow option: Password123
> psql: could not set printing parameter "Password123"

It is the option for pset as the error message says.

> 
> I can connect from psql shell fine when it prompt hostname, username 
> (but connect to postgres not to PSmasteruser, PSmasteruser username set 
> up for aws maintenance postgres database, someone did, not me and the 
> password is same on both).  Once I'm in psql and I can change to PSCIDR 
> instance fine and run select count(*) from tableA;
> 
> 
> 
> **
> *Bach-Nga
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

18 June 2020, 23:00:33

On 6/18/20 12:54 PM, Pepe TD Vo wrote:
>>>psql -d production  -U postgres -c 'select count(*) from cell_per';
> Null display is "NULL".
>    count
> -------
>      68
> (1 row)
> 
> you can do this once you are in psql. But if you are running from shell 
> script, it will be an error
> 
>  >>What error messages do you get?
> 
> my shell script is:
> @echo off
> C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser  -d PSCIDR -h 
> hostname.amazonaws.com -p 5432 -c "select count(*) from tableA;"
> pause
> 
> the error I have is 'C:\Program' is not recognized as an internal or 
> external command, operable program or batch file.
> 
> I even surround the path in quotes because of space.
> @echo off
> cmd /c ""C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d 
> PSCIDR -h hostname.amazonaws.com -p 5432 -c "select count(*) from tableA;"
> pause

Not sure how quoting works in Windows shell scripts, but pretty sure the 
above has unbalanced quotes.


> 
> error is: 'C:\Program Files\PostgreSQL\11\bin\psql: illegal option -- u
> 
> when I put -P Password123 (or fully qualified password=Password123)

I would recommend spending some time here:

https://www.postgresql.org/docs/12/app-psql.html

to see what the options are. Hint: -P is not the option for password.

> 
> it gives me another error "pset: unknow option: Password123
> psql: could not set printing parameter "Password123"

It is the option for pset as the error message says.

> 
> I can connect from psql shell fine when it prompt hostname, username 
> (but connect to postgres not to PSmasteruser, PSmasteruser username set 
> up for aws maintenance postgres database, someone did, not me and the 
> password is same on both).  Once I'm in psql and I can change to PSCIDR 
> instance fine and run select count(*) from tableA;
> 
> 
> 
> **
> *Bach-Nga
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

18 June 2020, 23:37:48

thank you for the link. I did try it and it's still error

echo 'SELECT count(*) FROM tableA;' | C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432

I can run 'psql -u postgres -d PSCIDR -p 5432' (on Linux server, still learning how to run it from psql shell in Window) fine from psql prompt. Just still wonder how to connect directly to the instance PSCIDR from scripting in both aws and linux. Otherwise manually run using pgAdmin.

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.

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

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

On Thursday, June 18, 2020, 07:00:37 PM EDT, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

On 6/18/20 12:54 PM, Pepe TD Vo wrote:
>>>psql -d production -U postgres -c 'select count(*) from cell_per';
> Null display is "NULL".
> count
> -------
> 68
> (1 row)
>
> you can do this once you are in psql. But if you are running from shell
> script, it will be an error
>
> >>What error messages do you get?
>
> my shell script is:
> @echo off
> C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser -d PSCIDR -h
> hostname.amazonaws.com -p 5432 -c "select count(*) from tableA;"
> pause
>
> the error I have is 'C:\Program' is not recognized as an internal or
> external command, operable program or batch file.
>
> I even surround the path in quotes because of space.
> @echo off
> cmd /c ""C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d
> PSCIDR -h hostname.amazonaws.com -p 5432 -c "select count(*) from tableA;"
> pause

Not sure how quoting works in Windows shell scripts, but pretty sure the
above has unbalanced quotes.

>
> error is: 'C:\Program Files\PostgreSQL\11\bin\psql: illegal option -- u
>
> when I put -P Password123 (or fully qualified password=Password123)

I would recommend spending some time here:

https://www.postgresql.org/docs/12/app-psql.html

to see what the options are. Hint: -P is not the option for password.

>
> it gives me another error "pset: unknow option: Password123
> psql: could not set printing parameter "Password123"

It is the option for pset as the error message says.

>
> I can connect from psql shell fine when it prompt hostname, username
> (but connect to postgres not to PSmasteruser, PSmasteruser username set
> up for aws maintenance postgres database, someone did, not me and the
> password is same on both). Once I'm in psql and I can change to PSCIDR
> instance fine and run select count(*) from tableA;
>
>
>
> **
> *Bach-Nga
>

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

18 June 2020, 23:37:48

thank you for the link. I did try it and it's still error

echo 'SELECT count(*) FROM tableA;' | C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432

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.

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

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

On Thursday, June 18, 2020, 07:00:37 PM EDT, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 00:00:04

On 6/18/20 4:37 PM, Pepe TD Vo wrote:
> thank you for the link.  I did try it and it's still error
> 
> echo 'SELECT count(*) FROM tableA;' |
> C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser -d PSCIDR -h 
> hostname.amazonaws.com -p 5432


This is getting old. The error is?
> 
> I can run 'psql -u postgres -d PSCIDR -p 5432' (on Linux server, still 
> learning how to run it from psql shell in Window) fine from psql 
> prompt.  Just still wonder how to connect directly to the instance 
> PSCIDR from scripting in both aws and linux.  Otherwise manually run 
> using pgAdmin.
> 
> v/r,
> 
> **
> *Bach-Nga
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 00:00:04

On 6/18/20 4:37 PM, Pepe TD Vo wrote:
> thank you for the link.  I did try it and it's still error
> 
> echo 'SELECT count(*) FROM tableA;' |
> C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser -d PSCIDR -h 
> hostname.amazonaws.com -p 5432


This is getting old. The error is?
> 
> I can run 'psql -u postgres -d PSCIDR -p 5432' (on Linux server, still 
> learning how to run it from psql shell in Window) fine from psql 
> prompt.  Just still wonder how to connect directly to the instance 
> PSCIDR from scripting in both aws and linux.  Otherwise manually run 
> using pgAdmin.
> 
> v/r,
> 
> **
> *Bach-Nga
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

cgerard999@gmail.com

Date:

19 June 2020, 01:25:21

Remove the quotes around echo

echo select count(*) from web_20200619; | "C:\Program Files\postgresql\11\bin\psql" -d *** -h *** -U ***

or, store your query into a text file and use

psql -f query.sql

Sent from my mobile phone

Le 19 juin 2020 à 02:00, Adrian Klaver <adrian.klaver@aklaver.com> a écrit :

On 6/18/20 4:37 PM, Pepe TD Vo wrote:
thank you for the link. I did try it and it's still error
echo 'SELECT count(*) FROM tableA;' |
C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432

This is getting old. The error is?
I can run 'psql -u postgres -d PSCIDR -p 5432' (on Linux server, still learning how to run it from psql shell in Window) fine from psql prompt. Just still wonder how to connect directly to the instance PSCIDR from scripting in both aws and linux. Otherwise manually run using pgAdmin.
v/r,
**
*Bach-Nga

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

cgerard999@gmail.com

Date:

19 June 2020, 01:25:21

Remove the quotes around echo

echo select count(*) from web_20200619; | "C:\Program Files\postgresql\11\bin\psql" -d *** -h *** -U ***

or, store your query into a text file and use

psql -f query.sql

Sent from my mobile phone

Le 19 juin 2020 à 02:00, Adrian Klaver <adrian.klaver@aklaver.com> a écrit :

On 6/18/20 4:37 PM, Pepe TD Vo wrote:
thank you for the link. I did try it and it's still error
echo 'SELECT count(*) FROM tableA;' |
C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432

This is getting old. The error is?
I can run 'psql -u postgres -d PSCIDR -p 5432' (on Linux server, still learning how to run it from psql shell in Window) fine from psql prompt. Just still wonder how to connect directly to the instance PSCIDR from scripting in both aws and linux. Otherwise manually run using pgAdmin.
v/r,
**
*Bach-Nga

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

19 June 2020, 11:12:30

thank you, I tried that too, remove the quote around the echo and it prompt for password, as I mentioned no matter I put -P mypassword no matter what I spell out password=mypassword still argument error

>>echo select count(*) from tableA; | "C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432

>> echo select count(*) from tableA; | "C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432 password=mypassword

all usernames are same password.

thank you so much for all input.

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.

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

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

On Thursday, June 18, 2020, 09:25:41 PM EDT, <cgerard999@gmail.com> wrote:

Remove the quotes around echo

echo select count(*) from web_20200619; | "C:\Program Files\postgresql\11\bin\psql" -d *** -h *** -U ***

or, store your query into a text file and use

psql -f query.sql

Sent from my mobile phone

Le 19 juin 2020 à 02:00, Adrian Klaver <adrian.klaver@aklaver.com> a écrit :

On 6/18/20 4:37 PM, Pepe TD Vo wrote:
thank you for the link. I did try it and it's still error
echo 'SELECT count(*) FROM tableA;' |
C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432

This is getting old. The error is?
I can run 'psql -u postgres -d PSCIDR -p 5432' (on Linux server, still learning how to run it from psql shell in Window) fine from psql prompt. Just still wonder how to connect directly to the instance PSCIDR from scripting in both aws and linux. Otherwise manually run using pgAdmin.
v/r,
**
*Bach-Nga

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

19 June 2020, 11:12:30

>>echo select count(*) from tableA; | "C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432

>> echo select count(*) from tableA; | "C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432 password=mypassword

all usernames are same password.

thank you so much for all input.

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.

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

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

On Thursday, June 18, 2020, 09:25:41 PM EDT, <cgerard999@gmail.com> wrote:

Remove the quotes around echo

echo select count(*) from web_20200619; | "C:\Program Files\postgresql\11\bin\psql" -d *** -h *** -U ***

or, store your query into a text file and use

psql -f query.sql

Sent from my mobile phone

Le 19 juin 2020 à 02:00, Adrian Klaver <adrian.klaver@aklaver.com> a écrit :

On 6/18/20 4:37 PM, Pepe TD Vo wrote:
thank you for the link. I did try it and it's still error
echo 'SELECT count(*) FROM tableA;' |
C:\Program Files\PostgreSQL\11\bin\psql -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432

This is getting old. The error is?
I can run 'psql -u postgres -d PSCIDR -p 5432' (on Linux server, still learning how to run it from psql shell in Window) fine from psql prompt. Just still wonder how to connect directly to the instance PSCIDR from scripting in both aws and linux. Otherwise manually run using pgAdmin.
v/r,
**
*Bach-Nga

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 13:19:14

On 6/19/20 4:12 AM, Pepe TD Vo wrote:
> thank you,   I tried that too, remove the quote around the echo and it 
> prompt for password, as I mentioned no matter I put -P mypassword no 
> matter what I spell out password=mypassword still argument error

Once again -P has nothing to do with password. Also --password does not 
take an argument, it is meant to be used as is. The purpose is to force 
a password prompt. This is all spelled out here:

https://www.postgresql.org/docs/12/app-psql.html

Also spelled out in above is:

" It is also convenient to have a ~/.pgpass file to avoid regularly 
having to type in passwords. See Section 33.15 for more information."

And Section 33.15:

https://www.postgresql.org/docs/12/libpq-pgpass.html

"The file .pgpass in a user's home directory can contain passwords to be 
used if the connection requires a password (and no password has been 
specified otherwise).  ..."

Read more at link for how to do that.

> 
>  >>echo select count(*) from tableA; | "C:\Program 
> Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h 
> hostname.amazonaws.com -p 5432
> 
>  >> echo select count(*) from tableA; | "C:\Program 
> Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h 
> hostname.amazonaws.com -p 5432 password=mypassword
> 
> all usernames are same password.
> 
> thank you so much for all input.
> 
> v/r,
> 
> **
> *Bach-Nga

-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 13:19:14

On 6/19/20 4:12 AM, Pepe TD Vo wrote:
> thank you,   I tried that too, remove the quote around the echo and it 
> prompt for password, as I mentioned no matter I put -P mypassword no 
> matter what I spell out password=mypassword still argument error

Once again -P has nothing to do with password. Also --password does not 
take an argument, it is meant to be used as is. The purpose is to force 
a password prompt. This is all spelled out here:

https://www.postgresql.org/docs/12/app-psql.html

Also spelled out in above is:

" It is also convenient to have a ~/.pgpass file to avoid regularly 
having to type in passwords. See Section 33.15 for more information."

And Section 33.15:

https://www.postgresql.org/docs/12/libpq-pgpass.html

"The file .pgpass in a user's home directory can contain passwords to be 
used if the connection requires a password (and no password has been 
specified otherwise).  ..."

Read more at link for how to do that.

> 
>  >>echo select count(*) from tableA; | "C:\Program 
> Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h 
> hostname.amazonaws.com -p 5432
> 
>  >> echo select count(*) from tableA; | "C:\Program 
> Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h 
> hostname.amazonaws.com -p 5432 password=mypassword
> 
> all usernames are same password.
> 
> thank you so much for all input.
> 
> v/r,
> 
> **
> *Bach-Nga

-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

19 June 2020, 13:53:36

Thank you sir and I am sorry for the typo not having "--" on password. I did spelling out with --password=mypassword

>> echo select count(*) from tableA; | "C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432 --password=mypassword

even -W for password

>> echo select count(*) from tableA; | "C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432 -W=mypassword

none of them work, still prompt me for password to type in. I will look into the pgpassfile which I know it will fail again.

very respectfully,

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.

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

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

On Friday, June 19, 2020, 09:19:35 AM EDT, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

On 6/19/20 4:12 AM, Pepe TD Vo wrote:
> thank you, I tried that too, remove the quote around the echo and it
> prompt for password, as I mentioned no matter I put -P mypassword no
> matter what I spell out password=mypassword still argument error

Once again -P has nothing to do with password. Also --password does not
take an argument, it is meant to be used as is. The purpose is to force
a password prompt. This is all spelled out here:

https://www.postgresql.org/docs/12/app-psql.html

Also spelled out in above is:

" It is also convenient to have a ~/.pgpass file to avoid regularly
having to type in passwords. See Section 33.15 for more information."

And Section 33.15:

https://www.postgresql.org/docs/12/libpq-pgpass.html

"The file .pgpass in a user's home directory can contain passwords to be
used if the connection requires a password (and no password has been
specified otherwise). ..."

Read more at link for how to do that.

>
> >>echo select count(*) from tableA; | "C:\Program
> Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h
> hostname.amazonaws.com -p 5432
>
> >> echo select count(*) from tableA; | "C:\Program
> Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h
> hostname.amazonaws.com -p 5432 password=mypassword
>
> all usernames are same password.
>
> thank you so much for all input.
>
> v/r,
>
> **
> *Bach-Nga

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

19 June 2020, 13:53:36

Thank you sir and I am sorry for the typo not having "--" on password. I did spelling out with --password=mypassword

>> echo select count(*) from tableA; | "C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432 --password=mypassword

even -W for password

>> echo select count(*) from tableA; | "C:\Program Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h hostname.amazonaws.com -p 5432 -W=mypassword

none of them work, still prompt me for password to type in. I will look into the pgpassfile which I know it will fail again.

very respectfully,

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.

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

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

On Friday, June 19, 2020, 09:19:35 AM EDT, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 13:58:02

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.

> 
>>> echo select count(*) from tableA; | "C:\Program 
> Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h 
> hostname.amazonaws.com -p 5432 --password=mypassword
> 
> even -W for password
>>> echo select count(*) from tableA; | "C:\Program 
> Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h 
> hostname.amazonaws.com -p 5432 -W=mypassword
> 
> none of them work, still prompt me for password to type in.  I will look 
> into the pgpassfile which I know it will fail again.
> 
> 
> very respectfully,
> 
> **
> *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.EmojiEmojiEmoji
> 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, 09:19:35 AM EDT, Adrian Klaver 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> On 6/19/20 4:12 AM, Pepe TD Vo wrote:
>  > thank you,   I tried that too, remove the quote around the echo and it
>  > prompt for password, as I mentioned no matter I put -P mypassword no
>  > matter what I spell out password=mypassword still argument error
> 
> Once again -P has nothing to do with password. Also --password does not
> take an argument, it is meant to be used as is. The purpose is to force
> a password prompt. This is all spelled out here:
> 
> https://www.postgresql.org/docs/12/app-psql.html
> 
> Also spelled out in above is:
> 
> " It is also convenient to have a ~/.pgpass file to avoid regularly
> having to type in passwords. See Section 33.15 for more information."
> 
> And Section 33.15:
> 
> https://www.postgresql.org/docs/12/libpq-pgpass.html
> 
> "The file .pgpass in a user's home directory can contain passwords to be
> used if the connection requires a password (and no password has been
> specified otherwise).  ..."
> 
> Read more at link for how to do that.
> 
> 
>  >
>  >  >>echo select count(*) from tableA; | "C:\Program
>  > Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h
>  > hostname.amazonaws.com -p 5432
>  >
>  >  >> echo select count(*) from tableA; | "C:\Program
>  > Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h
>  > hostname.amazonaws.com -p 5432 password=mypassword
>  >
>  > all usernames are same password.
>  >
>  > thank you so much for all input.
>  >
>  > v/r,
>  >
>  > **
>  > *Bach-Nga
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 13:58:02

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.

> 
>>> echo select count(*) from tableA; | "C:\Program 
> Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h 
> hostname.amazonaws.com -p 5432 --password=mypassword
> 
> even -W for password
>>> echo select count(*) from tableA; | "C:\Program 
> Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h 
> hostname.amazonaws.com -p 5432 -W=mypassword
> 
> none of them work, still prompt me for password to type in.  I will look 
> into the pgpassfile which I know it will fail again.
> 
> 
> very respectfully,
> 
> **
> *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.EmojiEmojiEmoji
> 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, 09:19:35 AM EDT, Adrian Klaver 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> On 6/19/20 4:12 AM, Pepe TD Vo wrote:
>  > thank you,   I tried that too, remove the quote around the echo and it
>  > prompt for password, as I mentioned no matter I put -P mypassword no
>  > matter what I spell out password=mypassword still argument error
> 
> Once again -P has nothing to do with password. Also --password does not
> take an argument, it is meant to be used as is. The purpose is to force
> a password prompt. This is all spelled out here:
> 
> https://www.postgresql.org/docs/12/app-psql.html
> 
> Also spelled out in above is:
> 
> " It is also convenient to have a ~/.pgpass file to avoid regularly
> having to type in passwords. See Section 33.15 for more information."
> 
> And Section 33.15:
> 
> https://www.postgresql.org/docs/12/libpq-pgpass.html
> 
> "The file .pgpass in a user's home directory can contain passwords to be
> used if the connection requires a password (and no password has been
> specified otherwise).  ..."
> 
> Read more at link for how to do that.
> 
> 
>  >
>  >  >>echo select count(*) from tableA; | "C:\Program
>  > Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h
>  > hostname.amazonaws.com -p 5432
>  >
>  >  >> echo select count(*) from tableA; | "C:\Program
>  > Files\PostgreSQL\11\bin\psql" -U PSmasteruser -d PSCIDR -h
>  > hostname.amazonaws.com -p 5432 password=mypassword
>  >
>  > all usernames are same password.
>  >
>  > thank you so much for all input.
>  >
>  > v/r,
>  >
>  > **
>  > *Bach-Nga
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

"David G. Johnston"

Date:

19 June 2020, 14:52:54

On Fri, Jun 19, 2020 at 6:58 AM Adrian Klaver <adrian.klaver@aklaver.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.

Re: create batch script to import into postgres tables

From

"David G. Johnston"

Date:

19 June 2020, 14:52:54

On Fri, Jun 19, 2020 at 6:58 AM Adrian Klaver <adrian.klaver@aklaver.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.

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 14:57:31

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

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 14:57:31

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

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

19 June 2020, 15:07:35

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.

**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@aklaver.com> 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@aklaver.com
> <mailto:adrian.klaver@aklaver.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.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

19 June 2020, 15:07:35

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.

**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@aklaver.com> wrote:

>

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

cgerard999@gmail.com

Date:

19 June 2020, 15:30:57

There is an alternate solution, which is to launch pgadmin GUI, connect to the database, tick « save password »

Then psql won’t prompt fir password any more.

Pay however attention to the security concern.

Sent from my mobile phone

Le 19 juin 2020 à 17:07, Pepe TD Vo <pepevo@yahoo.com> a écrit :

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@aklaver.com> 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@aklaver.com
> <mailto:adrian.klaver@aklaver.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.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

cgerard999@gmail.com

Date:

19 June 2020, 15:30:57

There is an alternate solution, which is to launch pgadmin GUI, connect to the database, tick « save password »

Then psql won’t prompt fir password any more.

Pay however attention to the security concern.

Sent from my mobile phone

Le 19 juin 2020 à 17:07, Pepe TD Vo <pepevo@yahoo.com> a écrit :

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@aklaver.com> 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@aklaver.com
> <mailto:adrian.klaver@aklaver.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.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 18:23:35

On 6/19/20 8:30 AM, cgerard999@gmail.com wrote:
> There is an alternate solution, which is to launch pgadmin GUI, connect 
> to the database, tick « save password »
> Then psql won’t prompt fir password any more.

Pretty sure that is only within the context of pgAdmin.

> Pay however attention to the security concern.
> 
> Sent from my mobile phone
> 
>> Le 19 juin 2020 à 17:07, Pepe TD Vo <pepevo@yahoo.com> a écrit :
>>
>> 
>> 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.EmojiEmojiEmoji
>> 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@aklaver.com> 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@aklaver.com <mailto:adrian.klaver@aklaver.com>
>> > <mailto:adrian.klaver@aklaver.com 
>> <mailto:adrian.klaver@aklaver.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.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>>
>>


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 18:23:35

On 6/19/20 8:30 AM, cgerard999@gmail.com wrote:
> There is an alternate solution, which is to launch pgadmin GUI, connect 
> to the database, tick « save password »
> Then psql won’t prompt fir password any more.

Pretty sure that is only within the context of pgAdmin.

> Pay however attention to the security concern.
> 
> Sent from my mobile phone
> 
>> Le 19 juin 2020 à 17:07, Pepe TD Vo <pepevo@yahoo.com> a écrit :
>>
>> 
>> 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.EmojiEmojiEmoji
>> 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@aklaver.com> 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@aklaver.com <mailto:adrian.klaver@aklaver.com>
>> > <mailto:adrian.klaver@aklaver.com 
>> <mailto:adrian.klaver@aklaver.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.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>>
>>


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

19 June 2020, 19:26:05

thank you for all the information but I have no problem connecting to the database using pgAdmin and/or directly psql from the postgres database.

I need to set up a batch/cron job to run in Linux/AWS to ingest the data. Therefore pgadmin GUI is not an option. I used pgAdmin to create tables, triggers, function triggers and manual importing/exporting. You can't schedule a time to run importing from csv file(s) using pgAdmin as same OEM.

The select table in this question is just an example for me to create scripting to see it connect or not. No one at work to manually run the script and enter the password. Need to bypass it like Oracle scripting. Since this is not an option to put the password to connect to the database and run the script(s), we will find another way to do.

I am thankful for all the input.

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.

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

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

On Friday, June 19, 2020, 02:24:05 PM EDT, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

On 6/19/20 8:30 AM, cgerard999@gmail.com wrote:
> There is an alternate solution, which is to launch pgadmin GUI, connect
> to the database, tick « save password »
> Then psql won’t prompt fir password any more.

Pretty sure that is only within the context of pgAdmin.

> Pay however attention to the security concern.
>
> Sent from my mobile phone
>
>> Le 19 juin 2020 à 17:07, Pepe TD Vo <pepevo@yahoo.com> a écrit :
>>
>>
>> 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.EmojiEmojiEmoji
>> 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@aklaver.com> 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@aklaver.com <mailto:adrian.klaver@aklaver.com>
>> > <mailto:adrian.klaver@aklaver.com
>> <mailto:adrian.klaver@aklaver.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.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>>
>>

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Pepe TD Vo

Date:

19 June 2020, 19:26:05

thank you for all the information but I have no problem connecting to the database using pgAdmin and/or directly psql from the postgres database.

I am thankful for all the input.

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.

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

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

On Friday, June 19, 2020, 02:24:05 PM EDT, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

>>
>> >
>>
>>
>> --
>> Adrian Klaver
>> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>>
>>

--
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Rob Sargent

Date:

19 June 2020, 19:37:28

On Jun 19, 2020, at 1:26 PM, Pepe TD Vo <pepevo@yahoo.com> wrote:

thank you for all the information but I have no problem connecting to the database using pgAdmin and/or directly psql from the postgres database.

I need to set up a batch/cron job to run in Linux/AWS to ingest the data. Therefore pgadmin GUI is not an option. I used pgAdmin to create tables, triggers, function triggers and manual importing/exporting. You can't schedule a time to run importing from csv file(s) using pgAdmin as same OEM.

The select table in this question is just an example for me to create scripting to see it connect or not. No one at work to manually run the script and enter the password. Need to bypass it like Oracle scripting. Since this is not an option to put the password to connect to the database and run the script(s), we will find another way to do.

I am thankful for all the input.

v/r,

And it has been explained upstream that one “way to do” is to use a .pgpass file for the cronjob user. And that file must be read-only to user, no access to group or other (chmod 400 $CRONUSER/.pgpass). Another is a “trust” entry for the user in pg_hba.conf. I suggest you revisit those messages.

Re: create batch script to import into postgres tables

From

Rob Sargent

Date:

19 June 2020, 19:37:28

On Jun 19, 2020, at 1:26 PM, Pepe TD Vo <pepevo@yahoo.com> wrote:

thank you for all the information but I have no problem connecting to the database using pgAdmin and/or directly psql from the postgres database.

I need to set up a batch/cron job to run in Linux/AWS to ingest the data. Therefore pgadmin GUI is not an option. I used pgAdmin to create tables, triggers, function triggers and manual importing/exporting. You can't schedule a time to run importing from csv file(s) using pgAdmin as same OEM.

The select table in this question is just an example for me to create scripting to see it connect or not. No one at work to manually run the script and enter the password. Need to bypass it like Oracle scripting. Since this is not an option to put the password to connect to the database and run the script(s), we will find another way to do.

I am thankful for all the input.

v/r,

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 19:37:55

On 6/19/20 12:26 PM, Pepe TD Vo wrote:
> thank you for all the information but I have no problem connecting to 
> the database using pgAdmin and/or directly psql from the postgres database.
> 
> I need to set up a batch/cron job to run in Linux/AWS to ingest the 
> data.  Therefore pgadmin GUI is not an option. I used pgAdmin to create 
> tables, triggers, function triggers and manual importing/exporting.  You 
> can't schedule a time to run importing from  csv file(s) using pgAdmin 
> as same OEM.

There is pgAgent:
https://www.pgadmin.org/docs/pgadmin4/development/pgagent.html

> 
> The select table in this question is just an example for me to create 
> scripting to see it connect or not.  No one at work to manually run the 
> script and enter the password.  Need to bypass it like Oracle 
> scripting.  Since this is not an option to put the password to connect 
> to the database and run the script(s), we will find another way to do.

But there is an option.

> 
> I am thankful for all the input.
> 
> 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.EmojiEmojiEmoji
> 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, 02:24:05 PM EDT, Adrian Klaver 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> On 6/19/20 8:30 AM, cgerard999@gmail.com <mailto:cgerard999@gmail.com> 
> wrote:
>  > There is an alternate solution, which is to launch pgadmin GUI, connect
>  > to the database, tick « save password »
>  > Then psql won’t prompt fir password any more.
> 
> Pretty sure that is only within the context of pgAdmin.
> 
>  > Pay however attention to the security concern.
>  >
>  > Sent from my mobile phone
>  >
>  >> Le 19 juin 2020 à 17:07, Pepe TD Vo <pepevo@yahoo.com 
> <mailto:pepevo@yahoo.com>> a écrit :
>  >>
>  >> 
>  >> 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.EmojiEmojiEmoji
>  >> 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@aklaver.com <mailto:adrian.klaver@aklaver.com>> 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@aklaver.com <mailto:adrian.klaver@aklaver.com> 
> <mailto:adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>>
>  >> > <mailto:adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>  >> <mailto:adrian.klaver@aklaver.com 
> <mailto:adrian.klaver@aklaver.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.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> 
> <mailto:adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>>
>  >>
>  >>
> 
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

Adrian Klaver

Date:

19 June 2020, 19:37:55

On 6/19/20 12:26 PM, Pepe TD Vo wrote:
> thank you for all the information but I have no problem connecting to 
> the database using pgAdmin and/or directly psql from the postgres database.
> 
> I need to set up a batch/cron job to run in Linux/AWS to ingest the 
> data.  Therefore pgadmin GUI is not an option. I used pgAdmin to create 
> tables, triggers, function triggers and manual importing/exporting.  You 
> can't schedule a time to run importing from  csv file(s) using pgAdmin 
> as same OEM.

There is pgAgent:
https://www.pgadmin.org/docs/pgadmin4/development/pgagent.html

> 
> The select table in this question is just an example for me to create 
> scripting to see it connect or not.  No one at work to manually run the 
> script and enter the password.  Need to bypass it like Oracle 
> scripting.  Since this is not an option to put the password to connect 
> to the database and run the script(s), we will find another way to do.

But there is an option.

> 
> I am thankful for all the input.
> 
> 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.EmojiEmojiEmoji
> 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, 02:24:05 PM EDT, Adrian Klaver 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> On 6/19/20 8:30 AM, cgerard999@gmail.com <mailto:cgerard999@gmail.com> 
> wrote:
>  > There is an alternate solution, which is to launch pgadmin GUI, connect
>  > to the database, tick « save password »
>  > Then psql won’t prompt fir password any more.
> 
> Pretty sure that is only within the context of pgAdmin.
> 
>  > Pay however attention to the security concern.
>  >
>  > Sent from my mobile phone
>  >
>  >> Le 19 juin 2020 à 17:07, Pepe TD Vo <pepevo@yahoo.com 
> <mailto:pepevo@yahoo.com>> a écrit :
>  >>
>  >> 
>  >> 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.EmojiEmojiEmoji
>  >> 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@aklaver.com <mailto:adrian.klaver@aklaver.com>> 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@aklaver.com <mailto:adrian.klaver@aklaver.com> 
> <mailto:adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>>
>  >> > <mailto:adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>  >> <mailto:adrian.klaver@aklaver.com 
> <mailto:adrian.klaver@aklaver.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.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> 
> <mailto:adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>>
>  >>
>  >>
> 
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: create batch script to import into postgres tables

From

"David G. Johnston"

Date:

20 June 2020, 00:24:09

On Friday, June 19, 2020, pepevo <pepevo@yahoo.com> wrote:

We can't just install any softwares without Goverment's approval. Also, they might ask Oracle/mysql/sql can run batch script, why not Postgres? I wonder myself and just realize today from this email.

PostreSQL isn’t the issue here, you are. To the extent that others attempting to help you over email are insufficient is a failing driven mainly by the medium of choice probably being an inefficient medium for the student. What you want to do is possible but it requires understanding multiple applications. You are better off getting closer to your goal by reading books and articles about those applications and then asking better questions. Or at minimum being more detailed in stating your goal and requirements.

David J.

Re: create batch script to import into postgres tables

From

"David G. Johnston"

Date:

20 June 2020, 00:24:09

On Friday, June 19, 2020, pepevo <pepevo@yahoo.com> wrote:

We can't just install any softwares without Goverment's approval. Also, they might ask Oracle/mysql/sql can run batch script, why not Postgres? I wonder myself and just realize today from this email.

David J.

Re: create batch script to import into postgres tables

From

"David G. Johnston"

Date:

20 June 2020, 01:38:14

On Friday, June 19, 2020, pepevo <pepevo@yahoo.com> wrote:

But everything can run by script on the server, right?

Separation of concerns. The server with the database cluster should probably not be running application code. Application code can be run other machine, “admin” machine is one label. Though for development it shouldn’t matter so long as the application is configurable. Configure it for local during development and when in production it pulls production configuration.

David J.

Re: create batch script to import into postgres tables

From

"David G. Johnston"

Date:

20 June 2020, 01:38:14

On Friday, June 19, 2020, pepevo <pepevo@yahoo.com> wrote:

But everything can run by script on the server, right?

David J.

Re: create batch script to import into postgres tables

From

Shaozhong SHI

Date:

08 July 2020, 11:41:19

I am happy to help with testing the bash script and producing a documentation.

Regards,

Shao

On Sat, 20 Jun 2020 at 02:38, David G. Johnston <david.g.johnston@gmail.com> wrote:

On Friday, June 19, 2020, pepevo <pepevo@yahoo.com> wrote:
But everything can run by script on the server, right?

Separation of concerns. The server with the database cluster should probably not be running application code. Application code can be run other machine, “admin” machine is one label. Though for development it shouldn’t matter so long as the application is configurable. Configure it for local during development and when in production it pulls production configuration.

David J.

Re: create batch script to import into postgres tables

From

Shaozhong SHI

Date:

08 July 2020, 11:41:19

I am happy to help with testing the bash script and producing a documentation.

Regards,

Shao

On Sat, 20 Jun 2020 at 02:38, David G. Johnston <david.g.johnston@gmail.com> wrote:

On Friday, June 19, 2020, pepevo <pepevo@yahoo.com> wrote:
But everything can run by script on the server, right?

Separation of concerns. The server with the database cluster should probably not be running application code. Application code can be run other machine, “admin” machine is one label. Though for development it shouldn’t matter so long as the application is configurable. Configure it for local during development and when in production it pulls production configuration.

David J.