Re: Trouble with COPY IN

From: Samuel Gendler <sgendler(at)ideasculptor(dot)com>
To:
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Trouble with COPY IN
Date: 2010-07-19 15:11:00
Message-ID: AANLkTimCYa3fvWu2-NwcUc_7GibTpFB1RjNC09IVk8IS@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

I've fixed other COPY-related bugs by running the latest code from
revision control rather than the latest released driver. My problem
doesn't appear to be the same as your problem, but it is probably
worth a test, since it is pretty trivial to build the driver from
source.

On Mon, Jul 19, 2010 at 7:16 AM, Matthew Wakeling <matthew(at)flymine(dot)org> wrote:
> On Mon, 19 Jul 2010, Matthew Wakeling wrote:
>>
>> I have isolated a reasonably small example that fails.
>
> Just ran the example again, and it passed. Looks like an intermittent
> problem, not a deterministic one. However, it does seem that the size of the
> COPY is a significant factor.
>
> Matthew
>
> --
> Here we go - the Fairy Godmother redundancy proof.
>                                       -- Computer Science Lecturer
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-07-19 16:49:12 Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock
Previous Message Robert Haas 2010-07-19 14:54:12 Re: SHOW TABLES

Browse pgsql-jdbc by date

  From Date Subject
Next Message Matthew Wakeling 2010-07-20 10:15:31 Re: Trouble with COPY IN
Previous Message Matthew Wakeling 2010-07-19 14:16:12 Re: Trouble with COPY IN