<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6001.18148" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>Balkan,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>I guess the error is being caused by the extra geometry
validation we are doing, though I thought it was set to not validate copy
.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>One way to fix the error now you are back in the old
PostGIS, is bring up the problem table and do an ST_IsValid check on the
geometries</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>something like</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>SELECT count(*)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>FROM badtable WHERE ST_IsValid(the_geom) =
false</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>The notice section should give listing of bad
geoms. That below one you have is pretty bad basically means you have a
line or polygon that does not have enough points to be a line or polygon.
Then youcan delete them or fix them.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>As far as these tiny upgrades go a dump restore is in
general not necessary - my general approach</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>1) Backup db as you have done (as a precautionary
measure).</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>2) Do a yum upgrade (if you are using CentOS, Fedora or
Red Hat, the new PostgreSQL YUM repository is pretty good and always has the
latest and greatest PostgreSQL builds)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008> (different depending on OS) -- sort of described
here - - <A
href="http://www.postgresonline.com/journal/index.php?/archives/60-YUM-2-Almost-Idiots-Guide-to-upgrade-from-PostgreSQL-8.3.1-to-8.3.3.html">http://www.postgresonline.com/journal/index.php?/archives/60-YUM-2-Almost-Idiots-Guide-to-upgrade-from-PostgreSQL-8.3.1-to-8.3.3.html</A></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008><A
href="http://www.postgresonline.com/journal/index.php?/archives/45-An-Almost-Idiots-Guide-to-PostgreSQL-YUM.html">http://www.postgresonline.com/journal/index.php?/archives/45-An-Almost-Idiots-Guide-to-PostgreSQL-YUM.html</A></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>3) Recompile and install latest
PostGIS.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008>4) reindex tables if necessary.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=024265023-15112008></SPAN></FONT> </DIV><FONT face=Arial
color=#0000ff size=2></FONT><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
postgis-users-bounces@postgis.refractions.net
[mailto:postgis-users-bounces@postgis.refractions.net] <B>On Behalf Of
</B>Balkan Uraz<BR><B>Sent:</B> Saturday, November 15, 2008 3:43
AM<BR><B>To:</B> postgis-users@postgis.refractions.net<BR><B>Cc:</B>
volkany@mobiliz.com.tr<BR><B>Subject:</B> [postgis-users] Postgre 8.3.5 &
PostGIS SVN 2008-11-13 Updates<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Dear All;</DIV>
<DIV> </DIV>
<DIV>We have been informed that Postgre 8.3.5 Update is critical for especially
GIST indexes. Therefore we decided to upgrade both Postgre & PostGIS.</DIV>
<DIV> </DIV>
<DIV>We have backed up our system:</DIV>
<UL>
<LI>Postgre 8.3.3
<LI>PostGIS 2008-10-08 SVN
<LI>PROJ.4 SVN
<LI>GEOS 3.0.0</LI></UL>
<DIV>We have then, upgraded to 8.3.5 Update for Postgre and 2008-11-13
SVN for PostGIS. However, we were not successful to restore our data back
in some tables. The error was:</DIV>
<DIV> </DIV>
<DIV>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"><FONT
face="courier new,monospace">ERROR:<SPAN style="mso-spacerun: yes">
</SPAN>geometry requires more points</FONT></P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"><FONT
face="courier new,monospace"><SPAN style="mso-spacerun: yes">
</SPAN>HINT:<SPAN style="mso-spacerun: yes">
</SPAN>"...000100000003000000E71A66683C954F40018926" <-- parse error at
position 74 within geometry</FONT></P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"><FONT
face="courier new,monospace"><SPAN style="mso-spacerun: yes">
</SPAN>CONTEXT:<SPAN style="mso-spacerun: yes"> </SPAN>COPY
dunyayerlesimalanlari, line 12024, column the_geom:
"0106000020E61000000100000001030000000100000003000000E71A66683C954F4001892650C4184B40BF45274BAD934F40..."</FONT></P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"><FONT
face="courier new,monospace"><SPAN style="mso-spacerun: yes">
</SPAN>STATEMENT:<SPAN style="mso-spacerun: yes"> </SPAN>COPY
dunyayerlesimalanlari (gid, name, featype, the_geom) FROM stdin;</FONT></P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"><FONT
face="Courier New"></FONT> </P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"><FONT
face=arial,helvetica,sans-serif>We couldn't find a way, therefore we reverted
all our system back to 8.3.3 and PostGIS 2008-10-08 SVN .</FONT></P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"> </P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt">Do you have any ideas on the
error? How could we resolve that error?</P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"> </P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt">Also, not specific for this
error; is there any predefined procedures for updating the Postgre & PostGIS
instances?</P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"> </P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt">Thanks for your help,</P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"> </P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt">Regards,</P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"> </P>
<P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt">Balkan
Uraz.</P></DIV></BODY></HTML>