Re: Status during copy [patch]

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Status during copy [patch]
Date: 2003-06-02 19:25:56
Message-ID: 200306021925.h52JPuV21332@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Yes, completely agree. Added to TODO:

> o Return the number of rows loaded/unloaded

---------------------------------------------------------------------------

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > How do people feel about this patch? Currently COPY doesn't even return
> > a line count of the number of lines processed, while this patch would
> > make psql \copy produce date/time and count every 1000 rows, then print
> > a similar completion message.
>
> Seems much too noisy for me. That would be appropriate behavior in a
> GUI, but psql is not and never will be a GUI. Martijn's concern about
> hacking the behavior depending on where stderr points demonstrates
> exactly why we don't want to do this.
>
> I would not object to adding a line count to the COPY command completion
> report (on the server side), though. That's arguably comparable to the
> number-of-rows-processed values for INSERT/UPDATE/DELETE.
>
> regards, tom lane
>

--
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Rasmus Resen Amossen 2003-06-02 19:34:41 Re: Postgres config file: autocommit = off
Previous Message Tom Lane 2003-06-02 19:23:26 Re: Status during copy [patch]