Skip site navigation (1) Skip section navigation (2)

Re: [BUGS] BUG #1347: Bulk Import stopps after a while (

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 11:31:49
Message-ID: Pine.BSO.4.56.0412220626570.11565@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-jdbc

On Wed, 15 Dec 2004, Oliver Jowett wrote:

> OK, it looks like it is the connection deadlock issue, but triggered by 
> a case I hadn't considered. For some reason every query in the batch is 
> creating a new named statement on the backend .. and the statement 
> cleanup process that happens before query execution is flooding 
> statement Close commands down the connection on the second batch 
> execution, which appears to deadlock the connection. The exact behaviour 
> will be fairly unpredicatable as it depends on when the JVM does garbage 
> collection.
> 

Any news on this?  In general it seems like the whole statement/portal 
cleanup is too lazy.  These things can take up significant backend 
resources and I would have expected calling ResultSet.close() and/or 
Statement.close() to actually close something (perhaps not immediately, 
but at least on the next network trip).

Kris Jurka

In response to

Responses

pgsql-jdbc by date

Next:From: Xavier PoinsardDate: 2004-12-22 11:34:54
Subject: Re: Patch to reduce the number of messages to translate
Previous:From: Kris JurkaDate: 2004-12-22 11:26:44
Subject: Re: Bug in JDBC-Driver?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group