Re: Different length lines in COPY CSV - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Different length lines in COPY CSV
Date
Msg-id 1693.1134399616@sss.pgh.pa.us
Whole thread Raw
In response to Re: Different length lines in COPY CSV  ("Andrew Dunstan" <andrew@dunslane.net>)
Responses Re: Different length lines in COPY CSV  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
"Andrew Dunstan" <andrew@dunslane.net> writes:
> The COPY code is probably on the edge of maintainability now.
> Our CSV routines accept a wide variety of imports formats, but a fixed
> number of columns is required. Maybe we need a pgfoundry project with some
> general perl CSV munging utilities - this issue comes up often enough.

What's been suggested in the past is some sort of standalone
file-format-conversion utility, which could deal with this sort of stuff
without having to also deal with all the backend-internal considerations
that COPY must handle.  So (at least in theory) it'd be simpler and more
maintainable.  That still seems like a good idea to me --- in fact,
given my druthers I would rather have seen CSV support done in such an
external program.
        regards, tom lane


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: psql patch: new host/port
Next
From: Tom Lane
Date:
Subject: Re: default resource limits