[GRASS-dev] db.login with postgresql and non standard port

Moritz Lennert mlennert at club.worldonline.be
Thu Mar 10 00:53:05 PST 2016


On 10/03/16 09:42, Luca Delucchi wrote:
> On 10 March 2016 at 09:10, Martin Landa <landa.martin at gmail.com> wrote:
>> Hi,
>>
>
> Hi,
>
>> 2016-03-10 9:01 GMT+01:00 Luca Delucchi <lucadeluge at gmail.com>:
>>> db.login -p
>>> sqlite|$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite.db|lucadelu|||
>>> sqlite|/grassdata,nc_spm_08,lucadelu,sqlite.db|lucadelu|||
>>
>> well, the lines are duplicated after substitution. I don't know, your
>> run command which defined db connection ones without and ones with
>> substitution. Ma
>>
>
> No, I donit think so. I just run
>
> db.connect driver=pg schema=public database=grassdata
> db.connect -p
>
> driver: pg
> database: grassdata
> schema: public
> group:
>
> db.login driver=pg database=grassdata user=lucadelu port=5433 host=localhost --o
> db.login -p
>
> sqlite|$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite.db|lucadelu|||
> sqlite|/grassdata,nc_spm_08,lucadelu,sqlite.db|lucadelu|||
> pg|host=localhost,dbname=pygrassdb_doctest|lucadelu|||
> pg|grassdata|lucadelu|||
>
> db.tables
>
> DBMI-PostgreSQL driver error:
> Connection failed.
> could not connect to server: No such file or directory
>          Is the server running locally and accepting
>          connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
>
>
> DBMI-PostgreSQL driver error:
> Connection failed.
> could not connect to server: No such file or directory
>          Is the server running locally and accepting
>          connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
>
>
> ERROR: Unable to open database <grassdata>
>
> So the port it is not stored, and also in db.login -p there is
> something strange with
>
> pg|host=localhost,dbname=pygrassdb_doctest|lucadelu|||
>
> where dbname=pygrassdb_doctest should be dbname=grassdata

Could this be "left-overs" from pre-grass71 ? How about erasing (or 
renaming $HOME/.grass7/dblogin) and trying again ?

Moritz


More information about the grass-dev mailing list