|
|||||||||||
|
Re: [JDBC] JDBC causing the connection to close after executing a COPY command
From: Altaf Malik <mmalik_altaf(at)yahoo.com>
Date: Fri Dec 14 2007 - 16:50:52 EST
For CopyInResponse, client will send a CopyFail message and server won't wait for the client input. For CopyOutResponse, exception is generated for only CopyOutResponse and not for every CopyData message. Also slightly changed the 'ignoring' mechanism from reading the message to ignore it to skipping the message. I hope this will also improve the performance.
Altaf Malik
Kris Jurka <books@ejurka.com> wrote: In the case of copying data from the server, if you do have a large table, you'll generate a SQLException for every row of the copy result which isn't great, but I guess it's better than failing completely. Trying to copy out a single column table of 100k integers took about seven minutes and 150 MB of memory here. Also, it doesn't work for copying data to the server. In that case the server is sitting waiting for data and the driver is waiting for the server and nothing happens. That was the case before, so this is no worse. Do you have plans to work on this further or shall I apply just this minor improvement? Kris Jurka
Best Regards
Never miss a thing. Make Yahoo your homepage. ---------------------------(end of broadcast)---------------------------TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
This archive was generated by hypermail 2.1.8 : Wed Jun 18 2008 - 23:41:32 EDT |
||||||||||
|
|||||||||||