Re: Status reporting for COPY

From: Doug McNaught <doug(at)mcnaught(dot)org>
To: jim(at)nasby(dot)net
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Status reporting for COPY
Date: 2003-05-14 17:18:05
Message-ID: m3he7xe9bm.fsf@varsoon.wireboard.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

"Jim C. Nasby" <jim(at)nasby(dot)net> writes:

> Would it be difficult to allow COPY to output intermediate status while
> it's in operation? IE: total rows copied so far, and maybe what position
> in the file it's in on a copy from? This would let you know it was still
> working as well as giving you some idea how much longer it will take. It
> would also be handy to get a summary report after the copy was done...
> rows inserted or exported, how long it took, rows/second.

IMHO this should be done by the client--use 'COPY FROM stdin' and keep
track yourself of where you are in the copy as you send the data. I'd
hate to clutter up the wire protocol with status updates that are
basically noise.

There's no reason that psql's \copy command couldn't be enhanced to do
this on the client side.

> BTW, is there a more official means of submitting feature requests? I
> don't see anything like a Bugzilla for PGSQL...

Posting to -hackers is probably a better place than -general.

-Doug

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mike Mascari 2003-05-14 17:22:27 Re: - what protocol for an Internet postgres
Previous Message Forest Wilkinson 2003-05-14 17:12:41 Re: fomatting an interval (resend)

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-05-14 17:21:27 Re: DNS problem,
Previous Message Forest Wilkinson 2003-05-14 17:12:41 Re: fomatting an interval (resend)