| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Bahadur Singh <bahadursingh(at)yahoo(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #1347: Bulk Import stopps after a while ( |
| Date: | 2004-12-22 23:18:12 |
| Message-ID: | Pine.BSO.4.56.0412221811190.15268@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Thu, 23 Dec 2004, Oliver Jowett wrote:
> I don't have the code to hand, but from memory an explicit
> close of the Query does exactly this -- it clears the
> reference which causes it to be immeditately enqueued, and
> the next query will do cleanup when it polls the reference
> queue.
This is true for the Query/Portal objects, the problem is that the
Statement/ResultSets aren't closing the underlying objects. Will fix.
> I was more worried about why a batch update was generating
> so many individual named statements.. it should either use
> zero (Statement.addBatch) or one
> (PreparedStatement.addBatch) named statement, not N statements.
>
Ahhh. The protocol is a problem, but this named statement misuse is
triggering it. I can take a look at that.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2004-12-22 23:33:25 | Re: PreparedStatement and setting an array is now broken |
| Previous Message | Andrew Lazarus | 2004-12-22 22:06:26 | PreparedStatement and setting an array is now broken |