Re: Re: [GENERAL] pg_dump return status..
От | Philip Warner |
---|---|
Тема | Re: Re: [GENERAL] pg_dump return status.. |
Дата | |
Msg-id | 3.0.5.32.20010106002513.0362e2e0@mail.rhyme.com.au обсуждение исходный текст |
Ответ на | Re: [GENERAL] pg_dump return status.. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Re: [GENERAL] pg_dump return status..
|
Список | pgsql-hackers |
At 20:50 4/01/01 -0500, Tom Lane wrote: > >Talk to Philip Warner about detecting output write failures. I think >this might be a lot easier in current sources than it would have been in >7.0.* or before; the actual I/O is more centralized, and I think you >could reasonably hope to check for write errors at just a couple of >places. There are a few places to check, but a lot less than before. Assuming I should just die on any failed write (which seems reasonable), how do I check for a failed write in a way that works on all Unixes? Is the following OK: - fwrite: ok if return value equals item count - fprintf: ok if return value > 0. - fputc: ok if != EOF ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 0500 83 82 82 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/
В списке pgsql-hackers по дате отправления: