Re: new compiler warnings

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> It is a pity we can't just tell the compiler to turn off the warning in
> a particular case.

I haven't tested, but won't an explicit cast to void silence the
warning?

(void) fwrite(...);

There are places, notably the calls in elog.c, where ignoring write
failures is the right thing. I think that what Kevin was on about
was something else entirely, namely whether we need to retry writes
to disk. I would hope that we're not simply not bothering to check
in any cases where it matters.

regards, tom lane