Re: pgsql-server/ oc/src/sgml/ref/copy.sgml rc/bac ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Neil Conway <neilc(at)samurai(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql-server/ oc/src/sgml/ref/copy.sgml rc/bac ...
Date: 2003-04-20 03:40:38
Message-ID: 24771.1050810038@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> COPY to STDOUT/STDIN will be controlled by the client end-of-line
> because those files are opened in text mode by the client, I think.

Actually, I was going to question you on that before. AFAICT, the
just-committed code will *only* send LF newlines during COPY TO STDOUT,
independent of the server's OS, the client's OS, or anything else.

This is perhaps justifiable on the grounds that "the FE/BE protocol
spec says LF and not anything else", and I didn't complain because
I assumed that was your thinking. But your response to Neil doesn't
suggest that you're thinking that way. What exactly do you have in
mind here? Certainly the client is not going to determine the
newline format for COPY TO STDOUT unless it does translation.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2003-04-20 17:03:25 pgsql-server/src/backend/commands trigger.c
Previous Message Bruce Momjian - CVS 2003-04-20 01:52:56 pgsql-server/doc/src/sgml/ref copy.sgml