Re: bytea size limit?
| От | Michael Privat |
|---|---|
| Тема | Re: bytea size limit? |
| Дата | |
| Msg-id | 1958959843.20040412211947@ceci.mit.edu обсуждение исходный текст |
| Ответ на | Re: bytea size limit? (Kris Jurka <books@ejurka.com>) |
| Ответы |
Re: bytea size limit?
|
| Список | pgsql-jdbc |
Here you go. Coded against the CVS HEAD. Let me know if you want me to change anything. Obviously, because I have to send the size ahead, there is no other way but store the entire byte[] in memory (can't stream), but with this code, I was able to load a blob of 30Mb+ (with a heap size of 32Mb) against 1.5Mb yesterday with the same heap. So there is some improvement. http://jupiter.incodea.com/trans/pgsql-jdbc.diff Michael Monday, April 12, 2004, 7:20:08 PM, you wrote: KJ> On Mon, 12 Apr 2004, Michael Privat wrote: >> Okay, I fixed the implementation of the BYTEA support in the driver >> based on your guidelines and it is very happy now. I want to clean >> up a few things before I do that, but what is the process for >> submitting a patch to the dev team? KJ> Make sure you are working against the cvs version of the driver, available KJ> at http://gborg.postgresql.org/project/pgjdbc/projdisplay.php and then KJ> produce a context diff ( -c ) and send it to this list. KJ> Kris Jurka KJ> ---------------------------(end of KJ> broadcast)--------------------------- KJ> TIP 9: the planner will ignore your desire to choose an index scan if your KJ> joining column's datatypes do not match
В списке pgsql-jdbc по дате отправления: