Re: [PATCHES] Current-stream read for psql's \copy

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Feit <mfeit(at)notonthe(dot)net>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Current-stream read for psql's \copy
Date: 2004-02-10 18:57:08
Message-ID: 25311.1076439428@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Mark Feit <mfeit(at)notonthe(dot)net> writes:
> What precipitated the patch in the first place was a need to be able
> to do copies in-line to populate tables with small amounts of initial
> data.

Right, that's clearly useful. The debate at hand is about the
usefulness of the other behavior.

BTW, pg_dump scripts use COPY FROM STDIN (not \copy) to achieve this
same behavior of reading COPY data from the script file. Your patch was
thus not strictly necessary, since there was already a way to do what it
did --- but I accepted it anyway, since it seems reasonable that \copy
should be able to do it too.

What Bruce is suggesting is that we remove the old \copy behavior and
make it *only* able to do what COPY FROM STDIN does. That strikes me
as loss of important functionality ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Sullivan 2004-02-10 18:57:14 Re: [PATCHES] Current-stream read for psql's \copy
Previous Message Mark Feit 2004-02-10 18:44:22 Re: [PATCHES] Current-stream read for psql's \copy

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Sullivan 2004-02-10 18:57:14 Re: [PATCHES] Current-stream read for psql's \copy
Previous Message Mark Feit 2004-02-10 18:44:22 Re: [PATCHES] Current-stream read for psql's \copy