pgsql: Add comments about why errno is set to zero.
This is a discussion on pgsql: Add comments about why errno is set to zero. within the pgsql Committers forums, part of the PostgreSQL category; --> Log Message: ----------- Add comments about why errno is set to zero. Modified Files: -------------- pgsql/src/backend/utils/adt: datetime.c (r1.162 -> ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-10-2008, 06:34 PM
| ||||
| ||||
 pgsql: Add comments about why errno is set to zero. Log Message: ----------- Add comments about why errno is set to zero. Modified Files: -------------- pgsql/src/backend/utils/adt: datetime.c (r1.162 -> r1.163) (http://developer.postgresql.org/cvsw...1.162&r2=1.163) float.c (r1.116 -> r1.117) (http://developer.postgresql.org/cvsw...1.116&r2=1.117) ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org      |
|
04-10-2008, 06:34 PM
| ||||
| ||||
| Re: pgsql: Add comments about why errno is set to zero. momjian@postgresql.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 ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend |
 |
« pgsql: Retry in FileRead and FileWrite if Windows returns
|
pgsql: Comment "errno = 0" in a more generic way. »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 07:21 PM.
