Skip site navigation (1) Skip section navigation (2)

Unworkable column delimiter characters for COPY

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Unworkable column delimiter characters for COPY
Date: 2007-12-27 15:37:07
Message-ID: 5426.1198769827@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Currently, copy.c rejects newline, carriage return, and backslash as
settings for the column delimiter character (in non-CSV mode).  These
all seem necessary to avoid confusion.  However, I just noticed that the
letters r, n, t, etc would also not work: on output, data characters
matching such a delimiter would get escaped as \r, \n, etc, which on
input would be read as C-style control characters.

I think at minimum we need to forbid b, f, n, r, t, v, which are the
control character representations currently recognized by COPY.
But I'm tempted to make it reject all 26 lower-case ASCII letters,
as a form of future-proofing.  Thoughts?

			regards, tom lane

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2007-12-27 16:39:29
Subject: Re: Binary data type with other output method
Previous:From: Andreas 'ads' ScherbaumDate: 2007-12-27 15:19:09
Subject: Re: Binary data type with other output method

pgsql-patches by date

Next:From: Andrew DunstanDate: 2007-12-27 16:58:50
Subject: Re: Unworkable column delimiter characters for COPY
Previous:From: Hans-Juergen SchoenigDate: 2007-12-27 08:37:19
Subject: CONNECT BY for 8.3 ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group