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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Magnus Hagander <magnus(at)hagander(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-21 17:07:34
Message-ID: 6373.1227287254@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane wrote:
>> (Whatcha gonna do if you fail to write the postmaster log ... try to
>> log a complaint message?)

> Well, good question, but I'm not convinced that doing nothing is always
> the best answer.

I didn't say it was --- merely opined that we need a consistent plan
about how to handle corner cases like that if we want to try to wipe out
all the warnings of this class.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2008-11-21 17:21:51 Re: Re: [COMMITTERS] pgsql: Silence compiler warning about ignored return value.
Previous Message Peter Eisentraut 2008-11-21 16:46:19 pgsql: Include the platform "FAQs" into the installation instructions.

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-11-21 17:09:23 Re: How should pg_standby get over the gap of timeline?
Previous Message Simon Riggs 2008-11-21 16:53:22 Re: Opening a recovering DB in for read-only access?