Re: psql copy command - 1 char limitation on delimiter
От | Bruce Momjian |
---|---|
Тема | Re: psql copy command - 1 char limitation on delimiter |
Дата | |
Msg-id | 201010130328.o9D3Stw09261@momjian.us обсуждение исходный текст |
Ответ на | Re: psql copy command - 1 char limitation on delimiter (Steve Crawford <scrawford@pinpointresearch.com>) |
Ответы |
Re: psql copy command - 1 char limitation on delimiter
|
Список | pgsql-general |
Steve Crawford wrote: > On 09/25/2010 07:03 AM, Tom Lane wrote: > > rey<reywang@optonline.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@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
В списке pgsql-general по дате отправления: