Re: [HACKERS] COPY problems with psql / libpq

From: "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] COPY problems with psql / libpq
Date: 2000-01-20 18:44:51
Message-ID: 200001201844.SAA10272@linda.lfix.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Patrick Welche wrote:
>On Thu, Jan 20, 2000 at 09:22:16AM -0800, Alfred Perlstein wrote:
>> * Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> [000120 09:10] wrote:
>> > On Thu, Jan 20, 2000 at 11:02:31AM -0500, Tom Lane wrote:
>> > >
>> > > It sure sounds like psql is failing to recognize the trailing \.
>> > > of the COPY data.
>> >
>> > Precisely what I saw yesterday (cf Subject: pg_dump disaster) - but what
>> > does one do about it?
>>
>> Is this with a recent snapshot or 6.5.3 using libpq?
>
>For me, it's using yesterday's cvs'd source - but I obviously can't speak
>for Oliver.

This morning's.

>> Either way, you should check the contents of the send buffer, please let
>> me know if there is data queued in it. You can include the 'internal'
>> header for libpq (libpq-int.h?) to get at the send buffer.
>
>That will take a while. In the meantime, just pg_dumpall something and try
>to read the output back in. I do have ^M's in some of the text columns if
>that matters.

I can't do that, because pg_dump seems to be broken if there are tables
with foreign key constraints. (See a separate message.)

--
Oliver Elphick Oliver(dot)Elphick(at)lfix(dot)co(dot)uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP key from public servers; key ID 32B8FAA1
========================================
"Neither is there salvation in any other; for there is
none other name under heaven given among men, whereby
we must be saved." Acts 4:12

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Elphick 2000-01-20 18:44:53 pg_dump and foreign keys
Previous Message The Hermit Hacker 2000-01-20 18:14:09 Re: [HACKERS] off topic