Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: copy progress notification
- From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: copy progress notification
- Date: Wed, 31 May 2006 18:43:23 +0200
Tom Lane wrote:
Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:Do you have a comment about the progress notification and its impact on copy to stdout?I didn't bother to comment on it because I think it's useless,
It's useful to see anything at all, and to be able to estimate how long the whole process will take. People might find it interesting whether they should go for a cup of coffee or come better back the next day...
as well as broken for the stdout case.
I know it's broken, but why? Is using ereport when sending copy data illegal by design? If not, it's not the feature that's broken but something in cvs HEAD.
Regards, Andreas
- References:
- copy with compression progress n
- From: Andreas Pflug
- Re: copy with compression progress n
- From: Tom Lane
- Re: copy with compression progress n
- From: Andreas Pflug
- Re: copy with compression progress n
- From: Tom Lane
- copy with compression progress n
- Prev by Date: Re: Possible TODO item: copy to/from pipe
- Next by Date: Re: Possible TODO item: copy to/from pipe
- Previous by thread: Re: copy with compression progress n
- Next by thread: Still not happy with psql's multiline history behavior
- Indexes: