From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, rey <reywang(at)optonline(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: psql copy command - 1 char limitation on delimiter |
Date: | 2010-10-13 03:28:55 |
Message-ID: | 201010130328.o9D3Stw09261@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Steve Crawford wrote:
> On 09/25/2010 07:03 AM, Tom Lane wrote:
> > rey<reywang(at)optonline(dot)net> writes:
> >
> >> Why limit this to a single character?
> >>
> > Performance. Believe it or not, breaking fields at the delimiter is
> > a significant factor in COPY speed.
> >
> > regards, tom lane
> >
> >
> I agree that that multi-character (or even regex) delimiters would be
> useful. Would it be reasonable for the copy process to differentiate
> between single character delimiters which could be processed in
> "high-speed" mode and multi-character or regex delimiters which would be
> available as needed albeit at the expense of a performance hit?
I am not sure you are aware but Postgres never confuses delimiters from
data because it uses a backslash before literal data that matches
delimiters.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2010-10-13 05:31:56 | Re: problem with PG install script on Windows |
Previous Message | Satoshi Nagayasu | 2010-10-13 03:11:42 | Re: NoSQL -vs- SQL |