From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql and COPY BINARY |
Date: | 2005-12-15 01:27:04 |
Message-ID: | 43A0C668.1030508@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I submitted a patch a while back to change that but I withdrew it
because I wasn't 100% confident I'd done it right.
Here is the link to it:
http://archives.postgresql.org/pgsql-patches/2005-03/msg00242.php
It's probably 99% there - just a bit of checking.
Chris
Andreas Pflug wrote:
> Examining why psql won't do sensible stuff with COPY BINARY, I realized
> that psql still uses PQgetline, which is marked obsolete since 7.4.
> Is this intentional or just a "never reviewed because it works"?
> Unfortunately, psql/copy.c also states "if you want to use copy in your
> app, this is the code to steal". Seems not a good template code any more.
>
>
> Regards,
> Andreas
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2005-12-15 01:28:53 | Re: psql and COPY BINARY |
Previous Message | Christopher Kings-Lynne | 2005-12-15 01:20:46 | Re: Refactoring psql for backward-compatibility |