On Tue, 30 Oct 2018, Rich Shepard wrote:
Trying to run db.copy to add attribute tables to the database (except for
one that is already present) using a script with commands like this:
Markus M./Moritz:
All fixed now. There was an issue with the postgres upgrade from 9.x to
10.x (a long time
On Wed, 31 Oct 2018, Moritz Lennert wrote:
try
psql -h 127.0.0.1 willamette-river-hg
Does this work ?
Moritz,
I've uncovered a postgres glitch: it's looking for libpq.so.5 in a
postgresql/10.2/ rather than in the 10.3/ directory. I'm looking for the the
wrong pointer now. Will fix that be
On 31/10/18 16:49, Rich Shepard wrote:
On Wed, 31 Oct 2018, Moritz Lennert wrote:
This sounds like Stefan might be on the right path: are you sure your
Postgresql server accepts connections from the network ? What is
'listen_addresses' set to in your postgresql.conf ? And is password
authentica
On Wed, 31 Oct 2018, Moritz Lennert wrote:
This sounds like Stefan might be on the right path: are you sure your
Postgresql server accepts connections from the network ? What is
'listen_addresses' set to in your postgresql.conf ? And is password
authentication enabled in pg_hba.conf ?
Moritz,
On 31/10/18 15:56, Rich Shepard wrote:
On Wed, 31 Oct 2018, Moritz Lennert wrote:
You database seems to be called 'willamette-river-hg', i.e. all hyphens,
whereas you are trying to db.copy to 'willamette_river_hg', i.e. one
hyphen, one underscore.
Moritz,
Thank you. I use hyphens in mult
The reason I ask is because you have to configure authentication and enable
remote access to connect to the database from an application. For me I had to
do that to use PG with GRASS.
psql connects via trusted connection because user postgres connects to the DB
from local machine. Postgres conne
On Wed, 31 Oct 2018, st_kie...@web.de wrote:
is it possible to connect to the DB with PGAdmin?
Stefan,
I don't run pgadmin.
The database is on this host, a server/workstation desktop. The postgres
shell has no problems connecting to any database (they're all owned by me).
For example:
$
On Wed, 31 Oct 2018, Moritz Lennert wrote:
You database seems to be called 'willamette-river-hg', i.e. all hyphens,
whereas you are trying to db.copy to 'willamette_river_hg', i.e. one
hyphen, one underscore.
Moritz,
Thank you. I use hyphens in multi-word file names while applications such
Hi,
is it possible to connect to the DB with PGAdmin?
Resp. is remote access enabled?
see
https://blog.bigbinary.com/2016/01/23/configure-postgresql-to-allow-remote-connection.html
https://www.postgresql.org/docs/9.1/static/auth-pg-hba-conf.html
Regards.
Stefan
> Rich Shepard hat am 31. Oktob
On 30/10/18 22:37, Rich Shepard wrote:
On Tue, 30 Oct 2018, Rich Shepard wrote:
I was thinking of working within grass rather than at the bash prompt.
You're right: I know the difference between double and single quotes but
blew it on this instance.
I'm still missing something.
From
On Wed, 31 Oct 2018, Markus Metz wrote:
try to set host and port with db.login. Username and password are not
required if a ~/.pgpass file exists. See the manual of db.login, following
the link to PostgreSQL that describes the GRASS PG driver.
Markus M,
Here ~/.pgpass contains host, port, *
On Tue, Oct 30, 2018 at 10:54 PM Rich Shepard
wrote:
>
> On Tue, 30 Oct 2018, Markus Metz wrote:
>
> > db.connect only sets the default database, it does not test if it exists
> > or is accessible. For PG, you need to use db.login first in order to
> > actually use the PG database.
>
> Markus M,
>
Running db.test also fails:
db.test test=test1
Using DB driver: pg
CREATE TABLE grass_test1 (i1 INTEGER, d1 DOUBLE PRECISION, c1 VARCHAR(20))
DBMI-PostgreSQL driver error:
Connection failed.
FATAL: database "willamette_river_hg" does not exist
How do I find where grass is looking for the
On Tue, 30 Oct 2018, Markus Metz wrote:
db.connect only sets the default database, it does not test if it exists
or is accessible. For PG, you need to use db.login first in order to
actually use the PG database.
Markus M,
Sigh. Neither without or with a username it still fails:
db.login d
On Tue, Oct 30, 2018 at 10:37 PM Rich Shepard
wrote:
>
> On Tue, 30 Oct 2018, Rich Shepard wrote:
>
> > I was thinking of working within grass rather than at the bash prompt.
> > You're right: I know the difference between double and single quotes but
> > blew it on this instance.
>
>I'm still
On Tue, 30 Oct 2018, Rich Shepard wrote:
WARNING: Unable to open database by driver
no database is open
no database is open
WARNING: Copy table failed
Oops! I forgot to include this information:
GRASS 7.7.svn (willamette_basin):~/data/grassdata/willamette_basin > db.connect
-p
driver: pg
On Tue, 30 Oct 2018, Rich Shepard wrote:
I was thinking of working within grass rather than at the bash prompt.
You're right: I know the difference between double and single quotes but
blew it on this instance.
I'm still missing something.
From the grass shell the command, db.connect driv
On Tue, 30 Oct 2018, Markus Metz wrote:
db.copy does not need db.connect. The reason for the error is that the
variable $HOME is not expanded because it is within single quotes. Use
double quotes instead of single quotes for the from_database argument and
it should work.
Markus,
I was think
On Tue, Oct 30, 2018 at 9:41 PM Rich Shepard
wrote:
>
>I started grass7.7.svn (r73623) and set db.connect to use driver=pg and
> database='willamette_river_hg'. Then I copied the vector files (g.copy
> vect=current_file,current_file_pg) per the migration instructions on the
> databaseintro man
I started grass7.7.svn (r73623) and set db.connect to use driver=pg and
database='willamette_river_hg'. Then I copied the vector files (g.copy
vect=current_file,current_file_pg) per the migration instructions on the
databaseintro manual page.
Trying to run db.copy to add attribute tables to t
20 matches
Mail list logo
