Richard,
Move the "data" directory to a new device, and then in
postgresql.conf, alter the location of the default data space to that
location.
P
On 13-Dec-07, at 7:37 AM, Richard Heimann [C] wrote:
This question is more to do with PostgreSQL then PostGIS but I’ve
always gotten good response on this forum and so I’m going back to
the well.
After a recent load, I received the following error, “…No space
left on device SQL State 53100 Hint: Check free Disk Space.” This
error is fairly self-explanatory but I don’t know how to approach
the problem. In SQL server I would simple stop autogrowth on a file
group, create a new file group on a larger partition and be done or
alternately attached/detach the database onto new partition and
begin work again. My point is there are several ways but Im new to
PostrgeSQL and Im curious - what’s the best practice. I believe all
the data is in the installation directory <data> folder. Can I
simply move this folder and somehow reattach? Thanks in advance, Rich
From: Gregory Williamson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 11, 2007 7:48 PM
To: [EMAIL PROTECTED]; PostGIS Users Discussion; Michael
Smedberg; [EMAIL PROTECTED]; PostGIS Users Discussion
Subject: RE: [postgis-users] HELP adding spatial field to table
I think it is rare that you'd want corrupt data. My usual approach
has been to load my data set into a temporary table (only lasts for
the session (or transaction)) and then apply sanity checks and
either delete offending rows or modify them if you know sane values
to set them to.
Then create the geometries from the data set and insert it into my
real table, possibly with something like
INSERT INTO some_real_table SELECT gid,label_name,the_geom FROM
foo WHERE IsValid(the_geom);
HTH,
Greg W.
(sorry for top-posting, challenged reader and pressed for time)
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of
Richard Heimann [C]
Sent: Tue 12/11/2007 4:57 PM
To: 'Michael Smedberg'; [EMAIL PROTECTED]; 'PostGIS
Users Discussion'
Subject: RE: [postgis-users] HELP adding spatial field to table
Thanks for the prompt response. And youre right there are some such
values.
Is there a work around?
Rich
-----Original Message-----
From: Michael Smedberg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 11, 2007 6:55 PM
To: [EMAIL PROTECTED]; PostGIS Users Discussion
Subject: RE: [postgis-users] HELP adding spatial field to table
Are you sure that x and y always have legit values? If one were
null or
the zero-length string, I think you'd get an error like that.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Richard Heimann [C]
Sent: Tuesday, December 11, 2007 3:44 PM
To: 'PostGIS Users Discussion'
Subject: [postgis-users] HELP adding spatial field to table
All,
Im getting some strange behavior that I cant explain and sadly know
its
likely trivial. My pursuit is simple, add a spatial filed to a table
containing x,y.
First. AddGeometryColumn
SELECT AddGeometryColumn( 'crimetest', 'geom', 4326,
'POINT', 2)
Next (and where the trouble lies)
UPDATE crimetest
SET geom = PointFromText('POINT(' || x || ' ' || y || ')',
4326)
This is the error I receive.
ERROR: Invalid OGC WKT (too short)
SQL state: XX000
Context: SQL function "geomfromtext" statement 1
SQL function "pointfromtext" statement 1
Can anyone shed some light on this?
Thanks
Rich
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
