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

Re: [HACKERS] COPY formatting

From: "Matt Van Mater" <nutter_(at)hotmail(dot)com>
To: pgman(at)candle(dot)pha(dot)pa(dot)us, pgsql-general(at)postgresql(dot)org
Subject: Re: [HACKERS] COPY formatting
Date: 2004-05-26 16:34:05
Message-ID: BAY9-F49tHJQQw0kmPi000446f8@hotmail.com (view raw or flat)
Thread:
Lists: pgsql-general
I have a comment about the following thread from about 2 months ago that 
dealt with delimiters in the copy command:
http://marc.theaimsgroup.com/?l=postgresql-general&m=107960271207890&w=2

I wanted to chime in and say that I think having more complex delimiters 
would be very useful.  I was curious if there are any developers considering 
working on this?  Here is an example of why I would like to see multi 
character delimiters:

I use pgsql 7.3.2 on OpenBSD 3.4 to store the results of my nessus scans 
(nessus is a very large and popular vulnerability scanner, see nessus.org).  
I currently use perl to parse the scan results and create tens of thousands 
of insert statements for each scan that is run, and was looking into using 
the copy command to speed up adding that data to the db.  Nessus scan 
results are very text heavy and often have many characters within the text 
fields, so I don't think there are any single characters that I can use as a 
delimiter (^|,\n and many others are all used within the scan results).  
With that in mind I'd like to specify my own custom multi character 
delimiter to ensure that it won't be used within a field.

Matt

_________________________________________________________________
Best Restaurant Giveaway Ever! Vote for your favorites for a chance to win 
$1 million! http://local.msn.com/special/giveaway.asp


Responses

pgsql-general by date

Next:From: Mario SotoDate: 2004-05-26 16:35:57
Subject: Re: [GENERAL] performance very slow
Previous:From: Tom LaneDate: 2004-05-26 16:27:47
Subject: Re: planer don't use index. bad plan for where id = x or id in (select ...)

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