Please give more details :-) Sorry -kidding- just had to say that.
These are just the suggestions of another newbie. Take with grain of salt.
Do the easiest thing - kill the loader, drop the database, create the user,
create the database as geo_user and start again.
If you use geo_user to
Paul,
Thank you. postgres *is* still consuming CPU. In the meantime,
terminal has finally changed, outputting several more setval selects.
But it seriously had shown know change for 3-4 hours when I sent this
message.
Glad I didn't kill it and thanks for the info.
Best,
--Lee
On Wed, Aug 26,
New Linux machine, new PostGIS install (postgresql-9.3-postgis-2.1). I
created DB and added extensions. Now trying to load database using
postgis_restore.pl. This is a large database (63GB dump, created from
DB that was probably 600GB or more).
The script ran for a while. Then it stopped at
Best advice ever: Listen to PAUL not to BRIAN. :-)
I was also going to say what makes you think it stopped? Stop is usually
noisy and ends with a command prompt.
Does it load the tables then set ownership? That would be easy to fix later.
My own Q -- What would be a reasonable query to run to
The COPY command used to load tables is basically 100% silent, so it
just might have been working away. A good thing to check is 'top' to
see if the postgres process is busy using CPU. If so, it's hard at
work on your process. If not, then perhaps something is awry.
P
On Wed, Aug 26, 2015 at
As I recall, I think pg_stat_activity shows database restore work. So I would
run something like
SELECT * FROM pg_stat_activity WHERE datname='mydb';
Replacing mydb with your db.
From: postgis-users-boun...@lists.osgeo.org
[mailto:postgis-users-boun...@lists.osgeo.org] On
Christopher,
This is the wrong group to be asking this question. You want to be on the
pgRouting Users or pgRouting develop group. Join details here:
http://pgrouting.org/support.html
This question probably makes sense to ask on both pgRouting users and dev,
since it is both a
