Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Add comments about why errno is set to zero.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add comments about why errno is set to zero.
Date: 2005-12-01 20:53:34
Message-ID: 16974.1133470414@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
momjian(at)postgresql(dot)org (Bruce Momjian) writes:
> Log Message:
> -----------
> Add comments about why errno is set to zero.

These comments seem a bit wrongheaded, since "checking
LONG_MIN/LONG_MAX" is exactly not what we could do to detect an overflow
error.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Greg StarkDate: 2005-12-01 20:54:42
Subject: Re: generalizing the planner knobs
Previous:From: Bruce MomjianDate: 2005-12-01 20:50:06
Subject: Re: [HACKERS] Strange interval arithmetic

pgsql-committers by date

Next:From: Bruce MomjianDate: 2005-12-01 21:00:15
Subject: Re: [COMMITTERS] pgsql: Add comments about why errno is set to zero.
Previous:From: Tom LaneDate: 2005-12-01 20:24:49
Subject: pgsql: Retry in FileRead and FileWrite if Windows returns

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group