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

pgsql: Check for ERANGE in exp() as well.

From: momjian(at)postgresql(dot)org (Bruce Momjian)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Check for ERANGE in exp() as well.
Date: 2007-01-06 15:18:03
Message-ID: 20070106151803.354519FA4F0@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Log Message:
-----------
Check for ERANGE in exp() as well.

Improve release docs for ecpg regression tests.

Modified Files:
--------------
    pgsql/src/backend/utils/adt:
        float.c (r1.144 -> r1.145)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/float.c.diff?r1=1.144&r2=1.145)
    pgsql/src/tools:
        RELEASE_CHANGES (r1.71 -> r1.72)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/tools/RELEASE_CHANGES.diff?r1=1.71&r2=1.72)

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2007-01-06 15:24:13
Subject: Re: 8.3 pending patch queue
Previous:From: Dan LangilleDate: 2007-01-06 14:44:40
Subject: Re: PGCon 2007 Program Committee

pgsql-committers by date

Next:From: Bruce MomjianDate: 2007-01-06 15:19:45
Subject: pgsql: Document problems with release links in early branches.
Previous:From: User OkbobDate: 2007-01-06 09:22:28
Subject: plpsm - plpgpsm: refactoring fetch stmt, early (compile time) check

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