Re: Status during copy [patch] - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Status during copy [patch]
Date
Msg-id 200306021925.h52JPuV21332@candle.pha.pa.us
Whole thread Raw
In response to Status during copy [patch]  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-hackers
Yes, completely agree.  Added to TODO:

>       o Return the number of rows loaded/unloaded


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

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.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@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: initdb problems handling super username with spaces.
Next
From: Tom Lane
Date:
Subject: Re: Status during copy [patch]