[GRASS-dev] [GRASS GIS] #3167: db.connect: connection to remote database does not work
GRASS GIS
trac at osgeo.org
Mon Sep 26 06:32:36 PDT 2016
#3167: db.connect: connection to remote database does not work
-----------------------------------+-------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.5
Component: Database | Version: unspecified
Keywords: postgresql db.connect | CPU: Unspecified
Platform: Unspecified |
-----------------------------------+-------------------------
In a freshly compiled 70release:
{{{
createdb -h myRemoteServer testgrass
grass70 -c /data/GRASS/DATA7/nc_spm_08/postgres_test
db.connect driver=pg database="host=myRemoteServer,dbname=testgrass"
> db.tables -p
DBMI-PostgreSQL erreur de pilote :
Connection failed.
FATAL: la base de données « testgrass » n'existe pas
DBMI-PostgreSQL erreur de pilote :
Connection failed.
FATAL: la base de données « testgrass » n'existe pas
ERREUR :Unable to open database
<host=myRemoteServer,dbname=testgrass>
}}}
and
{{{
> g.copy vect=boundary_county,bc
Copy vector <boundary_county at PERMANENT> to current mapset as <bc>
DBMI-PostgreSQL driver error:
Connection failed.
FATAL: la base de données « testgrass » n'existe pas
DBMI-PostgreSQL driver error:
Connection failed.
FATAL: la base de données « testgrass » n'existe pas
WARNING: Unable to open database
<host=myRemoteServer,dbname=testgrass> by driver
<pg>
no database is open
no database is open
WARNING: Unable to copy table <bc>
WARNING: Unable to copy table <boundary_county> for layer 1 from
<boundary_county at PERMANENT> to <bc>
}}}
but
{{{
> psql -h myRemoteServer -l | grep testgrass
testgrass | mlennert | UTF8 | C | C |
}}}
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3167>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list