| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY formatting |
| Date: | 2004-03-22 14:57:00 |
| Message-ID: | 29626.1079967420@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> writes:
> On Fri, Mar 19, 2004 at 09:54:37AM -0500, Tom Lane wrote:
>> Why? The client-side code doesn't have any real say over the meaning of
>> the data, at least not in psql-class clients. I suppose a client app
>> that tries to interpret the data could get confused, but psql sure
>> doesn't do that.
> libpq, fe-protocol2.c, pqGetCopyData2() and pqGetline2() cut string
> behind '\n'.
Sure, but that doesn't invalidate the data stream as a whole, it's just
a bufferload boundary choice that won't be very helpful for clients not
using a newline-based data layout. In any case, v2 protocol is
obsolete and needn't limit our thoughts about what to do in future.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-03-22 14:59:33 | Re: Custom format for pg_dumpall |
| Previous Message | Bruce Momjian | 2004-03-22 14:52:54 | Re: [PATCHES] UnixWare/CVS Tip/initdb.c needs to use threads |