Обсуждение: JDBC driver inserting into a table with Bytea type gets out of me mory error.
JDBC driver inserting into a table with Bytea type gets out of me mory error.
There was a posting in the mailing list archives that I can't find anymore. The web site right now is presenting a list of items from a search in a reasonable amount of time, but takes 5-10 minutes to retrieve the detail for each one as they are clicked. Rather frustrating.
This person was getting out of memory conditions inserting rows when the data in the bytea field was larger than approx. 1400 Kb. This person had posted a fix to the group that seemed to work for him. The inserts were coming from a java application using the JDBC driver.
I just tried the latest JDBC driver and the problem still exists. We have no plans to convert to using the large object interface. This ties our code to PostgreSQL and would go against our need to keep the code generic enough to work against many different databases.
Is this issue acknowledged as a bug?
If yes, when is this issue going to be implemented in the code base?
If it is already fixed, what are the steps to implement the changes to my 7.4.2 installation? Build my own JDBC driver?
Denis, You will get better search results using google just append site:postgresql.org to your search terms Dave On Mon, 2004-06-21 at 12:44, Sailer, Denis (YBUSA-CDR) wrote: > There was a posting in the mailing list archives that I can't find > anymore. The web site right now is presenting a list of items from a > search in a reasonable amount of time, but takes 5-10 minutes to > retrieve the detail for each one as they are clicked. Rather > frustrating. > > > > This person was getting out of memory conditions inserting rows when > the data in the bytea field was larger than approx. 1400 Kb. This > person had posted a fix to the group that seemed to work for him. The > inserts were coming from a java application using the JDBC driver. > > > > I just tried the latest JDBC driver and the problem still exists. We > have no plans to convert to using the large object interface. This > ties our code to PostgreSQL and would go against our need to keep the > code generic enough to work against many different databases. > > > > Is this issue acknowledged as a bug? > > If yes, when is this issue going to be implemented in the code base? > > If it is already fixed, what are the steps to implement the changes to > my 7.4.2 installation? Build my own JDBC driver? > > > > > !DSPAM:40d71228141141400527835! -- Dave Cramer 519 939 0336 ICQ # 14675561
On Mon, 21 Jun 2004, Sailer, Denis (YBUSA-CDR) wrote: > This person was getting out of memory conditions inserting rows when the > data in the bytea field was larger than approx. 1400 Kb. This person had > posted a fix to the group that seemed to work for him. The inserts were > coming from a java application using the JDBC driver. > I just tried the latest JDBC driver and the problem still exists. > Is this issue acknowledged as a bug? It is more of a missing feature, "the ability to stream large data to the backend." > If yes, when is this issue going to be implemented in the code base? There is an outstanding patch by Oliver Jowett, but I have some concerns about how it handles errror conditions (it will just drop the connection in some cases.) > If it is already fixed, what are the steps to implement the changes to my > 7.4.2 installation? Build my own JDBC driver? When/if it is applied it will go only into the 7.5 source tree so you can use that against your 7.4 server, but for the moment your only option is to build your own version of the driver. The original patch/discussion is here: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&c2coff=1&safe=off&threadm=Pine.BSO.4.56.0405251012470.21539%40leary.csoft.net&rnum=1&prev=/&frame=on Kris Jurka