> > > Should work fine on Windows. fileno() is deprecated however, with
> > > the following comment:
> > > C:\Program Files\Microsoft Visual Studio
> > > 8\VC\INCLUDE\stdio.h(688) : see
> > > declaration of 'fileno'
> > > Message: 'The POSIX name for this item is deprecated.
> >
Tom Lane wrote:
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> > Should work fine on Windows. fileno() is deprecated however, with the
> > following comment:
> > C:\Program Files\Microsoft Visual Studio
> > 8\VC\INCLUDE\stdio.h(688) : see
> > declaration of 'fileno'
> > Message:
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> Should work fine on Windows. fileno() is deprecated however, with the
> following comment:
> C:\Program Files\Microsoft Visual Studio
> 8\VC\INCLUDE\stdio.h(688) : see
> declaration of 'fileno'
> Message: 'The POSIX name for this item
> >> Hmm. If the messages are less than PIPE_BUF bytes long
> (4096 bytes
> >> on
> >> Linux) then the writes are supposed to be atomic.
>
> > Some of them involve long messages (>4K), but there are
> many that do
> > not (like the ones I had posted at the start of this thread).
>
> I checke
Tom Lane wrote:
> I checked around with some kernel/glibc gurus in Red Hat, and the
> consensus seemed to be that we'd be better off to bypass fprintf() and
> just send message strings to stderr using write() --- ie, instead of
> elog.c doing
>
> fprintf(stderr, "%s", buf.data);
>
> d
