From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: COPY formatting |
Date: | 2004-03-20 04:00:46 |
Message-ID: | 200403200400.i2K40kI28380@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> Josh Berkus wrote:
>
> >
> >Overall, I assert again that approaching this issue through COPY enhancements
> >is really not the way to go. We should be looking at a client utility,
> >like pg_import and pg_export. The primary purpose of COPY is bulk loads
> >for backup/restore, and I'm against doing a lot of tinkering which might make
> >it less efficient or introduce new issues into what's currently very
> >reliable.
> >
> >
> >
>
> That's not unreasonable. I floated my idea as an alternative to a much
> more radical proposal. If we decided against it we should remove the
> TODO item.
>
> As against that, if we don't do this then I think we should embrace
> these utility programs more, possibly bringing them into the distribution.
CSV seems to be the most widely requested conversion format. Anything
else is probably a one-off job that should be done in perl or sed.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2004-03-20 05:41:49 | Re: looking for an 'array_index' function? |
Previous Message | Kevin Brown | 2004-03-20 03:48:17 | Re: [HACKERS] fsync method checking |