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

Re: [HACKERS] Trouble with COPY IN

From: James William Pye <lists(at)jwp(dot)name>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kris Jurka <books(at)ejurka(dot)com>, pgsql-hackers(at)postgresql(dot)org, Matthew Wakeling <matthew(at)flymine(dot)org>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Maciek Sakrejda <msakrejda(at)truviso(dot)com>, Samuel Gendler <sgendler(at)ideasculptor(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [HACKERS] Trouble with COPY IN
Date: 2010-07-25 02:03:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-jdbc
On Jul 23, 2010, at 7:11 AM, Tom Lane wrote:
> I can't help thinking that the JDBC driver must be being overly cute
> if this breaks it ...

I was wondering the same thing when I first saw Kris' message. However, iff I understand what JDBC is trying to achieve, I don't think I would call it "overly".


Is this a problem because JDBC is trying to detect failures as early as possible during a COPY IN?
Or, is it just JDBC's normal MO to always be reading?

Well, I've wanted to do the former (early error detection) with py-postgresql's COPY support, and I imagine getting a read event marking completion prior to emitting done/fail could be a snag.

cheers, jwp

In response to


pgsql-hackers by date

Next:From: Joseph AdamsDate: 2010-07-25 02:34:53
Subject: patch: utf8_to_unicode (trivial)
Previous:From: Andres FreundDate: 2010-07-25 00:22:36
Subject: Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP)

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2010-07-25 15:01:48
Subject: Re: [HACKERS] Trouble with COPY IN
Previous:From: Radosław SmoguraDate: 2010-07-24 15:21:00
Subject: Re: Binary protocol support for JDBC

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