[prev in list] [next in list] [prev in thread] [next in thread]
List: postgis-users
Subject: Re: [postgis-users] Re:pgsql2shp
From: "Tyler Mitchell" <TMitchell () lignum ! com>
Date: 2002-09-16 15:40:33
Message-ID: OF6DBF4A1D.654EE85B-ON88256C36.00560031-88256C36.005618CE () lignum ! com
[Download RAW message or body]
You can add "-o -i" to add the same option using pg_ctl. Since me startup
script uses pg_ctl this was the only solution for me :)
Tyler
\
Guido Staub \
<staub@gik.uni-karlsruhe.de> To: \
postgis-users@postgis.refractions.net
Sent by: cc: \
postgis-users-admin@postgis.refr Fax to: \
actions.net Subject: Re: \
[postgis-users] Re:pgsql2shp
\
\
09/16/2002 01:40 AM \
Please respond to postgis-users \
\
\
OK, I've got it. My problem was that I've started the postmaster with the
pg_ctl script but here I couldn't set the -i flag. So now I'm starting the
postmaster with the postmaster file and here it works fine.
Thanks to all.
Guido
Chris Hodgson schrieb:
The command 'psql -d db' DOES NOT use TCP/IP sockets to connect to
the db, it uses unix sockets (by default). Whereas, pgsql2shp DOES
use TCP/IP sockets. Therefore, the advice that David Garnier gave
you, still stands. Check your config, or start your database with the
-i flag to allow tcp connections. Chris
----- Original Message -----
From: Guido Staub
To: postgis-users@postgis.refractions.net
Sent: Friday, September 13, 2002 6:21 AM
Subject: [postgis-users] Re:pgsql2shp
What I wanted to say is, that
shp2pgsql shapefile table db | psql -d db
is running fine and uploading data is no problem. I don't get an
error message about any TCP/IP problems.
So my problem still exists, that I can't get my data out of the
table into a shapefile.
Reading the Online Doc there should not be a problem using the
dumper. It's only the
pgsql2shp [<options>] <database> <table>
command from the commandline, isn't it?
Thanks
Guido
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic