pgsql: Fix LLONG_MAX define used by new int64 FETCH/MOVE patch. - Mailing list pgsql-committers

From momjian@postgresql.org (Bruce Momjian)
Subject pgsql: Fix LLONG_MAX define used by new int64 FETCH/MOVE patch.
Date
Msg-id 20060903011540.A88219FB520@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix LLONG_MAX define used by new int64 FETCH/MOVE patch.

Modified Files:
--------------
    pgsql/src/backend/tcop:
        pquery.c (r1.108 -> r1.109)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/pquery.c.diff?r1=1.108&r2=1.109)
    pgsql/src/include/nodes:
        parsenodes.h (r1.327 -> r1.328)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/parsenodes.h.diff?r1=1.327&r2=1.328)

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Remove unnecessary copyObject() call in update (values) code.
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Fix case where "PM" to_timestamp() mask was eating too many