<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 2012-07-03, at 1:43 PM, Mark Cave-Ayland wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 03/07/12 12:34, René Fournier wrote:<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">If I quit and restart psql, same error occurs. Only if I drop the table<br></blockquote><blockquote type="cite">can I insert more rows — but again, only up to around 300 rows or 100 kb<br></blockquote><blockquote type="cite">(not sure where the limit is)... So, it's not dependent on the kind of<br></blockquote><blockquote type="cite">coordinates or row data, just the number of inserts and/or the amount of<br></blockquote><blockquote type="cite">data. Any ideas what is causing the problem here?<br></blockquote><br>Strange - from what you're saying, it sounds as if it could be to do with the index splitting code, but without a backtrace (<a href="http://trac.osgeo.org/postgis/wiki/DevWikiGettingABackTrace">http://trac.osgeo.org/postgis/wiki/DevWikiGettingABackTrace</a>) it's tricky to say exactly.<br><br>One small nit - I notice you've got a geography column but you're using ST_GeomFromText() rather than ST_GeogFromText() which is likely introducing an extra cast somewhere. Does changing to ST_GeogFromText() help prevent the crash at all?<br></div></blockquote></div><br><div>Hi Mark,</div><div>Thanks for the tip... I changed to GeogFromText(), but the error/crash still occurs, at the same point... After the crash, here's what the tables look like:</div><div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div> List of relations</div></div><div><div> Schema | Name | Type | Owner | Size | Description </div></div><div><div>--------+--------------------+----------+----------+------------+-------------</div></div><div><div> public | accounts | table | postgres | 8192 bytes | </div></div><div><div> public | accounts_id_seq | sequence | postgres | 8192 bytes | </div></div><div><div> public | addresses | table | postgres | 96 kB | </div></div><div><div> public | addresses_id_seq | sequence | postgres | 8192 bytes | </div></div><div><div> public | geography_columns | view | postgres | 0 bytes | </div></div><div><div> public | geometry_columns | table | postgres | 8192 bytes | </div></div><div><div> public | languages | table | postgres | 8192 bytes | </div></div><div><div> public | languages_id_seq | sequence | postgres | 8192 bytes | </div></div><div><div> public | spatial_ref_sys | table | postgres | 3000 kB | </div></div><div><div> public | territories | table | postgres | 416 kB | </div></div><div><div> public | territories_id_seq | sequence | postgres | 8192 bytes | </div></div><div><div> public | users | table | postgres | 96 kB | </div></div><div><div> public | users_id_seq | sequence | postgres | 8192 bytes | </div></div><div><br></div></blockquote>Is it strange that the geography_columns view is 0 bytes? Even though both territories and addresses have a geography column (POLYGON and POINT respectively) and an associated GIST index?<div><br></div><div>...Rene</div><div><br></div><div><br><br></div></body></html>