Re: Re: [COMMITTERS] pgsql: Silence compiler warning about ignored return value.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Silence compiler warning about ignored return value.
Date: 2008-11-20 20:08:24
Message-ID: 7153.1227211704@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Tom Lane wrote:
>> We're definitely *not* fortify-clean, although maybe trying to become so
>> would be a good idea. From memory, what I have seen in past builds on
>> Red Hat systems is a lot of warnings about ignoring the return value
>> from fwrite() and related functions.

> So. Should I revert it?

I dunno. Was that the only such warning you got on your build? That
would be a bit odd given that I see many more ...

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2008-11-20 20:45:30 pgsql: Issue a proper error message when MD5 is attempted when
Previous Message Tom Lane 2008-11-20 19:52:54 pgsql: Fix breakage of bitmap scan plan creation for special index

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-20 20:16:54 Re: pg_upgrade: How to deal with toast
Previous Message Tom Lane 2008-11-20 20:05:35 Re: Problem with Bitmap Heap Scan