| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(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:23:26 |
| Message-ID: | 11451.1054581806@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-06-02 19:25:56 | Re: Status during copy [patch] |
| Previous Message | Bruce Momjian | 2003-06-02 19:14:33 | Re: Postgres config file: autocommit = off |