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

python - be: Expected is always filled in now, so it cannot be used as

From: jwp(at)pgfoundry(dot)org (James William Pye)
To: pgsql-committers(at)postgresql(dot)org
Subject: python - be: Expected is always filled in now, so it cannot be used as
Date: 2005-08-12 04:26:42
Message-ID: 20050812042642.1F47A1125018@pgfoundry.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Expected is always filled in now, so it cannot be used as an indicator to
whether the call or the result of the call is to be returned.

Modified Files:
--------------
    be/src:
        function.c (r1.8 -> r1.9)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/be/src/function.c.diff?r1=1.8&r2=1.9)

pgsql-committers by date

Next:From: Tom LaneDate: 2005-08-12 05:05:51
Subject: pgsql: Remove BufferBlockPointers array in favor of a base + (bufnum) *
Previous:From: Bruce MomjianDate: 2005-08-12 03:25:36
Subject: pgsql: Add files to do read I/O on the cluster directory:

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