| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: testing cvs HEAD - HS/SR - cannot stat |
| Date: | 2010-02-04 18:33:19 |
| Message-ID: | 9837222c1002041033nf390c12jbc40050e95328d4c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2010/2/4 Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>:
> Josh Berkus wrote:
>> Can we improve the error message? Right now it's alarming people. Such as:
>>
>> cannot stat
>> `/var/data1/pg_stuff/dump/replication_archive/000000010000000000000002':
>> End of Log
>
> Not really, it's coming from 'cp'. Not sure if we could capture the
> stderr and somehow decorate the message to make it less alarming.
>
> This isn't really a new problem, PITR has always done that, but I agree
> it's always been a bit clumsy to have those messages in the log.
Can we follow it up with a well-phrased message that we switched to
streaming mode right after it, so people realize it's not a problem?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2010-02-04 18:46:06 | Re: testing cvs HEAD - HS/SR - cannot stat |
| Previous Message | Heikki Linnakangas | 2010-02-04 18:29:43 | Re: testing cvs HEAD - HS/SR - cannot stat |