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

pgsql: Don't try to constant-fold functions returning RECORD.

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't try to constant-fold functions returning RECORD.
Date: 2005-07-03 21:14:19
Message-ID: (view raw or whole thread)
Lists: pgsql-committers
Log Message:
Don't try to constant-fold functions returning RECORD.  We were never
able to do this before, but I had tried to make an exception for functions
with OUT parameters.  Michael Fuhr found one problem with it already, and
I found another, which was it didn't work for strict functions with a
NULL input.  While both of these could be worked around, the probability
that there are more gotchas seems high; I think prudence dictates just
reverting to the former behavior for now.  Accordingly, remove the kluge
added to get_expr_result_type() for Michael's case.

Modified Files:
        clauses.c (r1.199 -> r1.200)
        funcapi.c (r1.23 -> r1.24)

pgsql-committers by date

Next:From: Tom LaneDate: 2005-07-03 21:56:19
Subject: pgsql: Fix memory leak in plperl_hash_from_tuple(), per report from
Previous:From: Peter EisentrautDate: 2005-07-03 18:54:29
Subject: pgsql: Support cross compilation by compiling "zic" with a native

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