<div>
hi guys,
</div><div>thanks for the feedback.</div><div><br></div><div>i installed the latest GEOS + POSTGIS and now it works!</div><div><br></div><div>thank your very much :-)</div>
<div><br>-- <br>Martin Güther<br><br></div>
<p style="color: #A0A0A8;">Am Sonntag, 23. Oktober 2011 um 21:14 schrieb Paragon Corporation:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>
<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 9.00.8112.16437">
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial">Martin,</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial">Can't remember last time I had that error, but Ihave seen it
before.</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial">I think the cause is one of two reasons</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial">Corrupted location on disk -- usually involving a geometry
record. That is a pain to figure out. I think I ended up doing
limits to find the bad record and then deleted it or relaoaded the table
skipping that record. That case usually screws up your backup so you can
tell if your backups are failing if this is the issue since the backup would try
to traverse the record and fail with a bad alloc.</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial">or</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial">Bad geometry that causes infinite memory
allocation.</font></span></div>
<div><span><font color="#0000ff" size="2" face="Arial"></font></span> </div>
<div><span><font color="#0000ff" size="2" face="Arial">You
might want to try upgrading your PostGIS to latest 1.4 minor (1.4.0 is not the
latest stable release of 1.4)</font></span></div>
<div><span><font color="#0000ff" size="2" face="Arial"></font></span> </div>
<div><span><font color="#0000ff" size="2" face="Arial">You
might also want to upgrade your Geos. I would try to go to 3.2.3 if at all
possible. I think several memory issues were fixed in 3.2 and may not have
been back-ported to 3.1 because the code changed too much.</font></span></div>
<div><span><font color="#0000ff" size="2" face="Arial">Strk
might have a better idea.</font></span></div>
<div><span><font color="#0000ff" size="2" face="Arial"></font></span> </div>
<div><span><font color="#0000ff" size="2" face="Arial">Hope
that helps,</font></span></div>
<div><span><font color="#0000ff" size="2" face="Arial">Regina</font></span></div>
<div><span><font color="#0000ff" size="2" face="Arial"><a href="http://www.postgis.us">http://www.postgis.us</a></font></span></div>
<div><span><font color="#0000ff" size="2" face="Arial"></font></span> </div>
<div><span><font color="#0000ff" size="2" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><br></div><blockquote type="cite"><div>
<div dir="ltr" lang="en-us" align="left">
<hr tabindex="-1">
<font size="2" face="Tahoma"><b>From:</b>
postgis-users-bounces@postgis.refractions.net
[<a href="mailto:postgis-users-bounces@postgis.refractions.net">mailto:postgis-users-bounces@postgis.refractions.net</a>] <b>On Behalf Of
</b>Martin Güther<br><b>Sent:</b> Sunday, October 23, 2011 7:03
AM<br><b>To:</b> <a href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</a><br><b>Subject:</b>
[postgis-users] memory bug in postgis query<br></font><br></div>
<div><span style="FONT-SIZE: 13px">Hi guys,<br>i
recently asked the same question on the postgresql mailing list but they
forwarded me to this mailing list.</span></div>
<div><span style="FONT-SIZE: 13px">I really hope you
can help me :)</span></div>
<div><br></div>
<div><span style="FONT-SIZE: 13px">on a test maschine
from my university i'm running into a weird problem (i attached detail
info):<br><br>A running postgis query eats more and more memory.(seen in
htop) </span></div>
<div><span style="FONT-SIZE: 13px">It'll
start using virtual memory and after eating up that one, too, postgres
will<br>crash with:<br><br>psql:/home/mguether/sql/benchmark.sql:6: NOTICE:
std::bad_alloc<br>psql:/home/mguether/sql/benchmark.sql:6: ERROR:
GEOS intersects()<br>threw an error!<br><br>once it gave me
an<br>psql:/home/mguether/sql/benchmark.sql:6: ERROR: out of
memory<br>DETAIL: Failed on request of size 182949.<br><br>after the
crash, all memory/swap is free again, so it really is postgres :)<br><br>i
don't really know how to debug it any more detailed or fix this<br>issue in
any way.<br><br>Does anyone here have a hint, where the issue might
be?<br><br>thanks,<br></span><span style="FONT-SIZE: 13px">martin<br><br><br><br><br><br><br><br>here some
information:<br><br>the maschine:<br>16 GB RAM, i7 4cores x64
2.6.32-21-server ubuntu<br><br>installed postgres:<br>psql (PostgreSQL)
8.4.9<br>including postgis<br>POSTGIS="1.4.0" GEOS="3.1.0-CAPI-1.5.0"
PROJ="Rel. 4.7.1, 23 September<br>2009" USE_STATS<br><br>i changed two
parameters from the default config:<br>shared_buffers = 512MB<br>work_mem =
256MB<br><br>using osm2pgsql I important some GEO data, and want to execute
this query:<br><br>SELECT a.osm_id, w.osm_id FROM "planet_osm_line"
w,<br>"planet_osm_polygon" a WHERE ST_Intersects(w.way,a.way) AND
w.highway<br>IS NOT NULL;<br><br>the EXPLAIN gives me:<br><br>Nested Loop
(cost=0.00..26427424.16 rows=1511021 width=8)<br> Join Filter:
_st_intersects(w.way, a.way)<br> -> Seq Scan on planet_osm_line
w (cost=0.00..49213.10<br>rows=1137488 width=837)<br>
Filter: (highway IS NOT NULL)<br> -> Index Scan
using osm_areas_index on planet_osm_polygon a<br>(cost=0.00..23.10 rows=6
width=824)<br> Index Cond: (w.way &&
a.way)<br>(6 rows)</span></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><span style="FONT-SIZE: 13px"><br></span></div>
</div></blockquote></div><div>_______________________________________________<br>postgis-users mailing list<br><a href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</a><br><a href="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis.refractions.net/mailman/listinfo/postgis-users</a><br></div></div></span>
</blockquote>
<div>
<br>
</div>