Skip to main content
I think a link to 8.3 is appropriate in this case
Source Link
Jack Douglas
  • 40.2k
  • 15
  • 104
  • 177

Please refer to the PostgreSQLpostgres manual for COPY. Note the versions across the top; click on 8.3 for docs that apply to your version of Pgmanual for COPY.

In pgAdmin (or the sql string you pass via a script or other db connection) you would just use COPY with no "" prefix.

so enter something like : COPY tablename....

You need to make sure that you have the relevant privileges to run the command, so in this case you need to be able to log into the database and have write access to 'tablename'. Postgres also needs to be able to reach the file, so the path /home/uploads/ should be accessible on the database server and the postgres user should be able to read the file - check the permissions to the file and directory.

Please refer to the PostgreSQL manual for COPY. Note the versions across the top; click on 8.3 for docs that apply to your version of Pg.

In pgAdmin (or the sql string you pass via a script or other db connection) you would just use COPY with no "" prefix.

so enter something like : COPY tablename....

You need to make sure that you have the relevant privileges to run the command, so in this case you need to be able to log into the database and have write access to 'tablename' Postgres also needs to be able to reach the file, so the path /home/uploads/ should be accessible on the database server and the postgres user should be able to read the file - check the permissions to the file and directory.

Please refer to the postgres manual for COPY.

In pgAdmin (or the sql string you pass via a script or other db connection) you would just use COPY with no "" prefix.

so enter something like : COPY tablename....

You need to make sure that you have the relevant privileges to run the command, so in this case you need to be able to log into the database and have write access to 'tablename'. Postgres also needs to be able to reach the file, so the path /home/uploads/ should be accessible on the database server and the postgres user should be able to read the file - check the permissions to the file and directory.

Linked to current manual version; links to old versions tend to clutter Google results after a while
Source Link

Please refer to the postgres manualPostgreSQL http://www.postgresql.org/docs/8.1/static/sql-copy.htmlmanual for COPY. Note the versions across the top; click on 8.3 for docs that apply to your version of Pg.

In pgAdmin (or the sql string you pass via a script or other db connection) you would just use COPY with no "" prefix.

so enter something like : COPY tablename....

You need to make sure that you have the relevant privileges to run the command, so in this case you need to be able to log into the database and have write access to 'tablename' Postgres also needs to be able to reach the file, so the path /home/uploads/ should be accessible on the database server and the postgres user should be able to read the file - check the permissions to the file and directory.

Please refer to the postgres manual http://www.postgresql.org/docs/8.1/static/sql-copy.html.

In pgAdmin (or the sql string you pass via a script or other db connection) you would just use COPY with no "" prefix.

so enter something like : COPY tablename....

You need to make sure that you have the relevant privileges to run the command, so in this case you need to be able to log into the database and have write access to 'tablename' Postgres also needs to be able to reach the file, so the path /home/uploads/ should be accessible on the database server and the postgres user should be able to read the file - check the permissions to the file and directory.

Please refer to the PostgreSQL manual for COPY. Note the versions across the top; click on 8.3 for docs that apply to your version of Pg.

In pgAdmin (or the sql string you pass via a script or other db connection) you would just use COPY with no "" prefix.

so enter something like : COPY tablename....

You need to make sure that you have the relevant privileges to run the command, so in this case you need to be able to log into the database and have write access to 'tablename' Postgres also needs to be able to reach the file, so the path /home/uploads/ should be accessible on the database server and the postgres user should be able to read the file - check the permissions to the file and directory.

deleted 3 characters in body
Source Link
user1822
user1822

Please refer to the postgres manual http://www.postgresql.org/docs/8.1/static/sql-copy.html.

In pgAdmin (or the sql string you pass via a script or other db connection) you would just use COPY with no "" prefix.

so enter something like : COPY tablename....

You need to make sure that you have the relevant privileges to run the command, so in this case you need to be able to log into the database and have write access to 'tablename' PostgressPostgres also needs to be able to reach the file, so the path /home/uploads/ should be accessible on the database server and the postgres user should be able to read the file - check the permissions to the file and directory.

Please refer to the postgres manual http://www.postgresql.org/docs/8.1/static/sql-copy.html.

In pgAdmin (or the sql string you pass via a script or other db connection) you would just use COPY with no "" prefix.

so enter something like : COPY tablename....

You need to make sure that you have the relevant privileges to run the command, so in this case you need to be able to log into the database and have write access to 'tablename' Postgress also needs to be able to reach the file, so the path /home/uploads/ should be accessible on the database server and the postgres user should be able to read the file - check the permissions to the file and directory.

Please refer to the postgres manual http://www.postgresql.org/docs/8.1/static/sql-copy.html.

In pgAdmin (or the sql string you pass via a script or other db connection) you would just use COPY with no "" prefix.

so enter something like : COPY tablename....

You need to make sure that you have the relevant privileges to run the command, so in this case you need to be able to log into the database and have write access to 'tablename' Postgres also needs to be able to reach the file, so the path /home/uploads/ should be accessible on the database server and the postgres user should be able to read the file - check the permissions to the file and directory.

Source Link
adam f
  • 674
  • 3
  • 3
Loading