From: | Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> |
---|---|
To: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
Cc: | Oliver(dot)Elphick(at)lfix(dot)co(dot)uk, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] COPY problems with psql / libpq |
Date: | 2000-01-20 17:26:59 |
Message-ID: | 20000120172659.L12966@quartz.newn.cam.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
> 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.
Cheers,
Patrick
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-01-20 17:55:04 | Re: [HACKERS] Status on 7.0 |
Previous Message | Thomas Lockhart | 2000-01-20 17:24:40 | Re: [HACKERS] timezone problem? |