Re: [GENERAL] Out Of Memory Error on GiST Index
On Thu, 1 Sep 2005, James Cradock wrote: Hello. I'm getting an Out Of Memory error when I try to create a GiST index on a geometry column (PostGIS) with approximately 33,000,000 rows. I can truncate the data in the table, create the GiST index on the empty table, but when I try to reload the data via pg_restore I get the error. I get the error also if I try creating the GiST index on the table with the 33,000,000 rows. Are there limitations with the GiST index? Has anyone seen this? AFAIK, no. Perhaps, it's PostGIS problem ? It'd be nice to build rtree index using contrib/rtree_gist to see if problem in GiST. Thanks. Jim - James Cradock, [EMAIL PROTECTED] - James Cradock, [EMAIL PROTECTED] me3 Technology Consultants, LLC 24 Preble Street, 2nd Floor Portland, ME 04101 207-772-3217 (office) 207-838-8678 (mobile) www.me3.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq Regards, Oleg _ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [GENERAL] Out Of Memory Error on GiST Index
Thanks. I'm using PostgreSQL 8.0.2. On Sep 1, 2005, at 6:35 AM, Richard Huxton wrote: James Cradock wrote: Hello. I'm getting an Out Of Memory error when I try to create a GiST index on a geometry column (PostGIS) with approximately 33,000,000 rows. I can truncate the data in the table, create the GiST index on the empty table, but when I try to reload the data via pg_restore I get the error. I get the error also if I try creating the GiST index on the table with the 33,000,000 rows. Are there limitations with the GiST index? Has anyone seen this? I seem to remember mention of memory-leak fixes being applied to the GiST code not too long back - might be worth checking the archives for the bug/hackers list. -- Richard Huxton Archonet Ltd - James Cradock, [EMAIL PROTECTED] me3 Technology Consultants, LLC 24 Preble Street, 2nd Floor Portland, ME 04101 207-772-3217 (office) 207-838-8678 (mobile) www.me3.com ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [GENERAL] Out Of Memory Error on GiST Index
James Cradock wrote: Hello. I'm getting an Out Of Memory error when I try to create a GiST index on a geometry column (PostGIS) with approximately 33,000,000 rows. I can truncate the data in the table, create the GiST index on the empty table, but when I try to reload the data via pg_restore I get the error. I get the error also if I try creating the GiST index on the table with the 33,000,000 rows. Are there limitations with the GiST index? Has anyone seen this? I seem to remember mention of memory-leak fixes being applied to the GiST code not too long back - might be worth checking the archives for the bug/hackers list. -- Richard Huxton Archonet Ltd ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[GENERAL] Out Of Memory Error on GiST Index
Hello. I'm getting an Out Of Memory error when I try to create a GiST index on a geometry column (PostGIS) with approximately 33,000,000 rows. I can truncate the data in the table, create the GiST index on the empty table, but when I try to reload the data via pg_restore I get the error. I get the error also if I try creating the GiST index on the table with the 33,000,000 rows. Are there limitations with the GiST index? Has anyone seen this? Thanks. Jim - James Cradock, [EMAIL PROTECTED] - James Cradock, [EMAIL PROTECTED] me3 Technology Consultants, LLC 24 Preble Street, 2nd Floor Portland, ME 04101 207-772-3217 (office) 207-838-8678 (mobile) www.me3.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq