I'd be willing to take a more in-depth look if you can minimize this
to a small, at-least-semi-reproducible test case. Ideally, something
that can be included in
http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/test/jdbc2/CopyTest.java
(since I noticed the driver doesn't have any WITH BINARY tests).
If that's more trouble to you than it's worth, I'd try turning on
driver-level logging and see if that gets you anything, or look at the
traffic on the wire with something like wireshark to see if you're
seeing the network traffic you expect (from the sound of it, I don't
expect the problem to be there, but it's always nice to eliminate
things). A protocol reference is available (
http://developer.postgresql.org/pgdocs/postgres/protocol-flow.html#PROTOCOL-COPY
), but you're basically looking for the pattern CopyIn CopyData*
(CopyDone|CopyFail). If for some reason you see other messages
interspersed from the client or a repeated Copy{Done,Fail} from the
client, that could be a bad sign (although again, your server logs
suggest this isn't the case).
---
Maciek Sakrejda | System Architect | Truviso
1065 E. Hillsdale Blvd., Suite 230
Foster City, CA 94404
(650) 242-3500 Main
(650) 242-3501 F
www.truviso.com
On Tue, Jul 20, 2010 at 3:29 AM, Matthew Wakeling <matthew@flymine.org> wrote:
> On Tue, 20 Jul 2010, Matthew Wakeling wrote:
>>
>> That does indeed fix the problem. I didn't realise the published jar was
>> so old!
>
> Okay, no it doesn't fix the problem after all. Identical stack trace to
> before. Any ideas?
>
> Matthew
>
> --
> for a in past present future; do
> for b in clients employers associates relatives neighbours pets; do
> echo "The opinions here in no way reflect the opinions of my $a $b."
> done; done
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>