> Using -Xmx512m allows the upload, but it seems a lot of 
> memory for a 9.5 Mb file. As expected, memory requirements 
> increase if you need a 20 Mb file etc. We will routinely 
> upload even larger files, so using high -Xmx values isn't 
> really a solution. Additionally, a 9.5 Mb upload under Tomcat 
> does not cause the error when using an older (circa Jan 04 
> CVS) Postgres JAR version. More recent JAR versions fail with 
> much smaller uploads.

For the benefit of those searching the archives in the future, the solution
was to use Postgres' Large Object support (PG_LARGEOBJECT) rather than BYTEA
columns in VERSION_CONTENT. This dramatically decreased memory usage as well
as increased efficiency in terms of PUT method processing time. It makes
using Postgres viable with large files (tested PUTting 100 Mb files with
modest RAM usage).

In relation to my other email re search integration, I ended up using
Postgres' tsearch2 module along with some stored procedures to successfully
index content.

Best regards
Ben


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to