| From: | Adrian Klaver <aklaver(at)comcast(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | Glen Beane <Glen(dot)Beane(at)jax(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Problem using COPY command to load data |
| Date: | 2008-11-12 02:31:04 |
| Message-ID: | 200811111831.05207.aklaver@comcast.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tuesday 11 November 2008 6:20:09 pm Glen Beane wrote:
>
> Python with the psycopg2 library. I swear this was working earlier today.
> Maybe I am imagining things :)
> It does work with a unix socket, and I have a deadline to meet, so for now
> I just need to make sure I am running this on the same host as the
>postgresqlserver
See these two posts for potential solution:
http://lists.initd.org/pipermail/psycopg/2008-October/006224.html
http://lists.initd.org/pipermail/psycopg/2008-October/006225.html
They point to a problem with ssl and psycopg2 COPY. Also I know there where
some problems with psycopg2 and copy that where fixed in psycopg2 version
2.0.7.
--
Adrian Klaver
aklaver(at)comcast(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2008-11-12 02:42:10 | Re: Problem using COPY command to load data |
| Previous Message | Tom Lane | 2008-11-12 02:29:00 | Re: Avoiding seq scan over 3.2 millions rows |