Tom Lane wrote:
>Claudio Natoli <claudio.natoli@memetrics.com> writes:
>
>
>>However, a number of tests fail purely because, for some reason, ERROR
>>messages seem to get printed out at the end of the test, instead of where
>>expected, and sometimes with an extra blank line. I've included a few
>>examples below.
>>
>>
>
>
>
>>Anyway care to hazard a guess as to what the cause could be, and how to
>>correct?
>>
>>
>
>Lack of fflush(stderr) maybe? On Unix systems stderr is line-buffered
>and so it's seldom necessary to fflush it, but perhaps Windows gets this
>wrong (yawn...).
>
>
>
Or unbuffered. On Linux "man setbuf " says:
The standard error stream stderr is always unbuffered by default.
Perhaps on Windows we should put a call to "setbuf(stderr,NULL)"
somewhere right at the beginning of each program.
cheers
andrew