Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: JDBC causing the connection to close after executing a COPY command
- From: Kris Jurka <books(at)ejurka(dot)com>
- To: Altaf Malik <mmalik_altaf(at)yahoo(dot)com>
- Cc: Dave Cramer <pg(at)fastcrypt(dot)com>, pgsql-jdbc(at)postgresql(dot)org
- Subject: Re: JDBC causing the connection to close after executing a COPY command
- Date: Mon, 28 Jan 2008 05:10:54 -0500 (EST)
On Fri, 14 Dec 2007, Altaf Malik wrote:
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.
Applied and backpatched to 8.0. Kris Jurka
- Prev by Date: Re: JDBC and GSSAPI/Krb5
- Next by Date: Re: JDBC and GSSAPI/Krb5
- Previous by thread: Re: JDBC and GSSAPI/Krb5
- Next by thread: backpatching 8.2 to deal with batch callable statements
- Indexes: