From: Paul Ramsey <pramsey@cleverelephant.ca>
Date: Wed, 16 Mar 2011 19:16:54 +0000 (+0000)
Subject: Jeff Adams: Updated man page for -X, -T, and -e parameters (#110 and #67).
X-Git-Tag: 2.0.0alpha1~1889
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7a85a4763ae5c863b268fe842ab2d7da0d84db16;p=postgis

Jeff Adams: Updated man page for -X, -T, and -e parameters (#110 and #67).


git-svn-id: http://svn.osgeo.org/postgis/trunk@6913 b70326c6-7e19-0410-871a-916f4a2858ee
---

diff --git a/doc/man/shp2pgsql.1 b/doc/man/shp2pgsql.1
index e6c80cd03..ca293f5dd 100644
--- a/doc/man/shp2pgsql.1
+++ b/doc/man/shp2pgsql.1
@@ -53,6 +53,12 @@ Use the PostgreSQL "dump" format for the output data. This can be combined
 with -a, -c and -d. It is much faster to load than the default "insert" SQL
 format. Use this for very large data sets.
 .TP 
+\fB\-e\fR
+Execute each statement on its own, without using a transaction.
+This allows loading of the majority of good data when there are some bad
+geometries that generate errors.  Note that this cannot be used with the
+-D flag as the "dump" format always uses a transaction.
+.TP 
 \fB\-s\fR <\fISRID\fR>
 Creates and populates the geometry tables with the specified SRID.
 .TP 
@@ -74,11 +80,6 @@ MULTILINESTRINGs by default. This switch will produce LINESTRINGs instead,
 but shp2pgsql will fail when it hits a real MULTILINESTRING. The same works
 for POLYGONs vs. MULTIPOLYGONs.
 .TP 
-\fB\-w\fR
-Output WKT format, for use with older (0.x) versions of PostGIS.
-Note that this will introduce coordinate drifts and will drop
-M values from shapefiles.
-.TP 
 \fB\-W\fR <\fIencoding\fR>
 Specify the character \fIencoding\fR of Shapefile's attributes.
 If this option is used the output will be encoded in UTF-8.
@@ -89,6 +90,15 @@ Create a GiST index on the geometry column.
 \fB\-N\fR <\fIpolicy\fR>
 Specify NULL geometries handling policy (insert,skip,abort).
 .TP 
+\fB\-T\fR <\fItablespace\fR>
+Specify the tablespace for the new table.  Indexes will still use the
+default tablespace unless the -X parameter is also used.  The PostgreSQL
+documentation has a good description on when to use custom tablespaces.
+.TP 
+\fB\-X\fR <\fItablespace\fR>
+Specify the tablespace for the new table's indexes.  This applies to
+the primary key index, and the GIST spatial index if -I is also used.
+.TP 
 \fB\-?\fR
 Display version and usage information.