Re: utf8 COPY DELIMITER? - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: utf8 COPY DELIMITER?
Date
Msg-id 20070418163806.GS72669@nasby.net
Whole thread Raw
In response to Re: utf8 COPY DELIMITER?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: utf8 COPY DELIMITER?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Tue, Apr 17, 2007 at 02:28:18PM -0400, Tom Lane wrote:
> I doubt that supporting a single multibyte character would be an
> interesting extension --- if we wanted to do anything at all there, we'd
> just generalize the delimiter to be an arbitrary string.  But it would
> certainly slow down COPY by some amount, which is an area where you'll
> get push-back for performance losses, so you'd need to make a convincing
> use-case for it.

Couldn't we use a fast code path (what we have now) for the case when
the delimiter is a single byte? That would allow for multi-character
delimiters without penalizing those that don't use them.

As for use case, I worked on migrating some stuff out of a MySQL
database a while ago, and having arbitrary string delimiters would have
made life easier.
-- 
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Autovacuum vs statement_timeout
Next
From: Robert Treat
Date:
Subject: Re: Autovacuum vs statement_timeout